← All posts
6 min read

The QBC faucet is live, and so is QBC on the QVM

Two things you can use today: a faucet that hands out native QBC on the L1 at qbc.network/faucet, and the QBC token on the QVM, chain 3303, backed one to one by L1 escrow and visible in MetaMask. We walked a round trip through the bridge this evening and show the numbers.

#release#bridge#qvm

Two pieces of the QuantumAI Blockchain are now simply there for anyone to use. The first is a faucet that pays out native QBC on the post-quantum L1, so you can get a wallet funded in a minute without asking anyone. The second is QBC on the QVM, our EVM-compatible layer on chain 3303, where QBC is a standard token that MetaMask understands and that is backed, unit for unit, by QBC held in escrow on the L1.

Both are live. Here is what each one does, what it will not do, and how we checked.

The faucet

Go to qbc.network/faucet, paste a QBC L1 address, and the faucet sends 1 QBC to it. The rules are deliberately plain:

  • 1 QBC per claim. Enough to register a key, send a first transaction, or lock a few units into the bridge.
  • One claim per address per 24 hours.
  • 500 claims per day across everyone. When the daily budget is used up, the page says so and the counter resets the next day.
  • Native L1 QBC. The faucet pays from an ordinary L1 wallet that was funded with 100,000 QBC at launch, so the supply of claims is finite and visible on-chain.

The faucet is for getting started, not for income. If you want more QBC than a claim, the honest routes are mining and participating in the network.

We tested a claim this evening from the public page. The transaction was accepted in about 13 seconds and the receiving wallet's on-chain balance rose by exactly 1.00000000 QBC.

QBC on the QVM

QBC now exists on the QVM as a token contract at:

0x2909035000B51675555e179521C7e37170659dC3   (chain 3303)
  • Name: QuantumAI Blockchain. Symbol: QBC. Decimals: 8, the same as native QBC, so one unit on the L1 is one unit on the QVM with no rounding.
  • Minted only by the bridge. No owner can mint. The bridge contract at 0x5D3441e6aB3eCF8F1D1Dc357aa9B5326c719F67a creates QBC on the QVM only against a confirmed lock of native QBC on the L1, once per lock, in nonce order.
  • Burned to leave. Burning QBC on the QVM, with your L1 address attached, releases the same amount from L1 escrow back to that address.
  • Two of three attesters must agree before any mint or release happens, and the L1 escrow module caps outflow at 10,000 QBC per 26,182 blocks (about a day) as a circuit breaker.

The invariant that matters is one line: QVM QBC supply equals L1 escrow, always. The bridge page at qbc.network/bridge shows both numbers side by side, read live from the two chains.

Add it to MetaMask

Add a network with chain ID 3303, RPC https://qvm.qbc.network/jsonrpc, and block explorer https://qbc.network/explorer. Then import the token address above. The wallet page at qbc.network does both steps for you with one click. MetaMask insists the network's native unit shows 18 decimals; that is a MetaMask rule and does not affect the QBC token, which has 8.

The round trip we ran tonight

Writing "backed one to one" is cheap, so we exercised the whole path on the live chains before publishing, with the numbers below taken as they happened (SNAPSHOT, 14 October 2026, evening AEST).

  1. Before. L1 escrow 3.076 QBC. QVM QBC supply 3.076 QBC. Balanced.
  2. Lock. We locked one mature L1 coinbase output of 15.27 QBC into the escrow module, naming a QVM address as the destination. The L1 extrinsic was included within a block.
  3. Mint. After L1 finality, the attesters saw the lock. The first attestation landed on the QVM and the mint executed about two and a half minutes after the lock. Escrow 18.346 QBC, supply 18.346 QBC. Balanced.
  4. Burn. From the QVM address we called burnToL1 for 15.27 QBC, attaching the original L1 address. The transaction succeeded in one QVM block.
  5. Release. Within a minute the attesters released 15.27 QBC on the L1 to that address, which showed the full amount back as a new spendable output.
  6. After. Escrow 3.076 QBC. Supply 3.076 QBC. Balanced, to the unit.

Nothing in that sequence needed anyone's permission, and nothing in it is simulated.

What this is not

  • The QBC on the QVM is a bridged representation of native QBC. It is not a second currency and there is no second supply.
  • The faucet is rate limited by design and will run dry if it is abused; the limits above are the limits.
  • The QVM is still a single-submitter rollup whose state root is anchored to the L1 by one validator. Moving that to a committee is on the roadmap.

Try it

ShareXLinkedIn

Written by

A
Ash Brown@blockartica
Founder, SusyLabs / QuantumAI Blockchain

Building the post-quantum AI-native L1 with permissionless on-chain training cycles. Writes about consensus, attestation, and the gap between what ships and what's claimed.

github.com/BlockArticax.com/QuantumAi_QBC

Related posts

10 min read

A post-quantum cold wallet, built in private

A long look at the QV desktop wallet: a post-quantum cold-storage wallet that holds Bitcoin, Lightning and QBC behind one recovery phrase. This is a private build, not a public release, and this post explains what is in it and how we harden it before anyone trusts it with value.