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
- 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. - 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.
- 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 · Early Solana Whale (Genesis Allocation) Theft
- Sequence
- #3
- Score
- 15 → 7 (-8)
- Cluster
- mainnet-beta
- Slot
- 462186056
- Off-chain at
- 2026-10-27T19:17:30.032Z
- Anchored at
- 2026-10-27T19:17:52.000Z
- Block time
- 2026-10-27T19:17:52.000Z
Independent verification
- 1. Database (off-chain)
- 7aGGfhyxuoaD4PodtW14RbwRFVCpRNPQT1TBoNFPBgj7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1398 chars)
{"actor":"judge","artifact_identity":"376bd18e42b6697871e521eb9ffb6878","band_override":null,"decided_at":"2026-10-27T19:17:29.656Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"e2a6bd01-0bad-443c-ad0b-5683f093c8ea","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":7,"page_slug":"early-solana-whale-genesis-allocation-theft","prev_score":15,"reason":"Core facts (amount, value, July 10 date, ZachXBT and Specter involvement, unconfirmed attack method and destination) match the cited sources. One of nine claims (11%) could not be verified: the $25.6 million repeat-phishing figure has no supporting citation (claim_findings[7]). Three further claims are only partly supported: the whole amount being bridged to Ethereum (claim_findings[1]), Specter detecting first (claim_findings[2]), and the AiCoin cause framing (claim_findings[4]). A minor omission (only about 60,000 SOL reportedly bridged) and a high-priority gap (no on-chain addresses or transaction hashes) support a small penalty, but no omission is material and the subject status does not contradict the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}