What runs today
Bitcoin Swap runs Hyperledger Besu with QBFT consensus. Its native coin, BTCw, is quoted at the BTC/USD rate and pays for gas at a fraction of a cent. The chain hosts three kinds of assets: bridged assets locked 1:1 on Arbitrum One (WBTCw backed by WBTC, USDC.e backed by USDC), USDw, the chain's US-dollar unit of account, and oracle-priced tracker tokens following crypto assets, US equities and ETFs. Users trade them on oracle market makers, two families of continuous-liquidity pools and a Uniswap V2 venue; an ownerless router reaches any asset in one transaction.
Six principles
Proof over promise
Each statement about backing, supply, volume or yield maps to an on-chain quantity anyone can read with a public RPC call. Backed value and protocol inventory are reported as separate numbers.
Backing comes from outside
A backed token is backed by an asset the system cannot create: WBTCw by WBTC, USDC.e by USDC, both locked on another chain under rules no key can override.
Rewards come from revenue
Rewards are funded by income the protocol has already collected — swap fees, spreads and bridge fees — so they grow with real use.
Rules before discretion
Order caps, oracle bounds, staleness halts and inventory limits are written into contracts before they are needed.
Keys cannot move backed funds
The WBTC and USDC.e bridge routes are sealed: their verifier and remote router are fixed at deployment. An administrator can pause a route or manage its allowlist, and nothing else.
Stability first, then decentralisation
The network is run by its founding operator through the launch phase, until 22 December 2026, and then hands control out step by step on published milestones.
Check it yourself
Read the chain
- Proof of reserve — WBTCw and USDC.e supply against WBTC and USDC locked on Arbitrum, read in your browser.
- Transparency — genesis, validators, keepers and their addresses.
- Trust model — who can do what on each contract.
- Market — price, depth, trades and volume of every asset, with the keeper wallets' volume in its own column.
Build on it
- Developer docs — network settings, API, SDK, deploy guide.
- contracts.json and tokenlist.json — machine-readable registry.
- Explorer — the core contracts in contracts.json are source-verified with a full match.
- Ecosystem — apps live on chain 482120.
Figures on this page are read live from the chain and the public API when the page loads. Text follows whitepaper v0.2, sections 1 and 2.