Qubic Cross-ChainBridges

Why bridges are the hardest problem in crypto

Cross-chain bridges are the connective tissue of Web3 — and historically its weakest link. Almost every bridge depends on a trusted middle: a small group of external signers, a relayer, or a custodian that attests what happened on another chain. That concentration of trust is exactly what attackers target, and bridge hacks account for some of the largest losses in the industry.

Qubic's goal is to remove the trusted middle altogether — and it's getting there in two generations: QBridge today, and a fully trustless bridge built on consensus-level verification.

QBridge: today's non-custodial bridge — and why it's only the first step

QBridge connects Qubic directly to Ethereum for token transfers using a lock-and-mint model. Moving QUBIC to Ethereum locks the native tokens in the QBridge smart contract on Qubic and mints an equal amount of wQUBIC (an ERC-20) at a strict 1:1 ratio; bridging back burns the wQUBIC and unlocks the original QUBIC. It is non-custodial — no custodian ever holds your funds — and security-audited, with a cross-chain message layer that can carry governance votes, oracle data, and contract calls, not just tokens.

But non-custodial is not the same as trustless. QBridge still relies on a trusted attestation between the two chains, governed by a 2-of-3 multisig. That removes single points of custody and is a solid, pragmatic first generation — but the middle still carries a trust assumption. Think of QBridge as the predecessor: the step that proves the model while the trustless successor comes online.

The trustless successor: verification built into consensus

The successor removes the trusted middle entirely. Instead of trusting anyone to report what happened on Ethereum, every Computor checks for itself. Reading a foreign chain's event follows a three-step query → commit → reveal flow:

• Query — a single request identifies the external chain, the transaction hash, and the log index of the event to read (for example, a specific log inside an Ethereum transaction).
• Commit — each Computor independently fetches that event log and broadcasts a hash of its reply (K12) together with a knowledge proof. Commitments accumulate until at least 451 of the 676 Computors agree.
• Reveal — once quorum is reached, the full reply is written on-chain: the raw external-chain event, with zero interpretation, exactly as an EVM node would return it.

The entire round trip completes in about a minute, and every value is reproducible on-chain — the result a Qubic smart contract sees can be checked against a public Ethereum explorer and matches byte for byte. There is no relayer to trust: the quorum is the bridge. In effect, EVM data becomes natively visible inside the Qubic environment, secured by the same guarantee as the chain itself.

Developers can reproduce the whole flow today using qubic-cli — submit a query, watch commitments climb past the quorum threshold, and read the revealed reply, all directly on-chain.

What this unlocks

When a smart contract can independently and trustlessly read what happened on another chain, a bridge stops being a fragile side-service and becomes a native capability. A Qubic contract can watch for a deposit on an Ethereum bridge contract, verify it through the Computor quorum, and then act — releasing funds or triggering logic — using outsourced computation. The read-and-react loop can be fully automated inside the contract, with the same security guarantees as the chain itself. It's the same consensus foundation that powers Qubic's decentralized AI research.