ARCHIVED V1 — HISTORICAL RECORDS ONLY
This specification describes the former discovery experiment. New generation is closed: POST /api/mine returns HTTP 401 without authentication and HTTP 410 for authenticated requests. Existing records and their deterministic verification rules are retained. The current continuous run has no discovery drop, collectible, NFT or token reward. Read the current run specification.
What this system does not prove
- No physical quantum hardware, quantum advantage, certified quantum random-number source or prediction capability.
- No publicly verifiable fairness proof. An operator with the signing key can generate, omit or selectively publish results.
- No Sybil-resistant identity. A person can control multiple wallets or sessions; basic limits are not a competition-grade anti-bot system.
- No cryptocurrency mining reward, token issuance, NFT minting, yield or promised economic value.
- No custom QEE Solana program or external security audit.
- No guarantee of permanent database or RPC availability. Exported payloads aid independent verification; hash-only Memo records cannot reconstruct a lost payload.
- No automatic cross-device guest collection or claim of guest records when authenticating a wallet.
Operational responsibilities
Operators must back up PostgreSQL and the signing key, monitor service errors and resource consumption, maintain archival key information, and review rate limits as usage grows. A signing-key rotation needs an explicit trusted-key migration; silently replacing the active key can make old records unverifiable by the current service.
The current implementation provides a server-authoritative experiment with inspectable records. A valuable competitive or financial launch requires an independent security review and stronger fairness and abuse controls appropriate to its stakes.