Anchor Protocol v0.1.0 — Apache 2.0

ANCHOR

The open standard that defines what it means for a prediction market oracle to be trustworthy. Published before any competitor has built a working oracle.

github.com/PROOF-xyz/ANCHOR ↗ Read Specification Verify a Receipt

The Problem

Why Anchor Exists

Every prediction market ever built has failed on the same constraint: the oracle has no skin in the game. Human committees are bribed. Regulatory oracles are captured. Token-weighted voting reduces to plutocracy.

The common failure root: when the oracle is wrong, nothing happens to it. An oracle that suffers no consequence for inaccuracy is not an oracle. It is an authority. Authorities can be purchased.

Anchor makes the oracle's economic wellbeing a direct function of its accuracy. Not reputational. Not social. Automatic, on-chain, inescapable.

◆

The Standard

Three Specifications

SPECIFICATION 01

Receipt Formation

A prediction is valid under Anchor if and only if:

The prediction text is specific and falsifiable
The hash is SHA-256(prediction_text + timestamp + oracle_pubkey) computed before any market activity
The hash is anchored to a public blockchain within the same block as the timestamp
The anchoring transaction is signed by the oracle's public key

Retrospective fabrication is cryptographically impossible.

SPECIFICATION 02

Resolution Determination

A market resolves under Anchor if and only if:

Resolution signal derives from the methodology specified in the receipt at issuance
Signal comes from at least two independent data sources specified in the prediction
Resolution fires automatically when sources confirm
Manual resolution triggers a governance-risk penalty from the credence pool

The methodology is locked before the market opens. Outcome is determined by data, not judgment.

SPECIFICATION 03

Credence Mechanics

An Anchor-compliant oracle must maintain a public $CRED credence pool:

Minting $CRED on confirmed correct predictions
Burning 50% of the staked amount on incorrect predictions
Publicly visible on-chain at all times
Oracle operations suspend when pool falls below minimum threshold

The incentive to be accurate is structural, not reputational.

◆

Receipt Schema

Receipt Format

    // Anchor v0.1.0 — Receipt Schema

    interface AnchorReceipt {

      receipt_id: string;      // Unique receipt identifier

      oracle_pubkey: string;   // Ed25519 public key

      prediction: {

        text: string;         // Specific, falsifiable claim

        hash: string;         // SHA-256(text + ts + pubkey)

        timestamp: ISO8601;    // Before outcome known

      };

      anchor: { chain: "solana-mainnet", tx_signature: string, block: number };

      resolution: { method: "automatic", sources: string[], trigger: string };

      credence_action: "mint" | "burn";

      sequence: number;  // 0 = genesis

      finality: "local" | "checkpointed" | "chain-anchored";

    }

◆

Verification

How to Verify Any Receipt

Any Anchor receipt is independently verifiable by anyone with access to the chain and SHA-256. No trust in PROOF required.

1. Retrieve the Receipt

Fetch from the public API: /api/v1/receipts/{receipt_id} — no authentication required.

2. Recompute the Hash

Compute SHA-256(prediction_text + timestamp + oracle_pubkey) and confirm it matches the receipt's prediction hash.

3. Verify Chain Anchor

Look up the anchor.tx_signature on Solana. Confirm the hash is in the transaction and the block timestamp precedes the outcome date.

4. Verify Signature

Confirm the anchoring transaction is signed by the oracle's declared Ed25519 public key.

→ Verify a receipt in your browser

◆

Conformance

Live Conformance Status

The PROOF intelligence engine is the reference implementation of Anchor v0.1.0 — the first Anchor-compliant oracle in production, against whose track record every subsequent implementation will be compared.

ANCHOR v0.1.0 — CONFORMANT

Public endpoint: /api/v1/conformance

87.6%

Accuracy Rate

Active Chains

Genesis Runs

◆

Competitive Position

The Competitive Checkmate

Anchor is published before any competing standard exists. Every possible competitor response strengthens PROOF's position.

Adopt Anchor + use PROOF oracle — PROOF becomes infrastructure. Revenue from oracle licensing. Network effect from adoption.

Adopt Anchor + build own oracle — Enter with empty credence pool 18+ months behind. PROOF's pool compounds in the meantime.

Reject Anchor — Must explain to sophisticated participants why they chose less accountability.

Use a human committee — Fail as every prior prediction market has failed. PROOF wins by default.

The gift is the specification. The weapon is the track record that no one else has and that the specification makes visible to everyone.