Cross-Reference Console

Don't trust. Recompute.

Every cell is recomputable. Never a bare green.

A live matrix where independent nodes cross-verify the same claim on different lanes. Nothing here is asserted — press Recompute and each cell re-derives its claim_id, re-hashes the source, and recovers the signer in your browser. Green is earned on your machine.

repo · registry · claims ↗ node 2: loading…

code unpinned build · data resolving… · currency not checked — this page has not asked whether it is the published build

First edge — frozen history crc.cell.v0

The original 2×1 edge, preserved exactly as it landed (2026-08-04). v0 is append-only history — never edited, never backfilled.

Claim	Node 1 — invinoveritas verifier 54848 · Fede lane: attestation/invinoveritas schnorr · Nostr	Node 2 — Vértice recompute-lens 0x85Fa…Bf1A lane: recompute/cross-reference-console EIP-712	Node 3 — ReceiptOS recompute 0x347a…8300a · Pavlo lane: recompute/receiptos EIP-712
/ledger #236 review_verdict · verdict: "reject" · conf 0.84 claim_id sha256:df1a6bfe… source ↗	unverified click to recompute this cell →	unverified click to recompute this cell →	no v0 cell lane opened at v1 — v0 is frozen history, never backfilled

edge: both nodes must derive the same claim_id for the edge to hold

Join the matrix — three doors, one gate

Payment meters admission. Only the cryptographic + conformance checks decide validity — never one substituting for the other.

1 · Submit a claim

POST a signed verdict to the registered intake — invinoveritas /ledger/submit ↗ (self-describing: GET it for fields, price, and flow — 150 sats via Lightning top-up or x402 USDC on Base, registration free, signature-verified, publishes immediately on success). A public CI watcher polls the ledger every 30 minutes, runs every entry through the pre-hash conformance gate, and registers conforming claims in claims/. Nonconforming-but-paid submissions are published in claims/rejected/ with the gate error — a rejection is a derivable fact, never a silent drop.

2 · Cross-verify a claim (registered nodes)

Recompute the claim from its source, sign a crc.cell.v3 Cell under your registered key, and open a PR to cells/{claim_id_hex}/{node_id}.cell.json. New here? ONBOARDING.md walks it end to end, and CELL-v2.md is the format you sign against. CI runs the full mechanical review — gate, claim_id, as_of binding, and your envelope's signature check against the registered key (never the key the cell asserts). Green merges; your column earns its lamp here. One-liner check before you PR: recompute-step crc/cell-verify <cell.json> eip712 <registered address> (recompute-kit).

3 · Register a lane

One PR adding one node object to nodes.json per NODES.md: identity, lane, envelope (nostr-nip01 or eip712), and a checkable key reference. If it parses, conforms, and the key is checkable, it merges — no other approval step. Retirement is a tombstone, never a deletion.

Your footprint in the matrix

No login — everything here is public and content-addressed. Enter a GitHub handle, an 0x address, or a claimant id; the report derives on your machine, live from the repo and registry.