Skip to main content
Status: Live on Mainnet The 0xio Bridge is live at bridge.0xio.xyz. Bridge OCT between Octra and Ethereum.

​
Overview

The 0xio Bridge connects the Octra Network with Ethereum, enabling bidirectional transfers between native OCT and wrapped OCT (wOCT, an ERC-20 token on Ethereum). Unlike intent-based bridges, the 0xio Bridge uses a light client architecture: an Octra Light Client contract on Ethereum verifies Merkle proofs of Octra transactions, providing trustless verification without relying on external oracles.

​
How It Works

​
OCT → wOCT (Octra to Ethereum)

1

Connect Wallets

Connect your 0xio wallet (Octra) and EVM wallet (MetaMask, Rabby, etc.)
2

Lock OCT

Lock OCT in the BridgeVault contract on Octra with your Ethereum destination address
3

Wait for Bridge Header

The bridge relayer submits epoch roots to the OctraLightClient on Ethereum (~2-5 minutes)
4

Claim wOCT

Once the epoch root is verified, claim your wOCT using a Merkle proof

​
wOCT → OCT (Ethereum to Octra)

1

Approve wOCT

Approve the EthereumBridge contract to spend your wOCT
2

Burn wOCT

Burn wOCT on Ethereum with your Octra recipient address
3

Automatic Unlock

The bridge relayer detects the burn and unlocks OCT on Octra (~2 minutes)

​
Features

  • Trustless Verification: Octra Light Client on Ethereum verifies Merkle proofs, with no trusted oracle
  • Multi-Wallet Support: EIP-6963 detection for Rabby, MetaMask, Phantom, and other EVM wallets
  • WalletConnect: Scan QR code from the mobile app to bridge
  • Auto-Reconnect: Wallets persist across page refreshes
  • Any chain to OCT: Pay with any token on the EVM chains Relay supports; Relay swaps it into wOCT and burns it to your Octra address in one fill
  • Bridge History: Full transaction history with claim actions and relayer-assisted recovery
  • Network Dashboard: Live chain stats at bridge.0xio.xyz/octra
  • Bridge Stats: Volume, transactions, unique wallets at bridge.0xio.xyz/stats
  • Transactions Log: On-chain mint/burn event feed at bridge.0xio.xyz/transactions

​
Contract Addresses

​
Bridge Limits

​
Fees

​
Architecture

​
Services

​
Known Limitations

  • Epoch Sync Delay: The ETH light client epoch updater may fall behind chain production. This causes Merkle proofs to be temporarily unverifiable until the sync catches up.
  • Pruned Epochs: Old epoch roots are pruned from the light client contract. Bridge transactions referencing pruned epochs cannot be claimed, so users should claim promptly.

​
Security

  • No trusted oracle: Verification is on-chain via Merkle proofs against the light client
  • Bridge pause: Owner can pause the bridge during emergencies
  • Cooldown protection: Rate limits prevent rapid drain attacks
  • Account change detection: Frontend detects wallet account switches to prevent sending to wrong address
Always verify the full destination address in the confirmation dialog before bridging. The bridge shows the complete address (not truncated) to prevent address injection attacks.