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 Does a Bridged Token Have a Different Contract on Each Chain?

0
Posted at

After a transfer, you may see the same token name at a new address because each chain keeps its own ledger and needs its own token contract. The bridge deploys that contract on the destination chain, where it has separate state and supply.

  • You’ll understand why the addresses differ and when they can match.
  • You’ll need to verify the token address for the chain you plan to use.

Why does each chain have its own token contract?

A token contract records balances and transfers on one chain. Ethereum cannot read or share the contract storage on Polygon or Solana, so a bridge or issuer deploys a separate token representation on each network it supports.

RenBridge issued renBTC as distinct contracts on Ethereum and Polygon, and as a mint on Solana, with the versions backed by the same BTC reserve. For background on the protocol behind that arrangement, ren protocol adds context on how RenBridge connected assets across chains.

On EVM chains, the deployment process determines the contract address. With CREATE, the address comes from the deployer’s address and its nonce, a counter that advances with deployments. With CREATE2, defined in EIP-1014, it comes from the deployer, a chosen salt, and the hash of the contract’s initialization code.

Addresses rarely match across chains because the deployer, nonce, salt, or initialization code may differ. But a project can deploy at the same address on several EVM chains by using CREATE2 with matching inputs, or by arranging a matching deployer nonce. Those are still separate contracts: each keeps its own balances and supply.

Think of each chain as a separate branch office keeping its own account book. A bridge can arrange for each office to issue a token backed by the same reserve, but a shared name or backing does not make the account books one system. The analogy stops at the bookkeeping: blockchains verify transfers through code and network rules, not office staff.

Take renBTC: a user locks or transfers value through the bridge, and the destination chain records the corresponding token in its own contract or mint. A token created by another bridge may also be called renBTC or wrapped BTC, yet have a different address and backing arrangement. Such versions are not interchangeable; an exchange or app must support the specific contract on the specific chain.

Solana uses a different structure: a token is identified by a mint account, whose address is written in base58. It is not an EVM contract address, even when the token represents the same asset.

Related questions

How do I find the official token address on a given chain?

Find the address from the project or bridge’s official channel, making sure the selected network matches the one where you’ll receive or use the token. Confirm it in that chain’s block explorer and check that the contract or mint matches the project’s stated details. A familiar name or ticker alone is not enough.

Can I send a bridged token to my same wallet address on another chain?

Often, an EVM wallet uses the same address on multiple EVM chains, but the token stays on its original chain until a bridge transfer moves it. Select the destination network and use a supported bridge route. Solana uses base58 addresses, so confirm your wallet supports the asset and destination before sending.

Before you transfer, verify both the destination chain and that chain’s official token 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?