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
#5
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
462051964
Off-chain at
2026-10-27T11:22:05.506Z
Anchored at
2026-10-27T11:22:33.000Z
Block time
2026-10-27T11:22:33.000Z

Independent verification

1. Database (off-chain)
Fn69ezYXhNwjmQS94i4GkVEykmo8xToheifXEffGHTrR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1364 chars)
{"actor":"reviewer","artifact_identity":"ad76071e59efaf06c97e5bd8c33f5d79","blocked_count":1,"decided_at":"2026-10-27T11:22:05.115Z","decision":"review","disputed_pct":0.1667,"findings_hash":"BDRfY15WG16muejUHLRTvNx5248ii7TfZ4Sx2eRRDDJQ","investigation_id":"1cc3092d-1f82-46ee-9145-3795a464c995","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":0,"total":1},"page_content_hash":"9a0f8677c35010adbb355d2e66c62d428f7ac259b4b16ceb7617a061f10a08cf","page_slug":"crypto-whale-repeat-phishing-25-6m-drain-august-2026","prev_score":0,"reason":"Core facts check out against the sources I could read: $25.6M, August 12, the PeckShield asset breakdown, the 20M DAI and 3,000 ETH conversion across four addresses, and the $49.8M combined figure. The page honestly flags the vector dispute and the 2023 return discrepancy. The attacker address 0x8fEB...F95Ae could not be found in the sources I read. Several sources were not fetched (Crypto Times returned 403), so confidence is moderate.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}