bb84 RNG
Status: On devnet · Group: Quantum infrastructure
Randomness measured on a real quantum computer.
Random bits from qubit measurements on real QPUs, delivered to Solana with commit-reveal. Every job leaves a public record: circuit hash, backend, job ID and result hash, so anyone can audit where a value came from.
How it works: from QPU to your program
- Request. A user or program creates a JobRequest with circuit type, parameters, shots and fee.
- Execute. The relayer watches events, builds the Ket circuit and submits it to a QPU.
- Fulfill. The relayer submits the result, job ID and hashes via
fulfill_job. - Settle. The bridge stores the result and optionally calls back into the requesting program.
Trust: 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
On-chain: two programs, live on devnet
| Program | What it does | Devnet address | Mainnet address |
|---|---|---|---|
qentropy | Commit-reveal randomness seeded by QPU measurements, mixed with a slot hash sampled after the commitment. Providers stake and can be slashed. | FZXp8BVcsPZcE6ZP4wCYouMsupGEGKSZFwNfzNaoiQmm | {{MAINNET_QENTROPY_ADDRESS}} |
qproof | Receipts for QPU jobs: job ID hash, backend, circuit hash and result hash, posted by the relayer. | 6pxqWGoxSRBwmL6GJie9BD43HGe3ybFu9xmJQ24TvcXB | {{MAINNET_QPROOF_ADDRESS}} |
Already run: first real QPU run, settled on Solana
Quantum randomness on IBM. Random bits measured on ibm_fez through IBM Quantum, committed and revealed on Solana devnet, and checked by a public script. See Hardware.
Example transaction: {{RNG_EXAMPLE_TX_URL}}
Related
Updated about 1 hour ago
Did this page help you?