What Happens to ETH When a Bridge Locks It
What happens to my ETH on the Monad bridge? It stays locked on Ethereum while an equal wrapped ETH token is minted on Monad after verification.
By Web3 Hub Newsroom3 min read
The Monad bridge leaves your ETH locked on Ethereum and gives you an equal wrapped ETH balance on Monad after verification. The Monad bridge is a concrete example of a cross-chain transfer app, with support for moving assets between Ethereum and Monad. In a lock-and-mint transfer, your ETH is deposited, verified and represented on Monad; seeing the wrapped balance there tells you delivery is complete.
Say you start with ETH in your wallet on Ethereum. The details here are illustrative: the route’s transfer method determines whether ETH is locked and represented by a wrapped token, or paid out from a liquidity pool.
Your ETH stays on Ethereum while the transfer is verified
At deposit, the source-chain transaction sends your ETH into the bridge contract on Ethereum. You pay the Ethereum transaction’s gas in ETH. Once that deposit is confirmed, the ETH remains locked there; it does not travel across chains.
Next comes the wait. Wormhole says its Guardians wait for source-chain finality, then sign an attestation of the transfer. With an Axelar route, validators verify the source-chain message before it is routed to the destination contract. The route determines which verification system applies, and the wait can vary with Ethereum finality, attestation and delivery.
After verification, a relayer submits the proof to the Monad-side contract. That contract mints the corresponding wrapped ETH to your wallet on Monad. Wormhole describes this lock, attest and mint sequence in its transfer flow; Axelar describes its validator verification and relaying in its message flow.
A confirmed deposit means a delay is not ETH lost in transit
If the deposit is confirmed but the wrapped balance has not arrived, the transfer is waiting on a later stage: finality, attestation or the relayer’s submission. Your ETH remains on Ethereum during that wait. A stuck lock-and-mint transfer is therefore a delivery delay, not ETH disappearing between chains.
Use the transaction records to identify the stage. A confirmed Ethereum deposit shows the lock happened; a destination mint shows delivery completed. Until that mint appears, you do not yet hold the wrapped ETH on Monad.
- Have ETH available for the Ethereum deposit and its gas, because the source transaction must be submitted there.
- Have MON for activity on Monad, because gas on that network is paid in MON.
- Keep the Ethereum transaction record, because it shows whether the deposit was confirmed.
- Check for the wrapped ETH balance on Monad, because that confirms delivery rather than just a completed deposit.
Once a lock-and-mint deposit is confirmed, the ETH backing the transfer stays in the Ethereum contract while verification and delivery finish. On arrival, you hold wrapped ETH on Monad, and MON is what you need to pay Monad gas.