I'm developing a ERC20 token to deploy on BSC network. But the client requests that the token should be on both BSC & Ethereum networks. I did a research and found out these methods.

  • Binance bridging (Looks like this is only for the binance listed tokens, so not applicable)
  • Deploying on both networks on the same contract address (But the two tokens balances, prices, holders will be independent)

Is there any standard way of doing this, possibly with capabilities of syncing two contracts somehow? Any resource or suggestion on this would be very helpful.

1 Answer 1


You need to deploy compatible token contracts on both networks, ideally not ERC-20 but ERC-677, and then set up a two-way bridge on both networks.

You should look into ChainSafe's Chain Bridge or POA Network's Token Bridge. I would recommend an AMB with an ERC-677-to-677 module.

Make sure the bridge mode is set to AMB_ERC_TO_ERC:


With regards to having the same contract address on both networks, this is easy: just use the same private key with the same transaction nonce to deploy the contract.

  • Thank you very much for your answer! Could you please tell me how can I deploy a wrapped token on one network that points to the actual token on another network? If it's possible, what are the pros/cons of wrapping compared to bridging? Jan 9, 2022 at 16:05
  • Would using the bridge approach mean the two tokens share the same maximum supply? Why do you suggest ERC677 over ERC20? Thank you!
    – Filip Lauc
    Jan 12, 2022 at 9:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.