QBC is live on the QVM and in MetaMask, exactly 1:1

QBC now lives in two places at once. It stays the native, post-quantum currency of the QuantumAI Blockchain L1, secured by CRYSTALS-Dilithium signatures. And from today it is also live on the QVM, our EVM-compatible layer on chain 3303, where it appears in MetaMask as a standard token you can hold, send and use with smart contracts.

The two are joined by the new QBC bridge, and the rule that joins them is simple: exactly 1:1. One QBC on the QVM always means one native QBC held in escrow on L1. Not approximately, not by promise, but enforced by code on both chains and visible live on the bridge page.

Try it now at qbc.network/bridge.

What went live

• QBC on the QVM. A standard ERC-20 token with the name QuantumAI Blockchain, the symbol QBC, and 8 decimals, the same as native QBC. One unit on L1 is one unit on the QVM, with no rounding and no conversion.
• An L1 escrow. A new runtime module on the QBC chain holds native QBC while it is on the QVM, and keeps a running on-chain total of everything locked.
• The bridge contract on the QVM. It is the only thing in the world that can create or destroy QBC on the QVM, and it only does so against confirmed L1 escrow activity.
• A live bridge page on qbc.network, reachable from the menu under More, with both totals read straight from the two chains.

Exactly 1:1, and you can check it yourself

The bridge page shows three numbers side by side, each labelled LIVE with the time it was read:

• L1 escrow: the total native QBC locked on L1.
• QVM QBC supply: the total QBC that exists on the QVM.
• Escrow minus supply: zero when everything is settled.

At launch the escrow and the QVM supply matched to the last unit, and the page showed Balanced: every QVM QBC is backed. That is the whole design in one line. QBC on the QVM is created only when native QBC enters escrow, and it is destroyed before native QBC ever leaves.

The rule is enforced in three places:

1. Minting only against a lock. The QVM contract mints only for a specific, confirmed L1 lock, only once for that lock, and only if the new QVM supply stays within the escrow total recorded on L1 with that lock.
2. Burning before release. Sending QBC back to L1 burns the QVM tokens in the same transaction that records the request. L1 then releases the same amount from escrow, once per burn, and never more than escrow holds.
3. Same units on both sides. 8 decimals on L1, 8 decimals on the QVM.

Moving QBC to MetaMask (L1 to QVM)

1. Open qbc.network/bridge and load your native QBC wallet on the lock tab.
2. Choose a coin (a UTXO) to lock and enter your MetaMask address as the destination. The minimum is 1 QBC.
3. Sign in your browser. Your quantum-secure Dilithium key signs a message that names that exact coin, the amount, the QVM chain and your MetaMask address, so the lock can only ever go where you said.
4. The coin moves into the L1 escrow. Once the lock is finalized on L1, the attester committee confirms it and the same amount of QBC is minted to your MetaMask address. The page tracks each step for you.

A lock moves one whole coin. If you want to bridge a smaller amount, send yourself that amount with a normal wallet transfer first, then lock the new coin.

New to QBC? The faucet gives you 1 native QBC to start with.

Moving QBC back to L1 (QVM to L1)

1. Connect MetaMask on the bridge page. It adds the QBC network and the QBC token for you.
2. Enter an amount and your native QBC address.
3. Confirm in MetaMask. The bridge contract burns your QBC and records the request.
4. The committee confirms the burn and L1 releases the same amount from escrow as a new native coin in your wallet, ready to spend.

Built for MetaMask

The QVM is fully EVM-compatible, so QBC behaves like any other token in MetaMask. Alongside the bridge we tuned the QVM's wallet interface so MetaMask's normal flow just works:

• No gas token needed. Transactions on the QVM are gasless. You do not need to hold anything else to send QBC or use the bridge.
• Accurate gas estimates. MetaMask's estimates for token transfers and bridge actions come from a real simulation of the transaction.
• One click to add the network, from the bridge page or the network details on qbc.network.

If you prefer to add things by hand:

How the bridge stays safe

• A committee of attesters. Locks and burns are confirmed by a committee of independent attesters running on separate machines. Two of three must agree on the exact details of a transfer before anything is minted or released, and a vote for the wrong details can never be combined with the right ones.
• Finalized L1 state only. Attesters act on L1 locks only once they are in finalized blocks.
• Post-quantum signatures at the entry point. Every lock is authorised by the owner's Dilithium key over a message bound to this chain's genesis, the exact coin and the exact destination.
• A daily release limit. L1 releases are capped per rolling window of roughly 24 hours, a steady ceiling on how fast escrow can move.
• No owner, no fees. The QBC token has no owner, no admin mint and no fees. Supply only changes through the bridge.
• Governed by multisig. Runtime changes and bridge settings on L1 go through the chain's 2-of-3 sudo multisig.

Verified before launch

Before the bridge opened on mainnet, we rehearsed it end to end on a scratch chain with the exact runtime that went live: lock, mint, a MetaMask-style token transfer, burn, release, and spending the released coin, with escrow and supply checked at every step. We also recovered from a simulated outage of every attester: a lock made while all of them were offline was minted normally once they came back.

Then we ran the first real transfers on mainnet, through both the command-line wallet and the website itself. 11.076 QBC was locked on L1 and exactly 11.076 QBC was minted on the QVM. 10 QBC was then burned on the QVM and exactly 10 QBC was released back to the original L1 wallet as a spendable coin. Escrow and supply matched exactly after every step, and the bridge page shows those totals live.

What this opens up

QBC on the QVM means QBC can now take part in everything the EVM ecosystem does: smart contracts, applications and the wallets people already use, while the native currency underneath stays on a post-quantum L1. The bridge is the path between the two, and 1:1 is the promise it keeps.

Head to qbc.network/bridge, add QBC to MetaMask, and bring your QBC across.