FURL bridge
Cross-chain FURL, when it is real.
FURL exists on Solana and nowhere else. There is no bridge contract, no token on any other chain, and no FURL locked. This page describes what is planned and what is stopping it — it is not a bridge you can use yet.
Not deployed — FURL is Solana-only
No Wormhole NTT contract has been deployed on any chain. No CanonicalFURL ERC-20 exists on Arbitrum, Base, or anywhere else. Zero FURL is locked. Any site offering to bridge, swap, or sell FURL on another chain today is not offering this token.
Verify the one real mintChains
| Chain | Role | Token | Status |
|---|---|---|---|
| Solana | Hub (locking) | FYatJq71zq…zV3gY1 | Live |
| Arbitrum One | Spoke (burning) | not deployed | Planned |
| Base | Spoke (burning) | not deployed | Planned |
FURL is a Token-2022 mint with 6 decimals and a fixed 1,000,000,000 supply. Every spoke would match those decimals exactly — an 18-decimal spoke against a 6-decimal hub would mis-scale every bridged amount by a factor of a trillion.
How it would work
Solana is the hub
FURL's canonical 1,000,000,000 supply and its published tokenomics live on Solana. Bridging locks FURL there and mints a representation on the destination chain. The accounting stays in one place.
EVM spokes burn and mint
Each spoke runs a CanonicalFURL ERC-20 at 6 decimals — matching the Solana mint exactly. Bridging out burns the spoke tokens and unlocks the Solana originals. Spoke-to-spoke never touches Solana.
Supply cannot exceed the cap
The spoke contract refuses to mint past 1,000,000,000 FURL, so a compromised bridge manager cannot print supply that no locked balance backs. The cap is enforced by the contract, not by a promise.
The invariant is published, not asserted
Locked FURL on Solana must equal the sum of every spoke's supply. /api/token/furl/supply/cross-chain evaluates that on every request so anyone can check it — which is the only thing that ever catches a bridge minting tokens nothing backs.
What is stopping it
In order. The first one is not about money.
Treasury custody comes first
100% of FURL sits in one deployer-controlled account. Bridging before that is fixed would multiply a single-key exposure across every chain it reaches, rather than reducing it.
Deployment is unfunded
The NTT program accounts need roughly 1.5–2.5 SOL on Solana; the deployer holds 0.048 SOL. No funded EVM deployer key exists for Arbitrum or Base.
No liquidity on any chain
A bridge moves a token between chains; it does not make it tradable. Without pools, FURL would be bridgeable and still unsellable everywhere. That is a separate and far larger cost than deployment.
Security parameters undecided
The transceiver threshold, the manager owner and the pause authority are all open decisions. A bridge whose pause authority is a single hot key has no pause authority.
For integrators
The cross-chain supply breakdown and the invariant check are served as JSON. Today it reports one chain, zero locked, and NOT_APPLICABLE — because there is no second side to reconcile against yet.
GET /api/token/furl/supply/cross-chain