ATRAC InstituteProtocol RV-256
A remote-viewing test designed so that neither the subject nor the operator can influence the target after it is committed. The protocol is short enough to audit by hand.
The Diagnostic
Each round, the server generates a random 2-character code and assigns it to one of 12 distinct archetypes. Your task is to identify the hidden archetype.
To demonstrate capability beyond chance, a subject needs a statistically significant grouping of correct identifications across a 12-round testing window.
Cryptographic Audit Trail
To prove the server does not modify targets dynamically based on subject input, RV-256 utilizes SHA-256 cryptographic commitments.
Phase 1: Generation & Commitment
Before the round accepts inputs, the system generates the code, assigns the archetype, and appends a random 16-byte cryptographic salt. It computes the SHA-256 hash of this string and publishes it to all clients.
Phase 2: Data Collection
The subject submits their identification. Because the hash is already published, the system mathematically cannot alter the target data.
Phase 3: Verification
The round concludes. The raw data (card and salt) is broadcast. Subjects may independently hash the raw sequence to verify it strictly matches the initial commitment broadcast in Phase 1.
Entropy Protocol
Every target is drawn from a physical hardware-noise source — never from a deterministic algorithm. A pseudo-random generator would be reproducible in principle: given its seed or log state, the “random” target could be recomputed and the test would prove nothing. Hardware noise has no seed, no state, and no algorithm to invert. The served feed uses a quantum hardware entropy source (ANU, photon-measured noise) and falls back to the operating system’s cryptographically secure generator, which is itself seeded from hardware entropy. Either way the bytes are unpredictable to us and to you — once committed, a target cannot be precomputed, biased, or influenced.
Hardware noise is the right tool for this use: an anomalous-cognition test is only meaningful if the target could not have been guessed, leaked, or steered by any mechanism. This guest terminal states the per-round source openly on every target.