0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

Why Bridged Tokens Have Different Contract Addresses: The Cause

0
Posted at

Monad bridge moves supported assets between Ethereum and Monad by coordinating a token action on one chain with a mint on the other. When you bridge an Ethereum token to Monad, the token you receive can have a different contract address because it lives in a separately deployed contract.

Say you lock an Ethereum token in a bridge contract. A verified bridge message reaches Monad, where a token contract mints the corresponding balance to your wallet. The Monad bridge flow uses that destination contract to represent the bridged asset. For more on what each model means for holders, read Monad bridge lock-and-mint versus burn-and-mint risk; it adds the backing trade-offs behind this transfer.

The destination token needs its own contract

A bridged token has a different address because Ethereum’s contract state does not exist on Monad. Each EVM chain keeps its own state, so the Ethereum token contract must be deployed separately on Monad before it can mint there.

Lock-and-mint and burn-and-mint both need this destination token contract. With lock-and-mint, the bridge locks tokens on Ethereum, then the Monad contract mints tokens when the message is verified. With burn-and-mint, the source tokens are burned, and the Monad contract mints the corresponding balance. In either case, the bridge message triggers a mint on Monad.

Your wallet address can stay the same across both chains because an externally owned account (EOA) address comes from your public key. A token contract address comes from its deployment, so it follows different rules.

Deployment determines the contract address

For a normal CREATE deployment, the new contract address derives from the deployer’s address and its transaction nonce. Deploying the token separately on Monad will usually use a different deployer or nonce, producing a different address.

CREATE2 can produce the same address on multiple chains, but only when the issuer deploys deterministically using the same deployer, salt, and initialization-code hash on each chain. The issuer must arrange those inputs to match. Without that setup, a different address is the expected result.

So the address difference does not mean your wallet changed or that the bridge skipped the destination token. It means the bridged balance belongs to a contract deployed on Monad, with an address set by that deployment. Identical addresses are possible when the issuer uses matching CREATE2 inputs; otherwise each chain’s token contract has its own address.

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?