Bridging Assets
This guide covers how to move assets between QoreChain and other blockchain networks. QoreChain's interoperability layer comprises 37 QCB (QoreChain Bridge) configurations (including a QoreChain loopback) for heterogeneous networks plus 8 IBC channels for Cosmos-ecosystem chains.
The cross-chain bridge is currently in a testnet / pre-production stage. Connection availability, supported assets, and finality parameters are subject to change and should not be treated as production-ready. Validate all transfers on qorechain-diana before relying on them.
The commands below use the qorechain-diana testnet (EVM chain ID 9800). Mainnet (qorechain-vladi, EVM chain ID 9801) has been live since 7 June 2026 running chain version v3.1.77 — substitute the mainnet chain ID and endpoints from the Connecting to Mainnet page where bridge support has been enabled.
Connection Overview
QoreChain provides two bridging protocols:
| Protocol | Connections | Use Case |
|---|---|---|
| IBC (Inter-Blockchain Communication) | 8 channels | Native interoperability with IBC-enabled chains |
| QCB (QoreChain Bridge) | 37 configurations | Cross-chain transfers with non-IBC networks via PQC-secured attestations |
A complete enumeration of every QCB configuration and IBC channel lives on the Bridge Architecture page. This guide focuses on day-to-day bridging usage.
IBC Channels
The following IBC-enabled chains have established channels with QoreChain:
| Chain | Channel | Status |
|---|---|---|
| Cosmos Hub | channel-0 | Active |
| Osmosis | channel-1 | Active |
| Noble | channel-2 | Active |
| Celestia | channel-3 | Active |
| Stride | channel-4 | Active |
| Akash | channel-5 | Active |
| Babylon | channel-6 | Active |
| QoreChain (loopback) | channel-7 | Active |
IBC transfers use the standard ibc-transfer module:
qorechaind tx ibc-transfer transfer transfer <channel> <recipient> <amount>uqor \
--from mykey \
--chain-id qorechain-diana \
--fees 500uqor
QCB Bridge Endpoints
The QoreChain Bridge connects to external chains spanning multiple ecosystem types. A representative selection of supported networks:
| Chain | Chain Type | Supported Assets |
|---|---|---|
| Ethereum | EVM | ETH, USDC, WBTC |
| BSC | EVM | BNB, USDC |
| Solana | Solana | SOL, USDC |
| Avalanche | EVM | AVAX, USDC |
| Polygon | EVM | MATIC, USDC |
| Arbitrum | EVM | ETH, ARB, USDC |
| TON | TON | TON |
| Sui | Sui Move | SUI |
| Optimism | EVM | ETH, USDC, OP |
| Base | EVM | ETH, USDC |
| Aptos | Aptos | APT, USDC |
| Bitcoin | Bitcoin | BTC |
| NEAR | NEAR | NEAR, USDC |
| Cardano | Cardano | ADA |
| Polkadot | Polkadot | DOT |
| Tezos | Tezos | XTZ |
| Tron | Tron | TRX, USDT |
See the Bridge Architecture page for the full list of QCB configurations and their current rollout status.
Deposit Flow (External Chain to QoreChain)
Depositing assets from an external chain into QoreChain follows this sequence:
- Lock — Lock tokens on the external chain by sending them to the QCB bridge contract or address.
- Attestation — Bridge validators observe the lock transaction and produce PQC-signed attestations.
- Threshold — Once 7 out of 10 validator attestations are collected, the bridge finalizes the deposit.
- Mint — The equivalent wrapped tokens are minted on QoreChain and credited to your
qor1...address.
CLI command:
qorechaind tx bridge deposit \
--chain ethereum \
--amount 1000000 \
--from mykey \
--chain-id qorechain-diana \
--fees 500uqor
Withdraw Flow (QoreChain to External Chain)
Withdrawing assets from QoreChain to an external chain:
- Burn — Burn the wrapped tokens on QoreChain.
- Attestation — Bridge validators observe the burn and produce PQC-signed attestations.
- Threshold — Once 7 out of 10 attestations are collected, the withdrawal is finalized.
- Unlock — The original tokens are released on the external chain to the specified destination address.
CLI command:
qorechaind tx bridge withdraw \
--chain ethereum \
--amount 1000000 \
--to 0xYourEthereumAddress \
--from mykey \
--chain-id qorechain-diana \
--fees 500uqor
Security Model
The QoreChain Bridge is secured by multiple defense layers:
| Mechanism | Description |
|---|---|
| 7-of-10 PQC Multisig | Every bridge operation requires attestations from at least 7 of 10 bridge validators, each using post-quantum cryptographic signatures. |
| 24-Hour Challenge Period | Withdrawals exceeding a configurable threshold enter a 24-hour challenge window during which validators or watchers can flag fraudulent transactions. |
| Circuit Breakers | Automated rate limiters halt bridge operations if abnormal volume or suspicious patterns are detected. Bridge operations resume after manual review. |
Querying Bridge Status
Check the status of a pending bridge operation:
qorechaind query bridge pending-deposits --address <your_qor_address>
qorechaind query bridge pending-withdrawals --address <your_qor_address>
List all active bridge connections:
qorechaind query bridge connections
Tips
- Bridge deposits typically finalize within minutes once the required 7-of-10 attestations are gathered.
- Large withdrawals trigger the 24-hour challenge period automatically. Plan ahead for time-sensitive transfers.
- Always verify the destination address format matches the target chain (e.g.,
0x...for EVM chains, base58 for Solana). - IBC transfers are generally faster than QCB transfers since they use native protocol-level communication.
- Bridge fees are burned through the
bridge_feeburn channel (see Token Operations).