The Portal runs on Whitechain Mainnet at bridge.whitechain.io and on Testnet at bridge.testnet.whitechain.io. On Mainnet it currently carries USDC (Ethereum to and from Whitechain, arriving as USDC.e) and WBT (Ethereum and Tron to and from Whitechain). Its contracts on Whitechain migrated with the legacy L1 state and keep their addresses. USDT and ETH come to Mainnet in a later release.
Overview
The Portal is a centralized bridge operated by Whitechain. It moves a fixed set of assets between Ethereum, Tron, and Whitechain in minutes, and it is the only route that connects Tron to Whitechain. On Mainnet it carries USDC and WBT, and USDT and ETH come in a later release. On testnet it carries USDC, WBT, and ETH. The bridge liquidity sits in Portal contracts that Whitechain administers, and a Whitechain-operated relayer signs each transfer, so you trade self-custody for speed. This is the opposite tradeoff from the OP Stack canonical bridge, which is trust-minimized but takes at least 7 days to withdraw to Ethereum on Mainnet. Use the Portal when you need a fast transfer, a Tron route, or a token the canonical bridge does not support. Use the canonical bridge when you want a trustless path and can wait out the dispute period.Portal compared to the canonical bridge
For the trustless path and its withdrawal steps, see OP Stack canonical bridge.
Supported routes and assets
The Portal connects Ethereum and Tron to Whitechain in both directions. There is no direct Ethereum to Tron route; to move between them, bridge through Whitechain in two steps. Tokens are a fixed list configured per route. A token deposited to Whitechain arrives as its bridged representation: USDC becomes USDC.e, following Circle’s standard for bridged USDC. WBT keeps its symbol and is the native gas token on Whitechain.Mainnet
Daily limits apply when the funds are released on the destination network, per token. Transfers of the same token that arrive on Whitechain from different networks share one limit, so WBT from Ethereum and WBT from Tron count against the same 200 WBT per day. Transfers that leave Whitechain have a separate limit for each destination network. A window starts with the first transfer after the previous one expired. Values may change.
Testnet
Testnet daily limits differ by direction and change often. The app shows what you can send before you sign: Max resolves to the tightest of your balance, the remaining daily limit, and the destination liquidity.
USDT on testnet is being updated and will be documented once the route is final.
ETH is available on testnet only for now, on the Ethereum route. There is no ETH route between Tron and Whitechain.
On the Ethereum side you send native ETH, and the Bridge contract locks it. The route is registered under the WETH contract address, which serves only as an identifier, so the transaction details can name WETH. On Whitechain, ETH is a bridged ERC-20 with 18 decimals; it is not the native asset and cannot pay gas. The app’s asset picker labels it WETH (Whitechain), while your wallet shows the token symbol ETH.
How a transfer works
For the same flow screen by screen in the app, see Use the Portal bridge.- Submit the transfer on the source network and sign one transaction. You can set a recipient address different from your own.
- Wait for the source network to confirm. Confirmation takes about 12 minutes on Ethereum and about 1 minute on Whitechain.
- The relayer checks that the destination network holds enough liquidity for the token. If liquidity is short, the transfer is rejected and you can retry later.
- The relayer releases the funds on the destination network. A Whitechain to Ethereum transfer is executed by the Portal, which pays the Ethereum gas for you.
Transaction statuses
The app tracks each transfer through three stages, then marks it complete.
A transfer that runs past its expected time is labelled as delayed rather than failed. For the tracker screen, see Use the Portal bridge.
Timing
A transfer completes within minutes once the source network confirms. This is the reason to choose the Portal over the canonical bridge for a fast exit to Ethereum.
Fees and limits
The Portal charges no bridging fee today. You pay the source-network gas for your own transaction. For a Whitechain to Ethereum transfer, the Portal pays the Ethereum gas and recovers it by charging you the equivalent in WBT. It reads the current Ethereum gas price, prices a typical token transfer, and converts that cost to WBT using WhiteBIT market rates. Each token has a daily limit. The Mainnet limits are listed in Supported routes and assets; on testnet the app shows the limit that applies to your transfer. Transfers are also bounded by available liquidity on the destination network: a transfer larger than the pooled liquidity is rejected, and you can retry once liquidity is topped up.Trust model
The Portal is centralized. The liquidity sits in the Bridge contract on each network, a Whitechain-operated backend signs every transfer with a dedicated key, and each Bridge contract only accepts transfers authorized by that key. No balance moves into a Whitechain wallet, so what makes the Portal custodial is control rather than location: Whitechain administers those contracts and authorizes every release. This is what makes transfers fast, and it is the tradeoff against the canonical bridge, where a dispute game rather than an operator decides whether a withdrawal completes. During maintenance the Portal can be paused. When it is paused, transfers stop until it resumes.Contract addresses
The Bridge contract executes transfers. The Mapper defines which token pairs and directions are allowed. Both are proxy contracts. Verify every address against this page before sending.Mainnet
Addresses below are for Whitechain Mainnet (chain ID 1875), Ethereum (chain ID 1), and Tron.Bridge and Mapper contracts
The Bridge and the Mapper have the same addresses on Ethereum and on Whitechain.
Token addresses
On Whitechain Mainnet the WBT routes are registered under WWBT at
0xb044a2a1e3C3deb17e3602bF088811d9bDc762EA, not under 0x4200000000000000000000000000000000000006. The address only identifies the route: a Portal transfer into Whitechain arrives as a native WBT balance. WBT has 8 decimals on Ethereum and Tron and 18 on Whitechain, and the Portal converts the amount between them.
Testnet
Addresses below are for the current testnet deployment: Ethereum Sepolia, Tron Nile, and Whitechain Sepolia (chain ID 1874).Bridge and Mapper contracts
Token addresses
On Whitechain Sepolia the bridged USDC contract reports the symbol
USDC.e (Bridged USDC (Whitechain)); the token list names it USDC. On Whitechain Sepolia the WBT routes appear as WWBT, Wrapped WhiteBIT Coin, the ERC-20 form of the gas token with 18 decimals, because native WBT has no contract address of its own. A Portal transfer into Whitechain still arrives as a native WBT balance. The same contract is listed as WWBT in the Whitechain token list.
When to use the Portal
Disclaimer
- Test with a small amount before bridging large balances.
- Verify every contract address against this page or the official Whitechain Explorer before submitting a transaction.
- The Portal is centralized: funds in transit sit in contracts the operator controls, not in a trustless protocol.

