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
#3
Score
31 → 31 (0)
Cluster
mainnet-beta
Slot
462187377
Off-chain at
2026-10-27T19:22:02.729Z
Anchored at
2026-10-27T19:22:34.000Z
Block time
2026-10-27T19:22:34.000Z

Independent verification

1. Database (off-chain)
AAjduXKEpHYoX39MtsQPsYowtJG6VEcnzFdBK7SFrWm6
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1499 chars)
{"actor":"reviewer","artifact_identity":"89559bb14197a6215e9c010e883c3ba1","decided_at":"2026-10-27T19:22:02.582Z","decision":"review","disputed_pct":0.2308,"findings_hash":"GxEhf2Lm9th5u7zYvHNzxEtQ1Z4oSQ45XdpzWaogZsME","investigation_id":"1ed0417b-43c3-4515-83ee-e082fefff6be","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":31,"omissions":{"material":1,"total":3},"page_content_hash":"20c312bc69973e6c0bf5f61e34e2dfb5f849f5eaf0abda2b006d2866b66cbd4d","page_slug":"multiversx-egld","prev_score":31,"reason":"The core timeline (Sept 19 exploit, Sept 24 restart, exchange actions, price and volume figures) is well supported by the cited news sources. Problems found: the User Protection Fund attribution to ETHNews and the executeOnDestContextByCaller attribution to CryptoTicker are not in the cited articles, the 2022 section heading says 'Bridge' while the body describes a Maiar DEX exploit, and the Sept 21 date for MultiversX's confirmation looks off. The page is also stale because the Upbit review window has passed. The attacker-freezing and no-loss claims rest solely on MultiversX's own statements, which the page mostly attributes correctly.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}