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.

Decision
review_revise · Abstract
View on Solana ↗
Sequence
#4
Score
38 → 32 (-6)
Cluster
mainnet-beta
Slot
461970719
Off-chain at
2026-10-27T06:34:33.879Z
Anchored at
2026-10-27T06:34:38.000Z
Block time
2026-10-27T06:34:38.000Z

Independent verification

1. Database (off-chain)
Dyfu1i8xKHHnBCcWjeH2jzaPeALtbVeXMy5twdU7Dwmo
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1301 chars)
{"actor":"judge","artifact_identity":"20b471683c02fc785e726fda447d380e","band_override":null,"decided_at":"2026-10-27T06:34:33.540Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"4c71cf79-10b4-4353-9d14-1411463bc12e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":32,"page_slug":"abstract","prev_score":38,"reason":"Of 8 claim findings, 1 is unverifiable with a dead source (claim_findings[6], the June 2025 X-account compromise), giving a disputed share of about 12.5%, which falls in the minor-issues band. The core claims were confirmed against Tier 2 sources: the October 6, 2026 shutdown and December 15 deadline, the Cardex figures, the L2Beat centralization details and the mainnet date. The one defect is a low-severity allegation that the page already labels unverified, whose only source now returns HTTP 410 (claim_findings[7]). Omissions are minor and the page already reflects that the subject is shutting down, so the penalty stays at the light end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}