Use Tuven

Bridge supported assets

Understand the BSC ↔ Tuven transfer flow and how destination delivery is verified.

The bridge connects registered ERC-20 assets on BNB Smart Chain with their mapped bridged tokens on Tuven. The interface is available only when the source BridgeLock and destination BridgeMint contracts are configured. A bridge route is not automatically a conversion into native USDX.

BSC to Tuven

1. Select BSC → Tuven and enter the ERC-20 token address on BSC. The app verifies that the token has a registered destination mapping.
2. Review the token decimals, your balance, and the current bridge fee. Connect to BSC and keep BNB available for gas.
3. Approve the source BridgeLock for the required amount, then confirm the lock transaction.
4. The relayer observes the Locked event and mints the mapped token on Tuven to the same wallet address.

Tuven to BSC

Select Tuven → BSC and enter the bridged token’s Tuven address. The app checks its source-token mapping, then submits a burn on Tuven. The authorized relayer unlocks the corresponding source token on BSC. The recipient is your connected wallet address on both networks.

Follow the full transfer

Source confirmation is only the first half of a bridge transfer. The app stores the pending transfer on this device and checks for a matching destination Minted or Unlocked event, including its nonce, recipient, token, and amount. It marks delivery complete only after that event is observed.

If you close the page, return on the same browser to resume checking the saved transfer. If the relayer or destination RPC is unavailable, the transfer remains pending. Keep the source transaction hash and check both network explorers before attempting another transfer.

Fees and supported routes

The fee is read from the active source-side bridge contract. It is charged on the bridged amount and can be configured by the contract owner. Source events report the net amount to deliver. Network gas is separate from the bridge fee.