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.
- Sequence
- #3
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 462187202
- Off-chain at
- 2026-10-27T19:21:33.793Z
- Anchored at
- 2026-10-27T19:21:57.000Z
- Block time
- 2026-10-27T19:21:57.000Z
Independent verification
- 1. Database (off-chain)
- 4sFxWep23ntP3SgymcnVrkXewQzByqeyGRvnw1TdN7D6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1346 chars)
{"actor":"reviewer","artifact_identity":"7bfda89c31bae41caf4f8f12bf85056c","blocked_count":1,"decided_at":"2026-10-27T19:21:33.655Z","decision":"review","disputed_pct":0.4286,"findings_hash":"DJrZjNmuWhmNvARTfVsBEECbJw47PPcFueoTKtf8C4Nq","investigation_id":"f78211a6-4a7d-45e8-843e-69c3fdbe0683","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"omissions":{"material":0,"total":1},"page_content_hash":"025c8d48f29b815b4c86d262d0006c5e8696c03ff666782a602fb4279c3520f0","page_slug":"fetch-ai","prev_score":60,"reason":"Merger dates and the exploit date and amounts largely hold. The Ocean withdrawal date appears to be one day off (Oct 9, not Oct 10), and the stated 10% FET drop is not supported by The Block, which reports about 3.8%. The litigation claims could not be fully verified because several sources were blocked. The page needs a current-status update on the Fetch-Ocean dispute and attribution of the Sept 2026 exploit to Fetch.ai versus SingularityNET infrastructure.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}