WETH on Monad: the canonical reference for Wrapped Ether

This is the MONAF canonical reference for WETH on Monad mainnet as of 27 October 2026. The token list names it Wrapped Ether, symbol WETH, 18 decimals, address 0xEE8c0E9f1BFFb4Eb878d8f15f368A02a35481242. It sits in the bridged-asset tables, not in the natively issued table. The extension on the token list is Wormhole NTT, bridge contract 0x36878C6FCa7e0E8a88F90dc410CfBBcA5B695C95. The docs’ own bridge link for it is MonadBridge, the 2/2 NTT front end, from ETH on Ethereum to WETH on Monad, and they describe it as bridgeable from many chains. Selected markets they name are a Uniswap WETH/MON pool and a Uniswap USDC/WETH pool. Those are not the execution pool this desk uses. Both can be true. A ticker does not tell you which pool just filled you.

What the token is, and what it refuses to be

On Ethereum, the canonical WETH contract custodies ether and withdraw() returns it. This contract is not that contract, and this chain does not hold ether as gas. Gas is MON. There is no local withdraw that turns this WETH into MON, and there is no local withdraw that turns it into ether on Ethereum. Getting back to ETH is a bridge, the one the docs name, in the direction the bridge allows, with the delay and the minimum that bridge publishes on the day you use it. A transfer of this token to your Ethereum address is a transfer on Monad to whatever account has that same hex. It does not arrive on Ethereum.

It is also not WMON. Both are 18 decimals. The token list even points both at the same NTT bridge contract. They are different tokens, different prices, different jobs. WMON is one MON. WETH is a claim, via its bridge, on ether. Approving the router for one does not approve the other. Selling one does not move the other. A wallet that stacks them in one “wrapped” row is hiding the only fact that matters, which is the contract.

Bridged ether. Eighteen decimals. Not withdrawable to MON. Not the Ethereum WETH contract.

The execution pool

This desk buys and sells WETH on PancakeSwap v3 pool 0xB02793FE655C1169A8699B4ee462F8Ac9c75E402, fee tier 500, 0.05 percent. WMON is token0. WETH is token1. A reference pool kept for price, and not used to execute, is 0x25EF1a210fF55BcEe9F8fee979aAFf6bD1bE5Bf1. The router is 0x21114915Ac6d5A2e156931e20B20b038dEd0Be7C. The measured round trip, buy and sell both on the 500 tier, is about 0.10 percent from 0.3 MON to 30 MON. The registry’s minimum entry is 0.1 MON. That is a depth fact, not a suggestion that 0.1 MON is a sensible idea. Below the bill, which the size page converts into MON, the target cannot pay the freight.

Spot, worked

slot0 is a Q64.96 sqrt price, the Uniswap v3 encoding Pancake’s fork uses. Because WMON is token0, raw WETH bought by a MON spend in wei equals that wei times the sqrt price squared, divided by 2^192. MON wei for a raw WETH balance is the reciprocal of that square. A print near 106,657 MON per WETH is the human form of the same ratio. Fifty MON at that print is about 0.0004688 WETH, about 4.688e14 raw. A stack of 0.000464 WETH is about 49.5 MON, not dust and not a full 50. The pay button spends the stack when it is at least half a MON and does not round up past the balance. Store the direction. Do not store the 106,657.

Holding, paying, and bridging

You can hold WETH as inventory and pay a USDC, WBTC, or cbBTC card with it. The path is this pool into WMON, then WMON into the other asset’s pool. Two fees, no unwrap, no bridge. The WETH button on the WETH card stays dark. Buying WETH is the WETH card paid in MON, USDC, or WBTC. A close of a MON-paid fill returns toward MON, not toward WETH. If you wanted to keep ether exposure, you either still hold this token or you buy the card again. The exit coin is the pay field of the fill unless you explicitly chose USDC on a wallet close.

Bridging in is MonadBridge, or an aggregator the docs mention as a convenience with selective coverage. Bridging out is the same family of contract, not a swap on PancakeSwap. A swap changes your Monad inventory. A bridge changes which chain custodies the exposure. The desk does not bridge. It will not call the NTT contract because you tapped Close. Close sells on the pool above. If the wallet banner says the transaction failed for 0 MON, that is a token call, which sends no native value, reverting. The usual causes are the floor, the allowance, or the quantity, and they are on the close page. They are not the bridge rejecting ether.

The first sell

The router cannot pull this token until this contract’s allowance covers the quantity. The first close is two transactions: approve, then the swap. Later closes of this same contract skip the approval. An approval on WMON, WBTC, cbBTC, or USDC does not count. If you revoke it in the token’s own interface, the next sell is a first sell again. Read the spender. It is the router above. Read the chain. It is 143. Read the raw amount against 18 decimals before you accept an interface that says “unlimited” in a friendly font.

A receipt that is actually WETH

The transfer’s contract is 0xEE8c0E9f1BFFb4Eb878d8f15f368A02a35481242. The pool, if this desk built the swap, is 0xB027…E402. The fee is 500. The other leg is WMON, unless the path continued into another asset. Decimals on the amount are 18. A raw amount near 1e8 is a bitcoin quantity that has been mislabeled. A mark of thousands of MON on a 50 MON clip is the formula run backwards. Do not close into that mark. Paste the hash into MonadVision and read the logs, not the wallet banner.