The next state has not been discovered.
A network is not proven by its promises. It is proven by what survives contact with reality.
OVRNULL is an open experiment in verifiable participation. Explorers, testers and builders interact with the system, challenge its assumptions, report what breaks and help improve what comes next. Every mission has a purpose. Every proof has a rule. Every result should be explainable.
We are not here to inflate transaction counts or sell certainty about rewards that do not exist. The protocol is a work in progress. The evidence is the point.
How verification works
The core loop is Connect → Explore → Execute → Prove → Review → Progress.
- Sign-in. You sign an EIP-4361 message bound to this domain, chain 7331, a single-use nonce and an expiry (300s). Replayed, expired or mismatched messages are rejected. No transaction, no gas.
- Transaction hash = hint. The frontend is untrusted. When you submit a hash, the server independently fetches the receipt from its own RPC.
- Checks. Chain id, receipt status, target contract, sender, the expected event from the official contract, mission id and version, the mission time window, mission-specific conditions, and duplicate use of the same event.
- Confirmations. A result is finalised after 2 confirmation(s). Recent proofs keep being re-checked for 64 blocks; if a reorg removes the evidence the proof is invalidated and a compensating ledger entry is appended.
- Automatic evidence. The indexer polls contract logs with a persisted cursor. Mission events from signed-up wallets create attempts automatically, even if you never paste a hash.
- Human review. Contributions are reviewed by a reviewer who must record a reason code; only accepted submissions score. Reviewers cannot review their own work.
- Attestation (optional). Verified on-chain proofs are attested to the Proof Registry as a hash — never personal data.
Verifier version: ovrnull-verifier/1.0.0.
Scoring rules
Rules are versioned per mission. Publishing a rule change creates a new mission version; historical ledger entries keep the rule version that produced them. XP totals are always the sum of the append-only Signal Log.
| Mission | Version | XP | Cap / wallet | Verification |
|---|---|---|---|---|
| EXP-001 Genesis Handshake | v1 · r1 | +10 | 1 | session_handshake |
| EXP-002 First Signal | v1 · r1 | +25 | 1 | contract_event |
| EXP-003 Break the Pattern | v1 · r1 | +40 | 1 | boundary_probe |
| EXP-004 Signal Report | v1 · r1 | +30 | 3 | manual_review |
| EXP-005 Builder Trace | v1 · r1 | +50 | 2 | manual_review |
Levels
L0 Observer (0 XP) · L1 Explorer (10 XP) · L2 Tester (50 XP) · L3 Prover (120 XP) · L4 Architect (250 XP) · L5 Null Walker (500 XP)
What XP is not
Reason codes
Every award, rejection and correction carries one of these codes:
MISSION_VERIFIED— All mission rules passed.SUBMISSION_ACCEPTED— A reviewer accepted the submission.SUBMISSION_DECLINED— A reviewer declined the submission.HANDSHAKE_COMPLETED— Wallet control proven with a signed nonce and disclaimer acknowledged.WRONG_CHAIN— The transaction is not on the configured OVRNULL network.TX_NOT_FOUND— The transaction could not be found on the configured network.TX_REVERTED— The transaction reverted on-chain.WRONG_CONTRACT— The transaction did not target the official OVRNULL contract for this mission.SENDER_MISMATCH— The transaction was sent by a different wallet than the signed-in participant.EXPECTED_EVENT_MISSING— The expected event was not emitted by the official contract.MISSION_VERSION_MISMATCH— The event references a different mission or mission version.CONDITION_NOT_MET— The event was emitted but the mission-specific condition was not met.DUPLICATE_ATTEMPT— This evidence was already used for another attempt.MISSION_NOT_ACTIVE— The mission was not active at the time of the action.CAP_REACHED— The award cap for this mission was already reached for this wallet.PREREQUISITE_MISSING— A prerequisite mission has not been completed yet.MANUAL_CORRECTION— Score adjusted by an operator through an audited correction.MANUAL_APPROVAL— A reviewer approved this attempt after manual review.MANUAL_REJECTION— A reviewer rejected this attempt after manual review.PROOF_INVALIDATED— The underlying transaction is no longer canonical (e.g. chain reorganization).VERIFICATION_TIMEOUT— The transaction was not confirmed within the verification window.
Contracts
Addresses are loaded from the recorded deployment manifest for OVRNULL Demo Chain (chain 7331), never typed by hand.
- OVRNULLMissionRegistry — mission ids, immutable versions, status and metadata hash: 0x000000…De0001
- OVRNULLSignal — the safe demo contract used by on-chain missions: 0x000000…dE0002
- OVRNULLProofRegistry — optional proof attestations: 0x000000…De0003
None of the contracts hold funds or request token approvals. They are not audited. See Status for compiler settings and verification state.
Wallets & networks
- Demo mode: this deployment runs on OVRNULL's simulated demo chain. A demo wallet is created in your browser; transactions are really signed and verified, but executed by the OVRNULL simulator instead of a public network. No faucet, nothing of value.
- Network: OVRNULL Demo Chain, chain id
7331, RPChttps://ovrnull.com/api/demo-rpc. - OVRNULL never asks for a seed phrase or private key and never requests token approvals.
Known limitations
- One person can control many wallets. OVRNULL does not claim to be sybil-proof; caps, review and anomaly flags reduce — not eliminate — farming.
- The testnet can be reset; interactions may fail or change.
- Rate limiting is per instance (MVP). Admin access is wallet-allowlist based; MFA is required before public launch.
- Contracts are unaudited testnet code. Testnet deployment is not proof of security.
- Demo chain: transactions are really signed and verified, but executed by OVRNULL's simulator, not a public network.
- Nothing on the demo chain is a real asset. Data may be reset at any time.