Q/01 / ARCHIVED V1 / DEVNET

V1 mining method

Historical discovery specification. New v1 mining is closed; existing records remain verifiable.

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.

The former mine → discover → collect flow

The v1 server was the authority for competitive discoveries. The browser requested a mine and displayed the returned record; it could not submit its own rarity, measurement or score. This generation endpoint now returns HTTP 401 without authentication and HTTP 410 for authenticated requests.

  1. Create or read the server session. A guest can try mining; wallet authentication gives a portable collection and a public miner identity.
  2. Validate the request and reserve its unique request ID in PostgreSQL. Apply server-side session, wallet and IP limits.
  3. Verify the configured Solana RPC genesis hash and fetch a confirmed slot. A failed network read fails mining; no slot is invented.
  4. Create a fresh 32-byte mining nonce and 32 bytes of cryptographically secure server entropy.
  5. Execute the 16-qubit circuit, sample 2,048 shots, and calculate measured marginal probabilities.
  6. Canonicalize the core payload; compute SHA-256; derive its ID, tier, score and visual seed.
  7. Sign the hash with the server Ed25519 key and store the signed record. Return it only after storage succeeds.
  8. Play the short reveal sequence. The animation does not control or improve the result.

Auto Mine uses the same API and server limits. Repeating a completed request ID for the same actor returns its original discovery rather than awarding another. Requests already processing and failed requests are distinguished.

Collections and competition

Every completed discovery is stored. An authenticated wallet sees its wallet-owned discoveries across devices; a guest collection belongs to its server session and is not automatically transferred on wallet login. Feed entries, rarity counts and leaderboards come from stored discoveries on the configured network. Empty data remains empty.

Guest discoveries can appear in the public discovery feed. Wallet miner rankings include authenticated wallet records. Mining does not issue $QEE, an NFT, a staking reward, or an entitlement to future value.