How it works

The Quantum-to-Blockchain Pipeline

Quantum Core operates a continuous pipeline that captures quantum randomness and permanently records it on the Solana and XRPL blockchains. This process runs automatically, creating an immutable audit trail of quantum entropy.

Step-by-Step Process

Step 1: Quantum Measurement

At the ANU laboratories in Canberra, Australia, the Quantum Random Number Generator continuously measures quantum vacuum fluctuations using homodyne detection apparatus. This generates a stream of truly random data at the source.

The ANU QRNG exposes this quantum random data through a secure API endpoint that Quantum Core accesses.

Step 2: API Request

The Quantum Core publisher service makes an authenticated request to the ANU QRNG API:

https://api.quantumnumbers.anu.edu.au

Each request retrieves fresh quantum random bytes. The API returns hexadecimal-encoded random data generated from quantum vacuum measurements.

Request Parameters:

• Data type: Hexadecimal (hex16)

• Block size: 10 blocks

• Format: Raw quantum random bytes

Step 3: Data Processing

Upon receiving the quantum random bytes, the publisher service:

1. Validates the response to ensure data integrity

2. Hashes the raw bytes using SHA-256 to create a cryptographic fingerprint

3. Records the source identifier ("ANU-QRNG") for transparency

4. Captures the current Unix timestamp

The SHA-256 hash serves as a compact, fixed-size representation of the quantum random data that can be efficiently stored on-chain.

Step 4: Blockchain Publication

The processed data is submitted to the Quantum Core smart contract on Solana and recorded as a memo transaction on XRPL. Each transaction includes:

Field	Description
hash	SHA-256 hash of the quantum random bytes
src	Source identifier ("ANU-QRNG")
timestamp	Unix timestamp of publication
id	Sequential pulse identifier

The smart contract stores this data in a Program Derived Address (PDA), creating a permanent on-chain record.

Solana Program ID: 6JmMTwYMe7g8ZThH7dxZPCAey9Bda42Wi2HgUz84R3Tn

XRPL Account: rs1XDtrWxmyfq2LpMUB3huchx7h61bBsLj

Step 5: Immutable Record

Once the Solana and XRPL networks confirm the transactions, the quantum pulse becomes a permanent part of both blockchains. This record:

• Cannot be altered: Blockchain immutability protects data integrity

• Cannot be deleted: The record persists indefinitely

• Is publicly verifiable: Anyone can inspect the data on Solana Explorer or XRPL Explorer

• Has cryptographic proof: Transaction signatures prove authenticity

Data Flow Diagram

 ┌─────────────────┐
  │   ANU QRNG      │
  │   Laboratory    │
  │   (Canberra)    │
  └────────┬────────┘
           │
           │ Quantum vacuum
           │ fluctuations
           ▼
  ┌─────────────────┐
  │   ANU QRNG      │
  │   API Server    │
  └────────┬────────┘
           │
           │ HTTPS request
           │ (hex16 blocks)
           ▼
  ┌─────────────────┐
  │   Quantum Core  │
  │   Publisher     │
  │   Service       │
  └────────┬────────┘
           │
           │ SHA-256 hash
           │ + metadata
           ▼
      ┌────┴────┐
      │         │
      ▼         ▼
  ┌───────┐ ┌───────┐
  │Solana │ │ XRPL  │
  │Smart  │ │ Memo  │
  │Contract│ │ Tx    │
  └───┬───┘ └───┬───┘
      │         │
      ▼         ▼
  ┌───────┐ ┌───────┐
  │Solana │ │ XRPL  │
  │Chain  │ │ Chain │
  │(Immut)│ │(Immut)│
  └───────┘ └───────┘

Why Hash Instead of Raw Bytes?

Quantum Core stores SHA-256 hashes of the quantum random data rather than the raw bytes for several reasons:

1. Cost Efficiency: Blockchain storage is expensive; a 32-byte hash is much cheaper to store than variable-length raw data

2. Fixed Size: Hashes provide a consistent data structure regardless of input size

3. Data Integrity: The hash serves as a cryptographic commitment—any tampering would change the hash

4. Privacy Option: Raw bytes could be revealed later while the hash proves they existed at publication time