Three independent verifier nodes fetch the same public dApp URL, calculate content fingerprints, sign their observations and return a transparent network integrity assessment.
The public testnet verifies public dApp URLs without trusting a single server. Three nodes independently fetch the target, calculate SHA-256 content fingerprints, sign their results, and the coordinator validates signatures and compares the fingerprints.
Each verifier independently requests the same public dApp URL and calculates a SHA-256 fingerprint of the returned content.
Every node signs its verification result with its own Ed25519 identity. The coordinator checks both signature and node identity.
The network compares authenticated node fingerprints. Matching signed results produce VERIFIED. Different authentic fingerprints are reported as CONTENT DIVERGENCE — not automatically as a security breach. Signature, identity and availability problems are reported separately.
Early testnet operators receive a permanent Genesis Node ID and test points. No tradable token is needed at this stage.
Install the verifier client on a VPS or computer.
Simulate transactions and submit signed verification results.
Correct consensus participation increases reputation and test points.
Browse recent QIN Public Proofs. Open any record or download its JSON for independent verification with QIN Verify v0.7.3. Open v0.7.3 release ↗
proof.json, then verify it independently with
QIN Verify on GitHub.
QIN batches Public Proofs into a Merkle tree and commits the resulting root to Solana Mainnet. This creates an external, timestamped reference that can be checked independently of QIN infrastructure.
The Merkle root below represents the first anchored QIN Public Proof batch. Changing any included proof changes the root and breaks the match with the finalized on-chain record.