Bridge xTOPAZ
xTOPAZ uses LayerZero OFT transfers to move shares between BNB and a spoke. The share backing remains on BNB. A bridge moves xTOPAZ; it does not change it into TOPAZ or another asset.
Bridging is live. Bridge xTOPAZ connects BNB with Robinhood Chain, Base, Ethereum and Arc. Each route checks peers, limits, fees and current contract state before sending. Source confirmation and destination delivery are separate. Network availability.
Every route goes through BNB
| Journey | Legs |
|---|---|
| BNB to a spoke | One OFT transfer from the hub adapter to that spoke |
| A spoke to BNB | One OFT transfer back to the hub adapter |
| One spoke to another | Return to BNB, then send from BNB to the destination spoke |
The bridge form always has BNB Chain on one side. Choose Robinhood, Base, Ethereum or Arc as the source and BNB becomes the destination; choose BNB as the source to send to any of those four networks. The arrow reverses the direction. To move between spokes, first bridge to BNB and wait for delivery, then start a new transfer from BNB. The form does not offer a two-step journey.
Only liquid xTOPAZ can bridge. Withdraw a spoke stake first if your shares are staked. BNB veTOPAZ NFTs and LP tokens are not sent through the xTOPAZ bridge.
What the bridge does
On BNB, the adapter locks canonical xTOPAZ when sending to a spoke and unlocks it on return. The spoke OFT mints on receipt and burns on departure. The hub tracks each spoke's bridged supply, including shares that have arrived but have not been staked.
The bridge's shared precision is six decimals. For an 18-decimal xTOPAZ token, quantities below a multiple of 10^12 raw units cannot be sent. Review both the amount actually sent and the dust left on the source; bridging does not promise delivery of the entire typed decimal amount.
Review before sending
- Confirm source and destination networks and the recipient on the destination. A matching address string is not proof that a smart wallet is deployed or controlled there.
- Read the fresh send amount, receive amount, native messaging fee and source gas requirement. Keep the source network's native token available for gas and the messaging fee.
- Check both ends of the route, their pause state and remaining capacity. Capacity can change after the quote.
- On BNB, the bridge adapter receives an unlimited xTOPAZ allowance when the existing allowance is insufficient. A direct send from the spoke OFT burns the caller's shares without a separate ERC-20 spender approval. Confirm the review once: Topaz automatically requests any approval, waits for its receipt, checks and simulates the bridge, then requests the bridge transaction. Your wallet still asks you to confirm each transaction. Changes to the reviewed transfer or fee limit require a new review.
Confirmation is not delivery
The source transaction can confirm while the packet is still in flight. Track the source hash and LayerZero packet identifier. The interface's saved-transfer checks verify source events and the actual sent amount, then use the LayerZero status report and the named destination receipt to check delivery.
A source receipt alone is not enough to say “received.” Nor does an unavailable status mean the transfer failed. Before retrying a send, establish whether the original transaction was accepted so that you do not send a second transfer accidentally.
Saved single-hash checks can run on the original chain after a network switch or feature rollback. Records are local to the browser; keep the hash yourself. Reload recovery for ambiguous batches and every historical RPC condition is not established.
Delays, pauses and limits
A paused route or exhausted receive capacity can hold a packet for retry after conditions change. The hub inbound policy limits the rate at which a spoke can return shares; use current on-chain availability rather than assuming a fixed limit or delivery time. Configured limits may change, and bridge recovery is not a guaranteed instant refund.
For a delayed transfer, inspect its original source receipt and message status, then follow that packet's supported retry path. Do not use the Private Swap refund flow: it belongs to another service and another asset journey.
Optional actions after delivery
The contracts also define bridge-and-stake on a spoke and bridge-back-and-redeem on BNB. If the destination action cannot run, their composers are designed to deliver liquid xTOPAZ to the designated recipient instead. Receiving shares does not establish that staking or redemption succeeded.
Composed destination actions are outside the current interface flow. Use a plain bridge transfer, wait for delivery, then stake locally or redeem on BNB. Spoke staking · BNB redemption.