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 · Neutron DAO
- Sequence
- #4
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 462179237
- Off-chain at
- 2026-10-27T18:53:12.319Z
- Anchored at
- 2026-10-27T18:53:42.000Z
- Block time
- 2026-10-27T18:53:42.000Z
Independent verification
- 1. Database (off-chain)
- 7KoXKpTL6LkBY6m9sWeVxg9P7JMLxALAEsQTWoZQ6b1a
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1746 chars)
{"actor":"judge","artifact_identity":"9b6696599936f87c4334d355509cee36","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T18:53:11.962Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"ac47d7bc-f668-41e1-b840-67a083d8ff15","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":32,"page_slug":"neutron-dao","prev_score":32,"reason":"Of 9 scoreable claims (2 excluded because the source blocked the reviewer), none were disputed and 2 could not be found in the cited articles (claim_findings[2] the 81.88% tally and claim_findings[3] the September 19 filing date), giving about 22%. The core facts are confirmed by the Cosmos Hub forum and news reports: the $20,199 purchase, the 24-minute drain, the loss split and the Hub halt. claim_findings[4] is only partly supported because the 83:1 ratio compares staked value to contract value, not attack cost. The page also omits the Neutron chain pause and post-mortem, and the reviewer flagged a high-priority gap on primary-source citations.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (Neutron chain pause, relaunch team and Sep 29 post-mortem) is follow-up context, and the subject status does not contradict the page, which already describes the exploit. The page already sits in the revise band at the upper end of the penalty range, so escalating to the significant band is not warranted."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}