Technology

Quantum circuits run on real QPUs. Results are settled on Solana.

Quantum circuits run on real QPUs, and Solana coordinates, pays, checks and records the results, fast and at low cost.

Architecture: from circuit to settlement

Solana ↔ QPU bridge: how a job flows

1. Request. A user or program creates a JobRequest with circuit type, parameters, shots and fee.
2. Execute. The relayer watches events, builds the Ket circuit and submits it to a QPU.
3. Fulfill. The relayer submits the result, job ID and hashes via fulfill_job.
4. Settle. The bridge stores the result and optionally calls back into the requesting program.

Trust minimization: why you don't have to take our word

• Staked oracle operators
• Public receipts: job IDs, QASM and raw counts on Arweave / IPFS
• Verifiable jobs where possible, such as QAOA
• Multiple operators and providers XORed together for randomness
• Commit-reveal for every random value
• Simulator results always clearly labeled

Quantum-proof custody: funds that only move with a Falcon signature

bb84 adds post-quantum custody to Solana at the app level, today: Falcon-512 signatures checked by a Solana program, with no protocol change needed.

• Quantum Proof Table. Each owner's 897-byte Falcon key is stored on-chain once, with its QPU receipt and registration slot. After that, a transaction carries only the 666-byte signature.
• Irreversible Q-Day switch. Once the owner turns it on, the Ed25519 key can no longer move funds, even if it leaks. Only a Falcon signature, verified on-chain, can.
• Throwaway fee payer. A relayer pays the fee and never controls funds. The Falcon signature binds the destination, amount, nonce and expiry, so it can't be redirected or replayed.

See bb84 Vault and bb84 Wallet.

For Ethereum developers: Ethereum concepts → Solana equivalents

Falcon smart account: one signature, any instruction

• Each registered Falcon key controls a smart wallet that holds SOL and owns token accounts
• One Falcon-512 signature runs any instructions: SOL and SPL transfers, memos, other programs
• The signature covers the exact instructions, a nonce and an expiry slot
• Fits one transaction: SOL + memo in 335k CU, an SPL transfer in 304k CU

Quantum IDs: .quantum and .pqc names, seeded via real QPUs, put a Falcon wallet, multisig and quantum proof behind a readable name. See Quantum ID.

Alpenglow: faster Solana, made quantum-safer by bb84

Alpenglow activated on Solana mainnet at epoch 1064 (around October 21, 2026). Faster finality makes post-quantum custody on Solana even more practical.

What it helps

• Practical multi-transaction PQ signatures
• Faster commit-reveal finality for rng
• A near-real-time classical channel for the BB84 lab

What bb84 adds

• Falcon-512 vaults and smart accounts
• An irreversible Q-Day switch for every vault
• Quantum IDs with post-quantum multisig
• QPU randomness and on-chain checks of quantum results

Quantum stack: built on Ket

• Ket. A Python-embedded quantum language with the Libket Rust runtime and the KBW simulator for CPU and GPU. Exports OpenQASM.
• Rust-native oracle. The oracle uses Libket directly, with a shared bb84-types crate for formats, IDs and hashing used by both oracle and programs.
• Real hardware. 12 QPUs from 6 vendors through IBM Quantum and Amazon Braket. Randomness is batched into one job with many shots. See Hardware.