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
#6
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
462188385
Off-chain at
2026-10-27T19:25:47.751Z
Anchored at
2026-10-27T19:26:10.000Z
Block time
2026-10-27T19:26:10.000Z

Independent verification

1. Database (off-chain)
BsxhTJXEf7tG2usS7SS27yxH3Tutei8zbV1ER4dpBjwQ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1592 chars)
{"actor":"reviewer","artifact_identity":"f0f1d0e7cb9406f768d41d1cd43f14a0","blocked_count":1,"decided_at":"2026-10-27T19:25:47.556Z","decision":"review","disputed_pct":0.125,"findings_hash":"9ryu9Trze5Djhi89tDyVA8tm7HFvGgkCgfDNkbNs9QLb","investigation_id":"dd0db8d8-86d7-4988-95a1-b35ea4d655cf","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":1,"total":2},"page_content_hash":"e48852fa8ad70d39806712cd26e58247ba88498730a5611c5e713a60b5312f09","page_slug":"north-korea-lazarus-group-h1-2026-systematic-crypto-theft-campaign","prev_score":0,"reason":"The core quantitative claims (TRM H1 2026 totals, Drift and KelpDAO dates and amounts, Chainalysis 2025 totals) check out against the primary sources fetched. Problems found were minor: the Drift attribution wording credits TRM and Elliptic with a UNC4736 medium-confidence finding that TRM's preliminary post does not make; the KelpDAO node-compromise detail differs from LayerZero's own wording; the Arbitrum freeze figure is attributed to a Crypto Briefing article that does not contain it; and the 2017/$6B timeline entry cites a TRM page that lacks the figure. Blockaid claims could not be read. The page omits recovery outcomes for Kelp and Drift.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":6,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}