Cross-Chain Bridge

Architecture

The QuantumBridge uses a lock-and-release model with ML-DSA-65 post-quantum validator signatures. Assets locked on one chain are released on the destination chain only after a validator quorum provides valid Dilithium3 signatures.

1. Lock: User locks asset in QuantumBridge.sol on source chain
2. Observe: ThiChain validators observe the lock event
3. Sign: Validator quorum signs a release message with ML-DSA-65 keys
4. Release: Signed proof submitted to destination chain; wrapped asset minted to user

Supported Chains

How to Bridge

import { QuantumDEXClient } from '@qubismic/quantumdex-sdk';

const bridge = client.bridge();

// Initiate bridge transfer
const tx = await bridge.lock({
  tokenAddress: USDC_ADDRESS,
  amount: parseUnits('1000', 6),
  destinationChainId: 42161,     // Arbitrum One
  recipientAddress: userAddress,
});

// Monitor bridge status
const status = await bridge.getStatus(tx.hash);
// { state: 'PENDING_SIGNATURES', signaturesCollected: 3, required: 5 }
// { state: 'RELEASING', txHash: '0x...' }
// { state: 'COMPLETE', destinationTxHash: '0x...' }

Security Model

• Validator quorum: 5-of-9 validator signatures required before release
• Replay protection: Each lock event has a unique nonce; double-spending is blocked at contract level
• Karma gate: Bridge validators must maintain minimum Karma Score to participate
• Emergency pause: Trinity Guardian contract can pause bridge within one block in emergency

ML-DSA-65 Post-Quantum Security

Every bridge release proof is signed with ML-DSA-65 (CRYSTALS-Dilithium3), standardised as NIST FIPS 204. This makes QuantumDEX the first cross-chain bridge provably secure against quantum computer attacks.