Suncex Docs
  • Summary
  • DOCUMENTATION
    • Learn about the Fuse Platform
      • Fuse Overview: vision, strategy and platform components
      • The Fuse Network Blockchain
        • Discovering the Network
        • Fuse Network Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting Fuse's Scalability
      • Fuse Token (FUSE)
        • FUSE Tokenomics
        • Exchanges, Wallets, On-Ramps and DeFi Tools Supporting FUSE
        • FUSE on Other Chains
      • Interoperability
      • Fuse Governance and Development
        • Fuse Assembly
        • Fuse Improvement Proposals (FIPs)
      • Wallets supporting Fuse Network
    • Fuse for Business
    • Things you can do on Fuse
      • Interacting with the Fuse Network Blockchain
      • Fuse Ecosystem
      • Community
      • Grants and Bounties
    • Fuse Mobile Infrastructure Use Cases
  • Developers
    • Network Details
      • Fuse Network Mainnet
      • Fuse Network Testnet Spark
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • Fuse Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on Fuse
    • Important smart contracts
      • Fuse Token
      • Fuse Dollar
      • Major Deployed Contracts
      • Bridges
        • Ethereum ↔ Fuse GoodDollar Token
        • Ethereum ↔ Fuse ERC20 Tokens
        • BSC ↔ Fuse BNB
        • BSC ↔ Fuse Native
        • BSC ↔ Fuse ERC20
        • Ethereum ↔ Fuse Native
    • How to become a validator
      • Getting started as a validator
      • Getting started as on the Spark testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
    • Join our mailing list
Powered by GitBook
On this page
  • Architecture Overview
  • Contracts
  • Source Code
  • How to use
  1. Developers
  2. Important smart contracts
  3. Bridges

BSC ↔ Fuse BNB

BNB inverse-native bridge is used to relay the BNB native token between Binance Smart Chain (BSC) and Fuse networks

PreviousEthereum ↔ Fuse ERC20 TokensNextBSC ↔ Fuse Native

Last updated 2 years ago

Architecture Overview

This bridge is two layer bridge. In the base level the Arbitrary Message Bridge (AMB) is responsible for relaying messages between the networks. On top of the AMB, the pluggable mediators implement a contract logic of token relaying of various assets. More info

The contract is called an "inverse-native" bridge, because the home and foreign network are inversed. In that case Fuse network is foreign and BSC is the home network.

Contracts

Home side of the bridge on the BSC network:

Foreign side of the bridge on the Fuse network:

BNB token on the Fuse network:

Home side of the AMB bridge on the BSC network:

Foreign side of the AMB bridge on the Fuse network:

Source Code

How to use

To send token from the BSC network:

Send native BNB token to the home bridge contract. Then you receive an equal amount of the BNB token on the Fuse network, sent from the foreign bridge contract.

To send token from the Fuse network:

  1. Approve the "BNB on Fuse" ERC20 token to be spent by the Foreign bridge.

  2. Call relayTokens function on the bridge contract

the relayTokens method will lock the ERC20 tokens on the foreign bridge. After a couple of confirmations, an equal amount of the BNB native token will be released from the home bridge contract on BSC.

https://docs.tokenbridge.net/amb-bridge/about-amb-bridge
0x51849F05090b222FFc329DC8825de0D7e26F84A1
0xA3C59198c10cB1ba9A3Ab924A23253072b393f25
0x6acb34b1Df86E254b544189Ec32Cf737e2482058
0x3A5A320a2f98a3Fe39c9040e7e3E9caA7F0D5bd6
0x1ee6E3E3d2DE779858728E157B3B9C488bA7b706
https://github.com/fuseio/tokenbridge-contracts