Bridge

The Tripools bridge moves tokens between Robinhood Chain, Ethereum, and Base using LayerZero V2. Transfers are burn-and-mint: your balance is burned on the source chain, independently verified by LayerZero DVNs, and minted to your wallet on the destination chain. There are no wrapped tokens and no custodial operator — the same TripoolsToken contract at the same CREATE2 address is native on every chain.

How to bridge

1. Open the Bridge page and connect your wallet.
2. Select the source chain and token, then the destination chain.
3. Enter the amount. The UI quotes the LayerZero fee upfront.
4. Confirm the transaction on the source chain. Tokens burn immediately; delivery on the destination chain typically completes within a few minutes depending on DVN confirmation time.

Transfers always go to your connected wallet address. Make sure your wallet is on the source chain before signing — the app will prompt you to switch if needed.

Who can bridge

Any holder of a Tripools-launched token can bridge their own balance at any time. The bridge is not limited to the factory or the keeper — it's the same path used during Triple Launch to move secondary-chain shares, and the same path arbitrageurs use to align prices across chains.

Supported chains

• Robinhood Chain — chain ID 4663, LayerZero EID 30416
• Ethereum — chain ID 1, LayerZero EID 30101
• Base — chain ID 8453, LayerZero EID 30184

Security model

Destination mints only happen inside _lzReceive, which the LayerZero endpoint invokes after configured DVNs attest to the matching source-chain burn. Tripools pins explicit DVN configuration on every send/receive pathway rather than relying on LayerZero defaults. Global supply is capped by construction: one mint at launch, then only verified burn-and-mint transfers — invariant-tested to sum to exactly totalSupply.

Bridge protection: 50% fee in the first hour

For price stabilization right after launch, any user-initiated bridge of a token still within its first hour of existence diverts 50% of the bridged amount to the protocol treasury instead of bridging it. It's enforced by TripoolsLzBridgeV2 on the source chain, before the LayerZero message is even sent — there's no separate step to skip and no way around it from the UI. The 1-hour window is clocked from the token's primary-chain launch timestamp, the same timestamp registered on every chain, not each chain's own deploy time.

Without this, a fresh launch's liquidity is thin enough that fast cross-chain arbitrage in the first few minutes can whipsaw the price on every chain the token exists on. Taxing early bridges — while leaving normal same-chain trading exactly as it is — keeps that volatility contained to a single chain during the riskiest window instead of letting it propagate everywhere at once.

The withheld amount is auto-sold for ETH directly against the token's own pool (capped at roughly a 90% price-impact ceiling so one bridge can't dump the pool outright) and sent to the treasury in ETH. If the sell can't fully complete — the price cap is hit, the pool has no liquidity yet, anything — whatever doesn't sell is swept to the treasury as plain tokens instead, so the treasury always receives the full 50% in value either way. This fee never touches the factory's own automatic secondary-chain allocation bridges during Triple Launch — only bridges you initiate yourself. After the first hour, bridging that token is back to gas + the LayerZero quote, with no protocol surcharge.

Fees

Bridging costs gas on the source chain plus a LayerZero messaging fee quoted on chain via quoteSend. Beyond the first-hour bridge protection above, Tripools does not add a separate protocol fee on top of the LayerZero quote.