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.
Three different claims, three checks
The public verifier accepts a discovery ID, full hash, or transaction signature and does not require a wallet. A known record can be exported and inspected independently.
- Payload integrity. Validate and canonicalize the payload; recompute SHA-256, the 96-bit display ID, rarity tier, raw rarity score, tier probability and visual seed. Compare every derived value with the record.
- Server origin. Verify the Ed25519 signature over the hash using an independently trusted server key. Reject unknown keys instead of trusting a record’s self-supplied key.
- Solana inclusion. When an anchor exists, fetch the successful confirmed transaction on the configured network. Check the exact Memo program, committed hash and wallet signer.
An unanchored discovery can have valid integrity and a valid server signature. It must still be labeled unanchored. Unavailable RPC or an unknown signing key is not a successful verification.
Independent modules
engine/discovery.ts implements canonicalization; engine/rarity.ts implements interval assignment; engine/verify.ts verifies integrity and trusted-key signatures; engine/visual.ts recreates geometry. These are browser-compatible modules without a database dependency.
Integrity and signatures cannot prove that the operator used unbiased entropy, retained every result, or ran the documented code. Those remaining assumptions are listed in the security model.