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 · Nomic Chain
- Sequence
- #3
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462278986
- Off-chain at
- 2026-10-28T00:47:50.784Z
- Anchored at
- 2026-10-28T00:48:04.000Z
- Block time
- 2026-10-28T00:48:04.000Z
Independent verification
- 1. Database (off-chain)
- 5WBZg9xY9VBQkXqcnMTuzepaP21XdHyAouyFZsa1jUpz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1434 chars)
{"actor":"reviewer","artifact_identity":"268c26f45fea264039a3d9c7dcf196b9","blocked_count":2,"decided_at":"2026-10-28T00:47:50.724Z","decision":"review","disputed_pct":0.1818,"findings_hash":"3T1tyaGSGoNypebSX6CdUpxXKciAjsrKQ38tb8sXLzwN","investigation_id":"a9ed9033-dace-4dd5-b671-0e13181d3aa0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":1,"total":2},"page_content_hash":"bd0267002a2b8892de7197b8a492e3952f191875e96e7ba9081983631ad498c8","page_slug":"nomic-chain","prev_score":26,"reason":"The core exploit facts (40.650602 nBTC minted, 25 transfers, 74-day gap, 39.84 nBTC and 36.03% impaired, $3.15M, 17.19 BTC remaining shortfall) match the sources I could reach. Defects found: an unsupported July 17 date on the Tornado Cash timeline entry, a 'two separate bugs' detail I could not find, a freeze date that appears off by a day, and an editorial claim about multiple outlets blaming lack of monitoring. Background claims and the Sept 6 checkpoint date could not be checked because of 403s. The page omits that Nomic stayed offline.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"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}