Move Flo tokens across chains. One call.
Bridge runs on LayerZero v2 with a 3-of-4 DVN quorum — four independent verifiers attest every message, any three must agree before delivery. Source burn, DVN-validated message, destination mint, all in a single API call.
The full Bridge spec lives in the docs
Source burn, DVN-validated message, destination mint — all in one call. Route matrix, failure semantics, and the 3-of-4 DVN quorum detailed in the reference. Python and Node.js tabs, copy-ready.
How bridging works
Burn on source, validate via LayerZero, mint on destination. The supply accounting stays balanced throughout — every bridge is a net-zero change to total Flo token supply.
Source burn
Flo burns the Flo tokens on the origin chain. The burn is recorded in the SPV ledger so the supply accounting stays balanced.
LayerZero message · 3-of-4 DVN
Flo posts a LayerZero v2 message from the source chain to the destination. Delivery requires a 3-of-4 DVN (Decentralized Verifier Network) quorum — four independent verifiers attest, any three must agree before the message is relayed. No single verifier can sign a fraudulent bridge.
Destination mint
On the destination chain, Flo mints the Flo tokens to the wallet you specified. The entire round trip completes in ~30 seconds on L2 routes.
What bridge gives you
No multi-step UX, no router contracts to integrate, no liquidity fragmentation across chains. Same token, same holder, new chain.
Every Flo token, every supported chain
Bridge AAPL, TLT, APCI, or any other Flo token. The same API works across every supported origin and destination.
LayerZero v2 · 3-of-4 DVN quorum
Flo bridges run on LayerZero v2 with a 3-of-4 DVN security config — four independent verifiers attest every message, any three must agree before a mint can land on the destination chain.
One call, one transaction
The user signs once. Flo orchestrates the source burn, the LayerZero message, and the destination mint. No multi-step UX.
Developer pays gas
You cover gas on both chains — which keeps costs transparent. L2s keep the bill low. No hidden fees from Flo.
Full lifecycle webhooks
Subscribe to bridge.queued, bridge.sent, and bridge.delivered events to drive in-app progress indicators and reconciliation.
Symmetric routes
Every route is bidirectional. If you can bridge A → B, you can bridge B → A with the same API shape.
Supported routes
Live across Base, Arbitrum, and Ethereum — every route bidirectional. Polygon, Solana, and Optimism are in active deployment. If you need Flo on a chain that isn't here, drop us a line at chains@flo.finance — we move based on developer pull.
| From | To | ETA |
|---|---|---|
| Ethereum | Base | ~30 seconds |
| Ethereum | Arbitrum One | ~30 seconds |
| Base | Arbitrum One | ~30 seconds |
| Base | Ethereum | ~1 minute |
| Arbitrum One | Ethereum | ~1 minute |
| Arbitrum One | Base | ~30 seconds |
Build once. Ship on every chain.
Let your users mint on one chain and move anywhere the API supports — without breaking the underlying SPV accounting.