Skip to main content
AVOID.NET
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Sequence
#1
Score
10 → 10 (0)
Cluster
mainnet-beta
Slot
462038712
Off-chain at
2026-10-27T10:35:31.500Z
Anchored at
2026-10-27T10:35:37.000Z
Block time
2026-10-27T10:35:37.000Z

Independent verification

1. Database (off-chain)
BEvkPCHnSKQkD8noBj8gqTQpVMMLQNw87a26hv8fuJWC
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1310 chars)
{"actor":"reviewer","artifact_identity":"5ee4482ff6cfc94b912d7bd4263528a7","decided_at":"2026-10-27T10:35:31.397Z","decision":"review","disputed_pct":0.1818,"findings_hash":"2pHCmugCsUhmd49FFciAB9KrUcVTzDiBAyDDk5tsfULz","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":0,"total":2},"page_content_hash":"07d8735cf09e1d0903e598d0c572acaf3b4c67162fa9db848c6bc6fceb831c7e","page_slug":"router-protocol","prev_score":10,"reason":"The shutdown, burn, deadline, price collapse and funding facts are well supported by multiple outlets. The main defect is the framing that the 2025 incidents were undisclosed until the shutdown, which conflicts with the page's own cited July 2025 official incident report. The 'solver-related' label for the February incident and 'led by Coinbase Ventures' are not supported by the cited sources. The page uses future tense for a deadline that has passed.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":1,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}