Supported chains
- Ethereum
- BNB Chain
- Arbitrum
- Solana
- More on the roadmap, check the AsterDEX docs.
Deposit flow
- User sends supported asset to the bridge contract on the origin chain.
- Validator nodes observe the deposit.
- Confirmation threshold: 3 of 4 validator nodes must verify before the bridge credits the user's Aster Chain account.
- Typical latency: under a minute for fast chains, longer for ETH.
Withdrawal flow
- User submits withdrawal intent on Aster Chain.
- Confirmation threshold: 2 of 3 validator nodes must verify.
- Withdrawals are batched. Multiple users' withdrawals can settle in a single destination-chain transaction to amortize gas.
Trust assumptions
- The bridge is custodial in the sense that the validator set holds the cross-chain balance. You trust the validator set to honor withdrawals.
- This is consistent with the PoSA consensus model: economic skin in the game (locked ASTER) backs the validators. See validators explained.
- There is no light-client bridge or zk-bridge in place today.
Supported assets
- Stablecoins: USDT, USDC, USDF
- Native tokens: ETH, BNB, SOL
- ASTER (bridges from BNB Chain)
- Check docs.asterdex.com for the full list and per-chain caps.
Common gotchas
Wrong-chain send
Bridge contract addresses differ per chain. Always verify the destination chain in your wallet UI before signing.
Stuck deposit
If a deposit does not arrive within 10 minutes for fast chains, check the explorer on the origin chain first. Most stuck deposits are pending L1 confirmation, not bridge issues.
Withdrawal queue
In periods of high outflow, batched withdrawals can queue. AsterDEX exposes the queue length in the UI.
Further reading
Last reviewed May 2026.
Corrections → @aster_scan