Skip to main content

Bridging Tokens

Bridging is the process of moving tokens from one blockchain to another. When you use a bridge to move tokens between incompatible blockchains, the tokens are wrapped and converted to a derivative token for the target blockchain (for example, Wormhole-minted tokens or ZetaChain ZRC-20 tokens, described below). You can transfer tokens from other blockchains to Sui, or transfer SUI tokens to other blockchains.

Sui supports bridging through Sui Bridge, Wormhole Connect, Wormhole Portal Bridge, and ZetaChain. Each bridge offers different features and capabilities to suit various use cases. To confirm the Sui address of a bridged token, see the Token address list.

Sui Bridge​

Sui Bridge is the native bridge for the Sui network, built into the core architecture. It provides optimal integration and operation, enabling the movement of digital assets between Sui and other blockchains while preserving security and maintaining interoperability. Sui Bridge supports secure and efficient transfer of native and wrapped ETH to and from Sui, leveraging Sui's capabilities to offer fast transactions, lower costs, and a decentralized architecture.

Bridge tokens at bridge.sui.io.

Operation and governance​

Sui Bridge is operated and governed by Sui validators, the same set that secures the Sui network. Bridge transfers and other actions require validator signatures with a threshold of voting power. Governance is handled by validator voting.

To learn how to set up a Sui Bridge full node, see Sui Bridge Validator Node Configuration.

Which assets does Sui Bridge support?​

Sui Bridge supports bridging between Sui and other networks with the following assets:

AssetDescription
Wrapped Bitcoin (WBTC)Tokenized representation of Bitcoin.
Lombard Staked Bitcoin (LBTC)Bitcoin liquid staking token by Lombard Finance.
Ethereum (ETH)Native cryptocurrency of the Ethereum network.
Wrapped Ethereum (WETH)Tokenized representation of native ETH.
Tether (USDT)Stablecoin pegged to the US dollar.

What are the Sui Bridge package IDs and contract addresses?​

The following package IDs and addresses are reserved for Sui Bridge:

AssetAddress/ID
Sui Bridge package on Sui0xb
Sui Bridge object on Sui0x9
Sui Bridge contract on Ethereum Mainnet0xda3bD1fE1973470312db04551B65f401Bc8a92fD
ETH on Sui0xd0e89b2af5e4910726fbcd8b8dd37bb79b29e5f83f7491bca830e94f7f226d29::eth::ETH
ETH on EthereumNative Ether
WETH on Ethereum0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

Source code​

Sui Bridge is open source:

Audits​

Audit reports:

How does the global limiter work?​

A limiter protects funds by constraining the total value of assets leaving Sui Bridge in a 24-hour window. It tracks value hourly and aggregates from the last 24 hours, refreshing every hour. The limit applies globally and varies by direction (Ethereum → Sui versus Sui → Ethereum). It also caps the maximum single transfer.

Limits are set by validator committee vote and announced in the mn-validator-announcements channel on Discord. The global limit is currently 16millionfromEthereumtoSuiand16 million from Ethereum to Sui and 7 million from Sui to Ethereum per 24 hours.

Asset pricing​

Sui Bridge v1 uses static pricing to calculate limits. ETH is priced at 2,600.OneETHconsumes2,600. One ETH consumes 2,600 of the limit. The validator committee governs pricing through voting.

What are the minimum and maximum transfer amounts?​

There is no minimum transfer, but very small fractions can be rounded down. For ETH and WETH, reduced precision of eight decimals rounds 10.0000000000000001 down to 10.

TokenMinimal value
ETH0.00000001 ETH
WETH0.00000001 ETH

The maximum transfer equals the global USD limit. See Global limiter.

When is a bridge transfer complete?​

Bridge transfers are not instant. Each direction has a different finality requirement:

  • Ethereum to Sui: The bridge waits for a configurable number of Ethereum block confirmations before minting tokens on Sui. This confirmation depth protects against Ethereum chain reorganizations. The exact depth is set by the bridge validator committee.
  • Sui to Ethereum: The bridge waits for Sui transaction finality before releasing tokens on the Ethereum side. The Ethereum transaction itself then requires Ethereum block confirmations before funds are available.

When you build an app that credits users for bridged assets (for example, an on-ramp flow where a user bridges ETH to Sui), do not credit the user until the bridge transfer is fully confirmed on the destination chain. Poll the bridge status to check whether the transfer is complete before updating your app state.

caution

Do not assume a bridge transfer is complete based on the source chain transaction alone. A source chain transaction confirms that the user initiated the bridge, but tokens are not available on the destination chain until the bridge validators process and finalize the transfer. Crediting users prematurely exposes your app to double-spend risk if the source transaction is reorganized.

Wormhole Connect​

Wormhole Connect lets you bridge tokens from any supported Wormhole chain into Sui, with an extra drop of SUI for gas fees. Developers can also embed Connect in their own websites and apps.

tip

See Cross-Chain Token Transfers with Wormhole Connect on the Wormhole website for a tutorial.

Supported assets​

Wormhole Connect supports lock-and-mint bridging for ETH, WETH, USDC, MATIC, WMATIC, BNB, WBNB, AVAX, WAVAX, FTM, WFTM, CELO, GLMR, WGLRM, and SOL across Ethereum, Polygon, BSC, Avalanche, Celo, Moonbeam, Solana, and Sui. Bridged tokens are received as Wormhole-minted tokens on the destination chain. See the Wormhole token list. Some tokens support swapping on destination DEXs.

Features​

Automatic relay: On EVM chains and Sui, Wormhole Connect can pay destination-chain gas automatically. Users only pay gas on the source chain.

Gas drop-off: Users can pay an extra fee on the source chain to receive a small amount of native gas on the destination chain. For example, bridging USDC from Ethereum to Sui can include a fee in USDC to receive SUI for gas. This feature is supported on EVM chains and Sui.

See the Wormhole FAQ for details.

Wormhole Portal Bridge​

The Portal Bridge, powered by Wormhole, supports bridging assets from any of the 22 supported Wormhole chains.

ZetaChain​

ZetaChain enables omnichain smart contracts and cross-chain messaging between Sui and other blockchains. The ZetaChain protocol supports bridging digital assets and sending arbitrary messages across Bitcoin, Ethereum, Polygon, BSC, Avalanche, and other major chains.

Supported assets​

ZetaChain supports native cross-chain transfers for tokens such as:

  • Bitcoin (BTC): Native Bitcoin transfers through HTLC

  • Ethereum (ETH): Native ETH and ERC-20 tokens including USDC, USDT, WBTC

  • Polygon (MATIC): Native MATIC and Polygon tokens

  • BSC (BNB): Native BNB and BEP-20 tokens

  • Avalanche (AVAX): Native AVAX and Avalanche C-Chain tokens

  • Layer 2 chains: Arbitrum, Optimism, Base

Assets bridged through ZetaChain are represented as ZRC-20 tokens on the ZetaChain network and can be transferred to any connected chain.

See the ZetaChain supported networks for the complete list.

Omnichain messaging​

Beyond asset transfers, ZetaChain's Universal App framework enables smart contracts to communicate across all connected chains. Developers can build applications that:

  • Call functions on contracts across multiple blockchains.

  • Read and write state across chains through ZetaChain's validators.

  • Execute complex multi-chain workflows in a single transaction.

How it works​

ZetaChain uses a proof-of-stake validator network to observe transactions on external chains and relay messages between them. When you initiate a cross-chain transaction:

  1. You interact with a gateway contract on the source chain (Sui or any supported chain).

  2. ZetaChain validators observe and verify the transaction.

  3. The validators execute any omnichain contract logic on ZetaChain.

  4. The validators trigger the corresponding action on the destination chain.

All cross-chain operations are handled automatically without manual intervention.

Gas handling​

ZetaChain provides flexible gas payment options:

  • Pay on source chain: Pay all fees upfront on the source chain in ZETA, USDC, or USDT.

  • Automatic gas drop: Receive native tokens on the destination chain for transaction fees.

  • Custom gas logic: Implement application-specific gas payment models.

Gateway contracts​

Interact with ZetaChain through gateway contracts deployed on each supported chain:

Athens Testnet

  • Sepolia (Ethereum): 0x0c487a766110c85d301d96e33579c5b317fa4995

  • Base Sepolia: 0x0c487a766110c85d301d96e33579c5b317fa4995

  • Amoy (Polygon): 0x0c487a766110c85d301d96e33579c5b317fa4995

  • BSC Testnet: 0x0c487a766110c85d301d96e33579c5b317fa4995

Always verify gateway addresses from the official ZetaChain documentation before integrating.

Getting started​

Install the ZetaChain CLI:

npm install -g zetachain

Explore example contracts and tutorials:

View transactions on the ZetaChain explorers:

Token address list​

The following table lists the address for each token type. Confirm token legitimacy by verifying the address matches.

TokenAddress
CELO0xa198f3be41cda8c07b3bf3fee02263526e535d682499806979a111e88a5a8d0f
WMATIC0xdbe380b13a6d0f5cdedd58de8f04625263f113b3f9db32b3e1983f49e2841676
WBNB0xb848cce11ef3a8f62eccea6eb5b35a12c4c2b1ee1af7755d02d7bd6218e8226f
WETH0xaf8cd5edc19c4512f4259f0bee101a40d41ebed738ade5874359610ef8eeced5
USDC0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf
USDT0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c
WBTC0x027792d9fed7f9844eb4839566001bb6f6cb4804f66aa2da6fe1ee242d896881
WAVAX0x1e8b532cca6569cab9f9b9ebc73f8c13885012ade714729aa3b450e0339ac766
WFTM0x6081300950a4f1e2081580e919c210436a1bed49080502834950d31ee55a2396
WGLMR0x66f87084e49c38f76502d17f87d17f943f183bb94117561eb573e075fdc5ff75
WSOL0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8
USDCsol0xb231fcda8bbddb31f2ef02e6161444aec64a514e2c89279584ac9806ce9cf037