Wombatexchange uses WOM that can be bought on Arbitrum or bridged from BNB Chain

Wombatexchange has a governance token, WOM, that can be bought on Arbitrum or bridged from BNB Chain. A local purchase acquires WOM using funds on Arbitrum; a bridge moves an existing transferable WOM balance between networks. veWOM, the vote-escrowed balance created by locking WOM, stays tied to its chain. BNB Chain veWOM does not grant voting rights in Wombatexchange’s Arbitrum deployment.

The choice starts with the location and state of the available assets. Spendable funds on Arbitrum suit a local purchase. Unlocked WOM on BNB Chain can suit bridging, while an active WOM lock introduces a separate withdrawal restriction.

Buying WOM on Arbitrum or bridging it there provides a WOM balance; Wombatexchange gauge voting on Arbitrum requires veWOM created through a lock on that chain.

Buying WOM Directly on Arbitrum

Uniswap is an Arbitrum purchase option for WOM when a suitable trading route is available. The selected network and output token must both match the intended Arbitrum holding. Buying a token called WOM on another chain produces a different network balance, even when the wallet uses the same account address. A local purchase therefore starts with assets that the selected Arbitrum market accepts.

The purchase quote identifies the input that will be spent and the WOM output that the trade expects. Available liquidity and the selected amount affect whether that route offers acceptable terms. A venue listing establishes a place to look for a market, without fixing its current liquidity, price, or available pair. The quote and token contract identify the specific purchase being considered.

Network-Specific WOM Contracts

WOM has different token contracts on BNB Chain and Arbitrum, so the ticker alone cannot identify the intended asset. The WOM token contract on Arbitrum is 0x7b5eb3940021ec0e8e463d5dbb4b7b09a89ddf96 . The output of an Arbitrum purchase or supported incoming bridge should correspond to that network-specific token. A similarly named asset can have a different contract and serve a different purpose.

The BNB Chain WOM contract is 0xad6742a35fb341a9cc6ad674738dd8da98b94fb1 . That address identifies the source asset for the BNB route, not the Arbitrum output. Copying the source contract into a destination token selector confuses two different network contexts.

What Does a WOM Bridge Transfer?

A WOM bridge transfers unlocked WOM between supported networks, while veWOM remains outside that transfer. WOM is the governance token that can be acquired and locked. veWOM represents the vote-escrowed balance associated with a WOM lock. The BNB Chain-to-Arbitrum route concerns transferable WOM; it does not relocate the source lock or reproduce its voting balance on Arbitrum.

The Manual BNB Chain Route Through Wormhole Portal

Acquire WOM documents a manual Wormhole Portal route from BNB Chain to Arbitrum, with source submission followed by destination redemption. Eligible automatic Portal routes use a relayer for destination redemption; check which mode the selected WOM route offers before submitting.

Source Chain and Destination Chain

The Portal flow starts with BNB Chain as the source and Arbitrum as the destination. It connects the source wallet, selects WOM, and connects the destination wallet before initiating the transfer. The selected destination chain and connected wallet determine where the transfer is intended to arrive. Reversing the chain selection describes a different route.

Gas Selection and Source Submission

The documented flow selects the gas-payment method before the transfer confirmation. A wallet confirmation then initiates the source-chain transaction. This authorization concerns the selected WOM transfer. It does not authorize a future WOM lock on Arbitrum, and it does not establish that the destination has already received tokens.

Confirmations and Destination Redemption

The Portal sequence waits for blockchain confirmations before its Redeem action. The destination redemption then requires wallet confirmation.

When Is a Portal WOM Transfer Complete?

The documented Portal transfer completes when destination redemption succeeds and the transferred WOM becomes available on Arbitrum. A successful source transaction establishes that the source action occurred. It does not, by itself, establish destination delivery. The destination transaction and the resulting token balance answer that separate question.

The destination balance also identifies what was received. WOM available under the Arbitrum token contract is distinct from a pending bridge status or a veWOM balance. Before a subsequent lock, the incoming transfer must produce the usable WOM that the Arbitrum locking contract accepts.

Purchase Quotes and Price Movement

A WOM purchase quote describes an exchange at the selected amount and available market conditions. It is different from a bridge quote for moving existing WOM. The trading route determines the quoted conversion, while liquidity and price movement affect the output that can actually settle. WOM has its own market price, separate from the pricing of assets within stableswap pools.

For a conventional wallet-submitted Uniswap swap, slippage tolerance limits an acceptable deterioration from the quoted output. A swap can revert when execution would breach that limit. The settled WOM amount therefore matters when the purchase must meet a particular target.

Gas and Bridge Charges

A route’s transaction estimates indicate its expected network expenses, separate from the quoted WOM output. A wallet-submitted Arbitrum swap needs its applicable network fee. The documented manual Portal flow also requires gas-payment selection and a destination redemption. Final network charges depend on execution; a fee from a stablecoin pool does not describe the entire WOM transfer.

Token Output and Separately Paid Costs

A quote may express the destination amount in WOM and show other expenses in another asset. Those units must stay separate. A gas payment in a network token cannot simply be subtracted numerically from a WOM balance. Any deduction that reduces the WOM received belongs in the destination-token calculation, while separately paid gas affects the additional funds required.

Comparing the Same Destination

A useful comparison keeps the destination chain and intended WOM amount consistent. The purchase route spends its selected input asset, while the bridge route starts with existing WOM. Different starting assets prevent a single nominal fee from deciding the comparison. Each route’s destination output and additional payment requirements describe what it actually delivers.

Wombatexchange Governance on Arbitrum and BNB Chain Locks

Gauge voting uses chain-specific veWOM positions, so acquisition location matters before locking WOM. BNB Chain veWOM does not provide voting rights in Wombatexchange’s Arbitrum governance system. Acquiring WOM on Arbitrum creates the asset needed for an Arbitrum lock. Holding that WOM and holding the resulting veWOM are different states.

A WOM purchase or bridge also leaves an existing liquidity-provider position on its original network. Staking that position and locking WOM remain different operations.

A 176 WOM Target on Arbitrum

In this hypothetical comparison, the target is 176 WOM available on Arbitrum. The purchase case has spendable funds on Arbitrum and a quote for 176 WOM. The bridge case has 176 unlocked WOM on BNB Chain.

View full-size image

The purchase quote describes expected output, whereas the bridge balance describes available input. Only the purchase figure already refers to the destination amount. The bridge’s destination quote must establish how much WOM would arrive after any WOM-denominated deductions. Expenses payable separately in another asset do not reduce the WOM amount merely because they appear beside it.

If either completed route makes 176 WOM available on Arbitrum, it meets the stated target. A lower settled amount leaves a shortfall. Both successful cases provide transferable WOM; neither has created Arbitrum veWOM yet. The comparison remains valid only while the quoted terms and available balances remain applicable.

Can Locked WOM Be Used for the BNB Chain Route?

Locked WOM can enter the BNB Chain bridge route only after its lock expires and the underlying tokens are redeemed.

Lock expiry permits redemption; it does not itself place WOM into a transferable wallet balance. Redeeming the underlying WOM burns the veWOM associated with that lock.

WOM lock redemption and Portal redemption act on different objects. The former recovers WOM from an expired source-chain lock. The latter completes the documented incoming bridge transfer on the destination chain.

A subsequent Arbitrum lock has its own selected amount, period, and unlock date. The BNB Chain lock’s terms do not travel with the transferred WOM. Committing the newly available tokens to that lock introduces its own restriction on when they can be reclaimed.

A WOM Bridge and a Crosschain Stablecoin Swap

The WOM Bridge and Swap entries address different asset movements within the interface. A WOM bridge relocates the governance token, while a crosschain stablecoin swap exchanges supported pool assets across networks. The existence of a stablecoin route does not establish a WOM route with the same conditions. For this acquisition task, the decisive output remains transferable WOM on Arbitrum, ready to hold or commit to a new local lock.