Links

Interoperability

Transfer tokens to and from the Fuse Network blockchain.
The Fuse team strongly believes in interoperability among public blockchains. No single platform is likely to become fully dominant in the future.
Hence, interoperability solutions enabling transfers between Fuse and other blockchains are vital for the continued growth of the Fuse platform and ecosystem.
The Fuse team has been making considerable progress in getting Fuse Network added by the leading operators. Currently, the Fuse Network blockchain is connected to other blockchains via the following multichain bridges and value transfer protocols:
1) The official Fuse bridge.
2) The Elk Finance value transfer protocol.
3) The Connext bridge (available to users via the xPollinate interface).
4) The Multichain (formerly, Anyswap) bridge.
5) The Allbridge bridge.
6) The ChainPort bridge.

The Official Fuse Bridge

The official Fuse multichain bridge connects Fuse Network to Ethereum and Binance Smart Chain (BSC). Both bridges are custodial. The bridge to Ethereum is permissionless, while new tokens must be added to the BNB Chain bridge.
On both bridges, sending tokens from the relevant blockchain to Fuse Network is not subject to fees or limits. Token withdrawals from Fuse incur a 0.05% fee on the amount bridged. Users transferring funds also need to pay the fees on the destination chain to claim their tokens from the bridge contract at the final stage of the transfer.
The bridge can be most easily accessed via the Voltage Finance interface. More information on its functioning can be found here.

The Elk Finance Value Transfer Platform

Elk Finance is not a typical multichain bridge because the only token that moves between the supported chains is ELK. If a user wants to get tokens on another chain, they can buy ELK on Elk DEX on Fuse, bridge ELK to the desired chain, and buy the desired token on that chain.
Elk connects Fuse Network, among others, to BSC, Polygon, Avalanche, Fantom, Harmony, and Moonriver. It does not currently support Ethereum. The full list of supported chains is available in the Elk DApp.

The Connext Bridge

The Connext bridge is a non-custodial multichain bridge that connects Fuse Network to Ethereum, BSC, Polygon, Arbitrum, Optimism, Avalanche, Fantom, Moonriver, and xDAI.
Please note that Connext's capacity to execute transfers depends on the availability of liquidity in a given token on the routers. Currently, the liquidity-provisioned tokens include USDC, USDT, and DAI.

The Allbridge Bridge

The Allbridge multichain bridge connects Fuse Network to many major chains, including Solana.
Allbridge's native ABR token can be transferred between Fuse Network and all the other covered chains.

The Multichain (formerly Anyswap) Bridge

The Multichain (formerly Anyswap) bridge is one of the most popular interoperability platforms in the crypto space.
Multichain has already enabled transfers for Fuse’s native FUSE token between the Fuse Network blockchain and Ethereum, BNB Chain (formerly Binance Smart Chain), and Polygon. WETH and USDC transfers via Multichain are available between Fuse Network and Ethereum. Beefy Finance’s BIFI token can be bridged to, and from almost all the networks Multichain supports. The agEUR stablecoin can be transferred between Fuse Network and Ethereum, BNB Chain, Fantom, Harmony, and Avalanche.
The bridge interface is accessible here.

The ChainPort Bridge

ChainPort's bridges are permissionless. This means anyone can bridge a token from Ethereum to any other supported chain (including Fuse Network), even if the token has not yet been ported.
In addition to Fuse Network, the list of chains added to ChainPort includes Ethereum, BNB Chain, Polygon, and Avalanche. The bridge interface can be found here.
IMPORTANT!!! Please note that ChainPort's wrappers on Fuse for the popular Ethereum-originating tokens, such as USDC, WETH, USDT, etc., will, by design, be different from the currently existing ones that were created using the FuseFi bridge.
We currently do not recommend users bridge those tokens to Fuse using ChainPort.