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 · WEN
- Sequence
- #3
- Score
- 42 → 27 (-15)
- Cluster
- mainnet-beta
- Slot
- 461772423
- Off-chain at
- 2026-10-26T18:51:26.867Z
- Anchored at
- 2026-10-26T18:51:52.000Z
- Block time
- 2026-10-26T18:51:52.000Z
Independent verification
- 1. Database (off-chain)
- FnfTp4yvJcX9tQq2rWUBFjNBoeaRnbgE4n9ps3BxeywV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1497 chars)
{"actor":"judge","artifact_identity":"b33fd9e37cd9b6f55bac3be16964a4ba","band_override":null,"decided_at":"2026-10-26T18:51:26.456Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4545,"investigation_id":"d2b7e266-d875-476a-a3ad-5c9578fa2aef","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"page_slug":"wen","prev_score":42,"reason":"Of 11 checked claims, 2 were disputed and 3 could not be found in their cited sources, giving 5 of 11 (about 45%) disputed or unverifiable, which falls in the significant-issues band. claim_findings[0] shows the page's 40.7% burn figure contradicts the roughly 27% burn the page states elsewhere and what CoinDesk and market data report, and claim_findings[1] shows the summary's 'over 91%' decline from peak should read over 98%. The three unverifiable items (claim_findings[5], [6], [7]) are secondary details such as the 70% announcement, the Ovols handover and the HTX listing date. The core launch narrative holds, no shutdown, exploit or sanction was found, and the reviewer's confidence is moderate, so the penalty sits at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"score_limit":{"applied":-15,"limited":true,"proposed":-18,"rule":"second_opinion_agreed","second":-15},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}