Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Nomic Chain
View on Solana ↗
Sequence
#4
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
462278991
Off-chain at
2026-10-28T00:47:50.961Z
Anchored at
2026-10-28T00:48:05.000Z
Block time
2026-10-28T00:48:05.000Z

Independent verification

1. Database (off-chain)
GFLvcB7n9Dg2bBJbrJuQ9wcbScQh47DeymRUeGubCRKB
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2088 chars)
{"actor":"judge","artifact_identity":"268c26f45fea264039a3d9c7dcf196b9","band_override":null,"blocked_count":2,"decided_at":"2026-10-28T00:47:50.724Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1818,"investigation_id":"a9ed9033-dace-4dd5-b671-0e13181d3aa0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"nomic-chain","prev_score":26,"reason":"The core exploit facts (40.65 nBTC minted, 25 transfers, 74-day gap, $3.15M, 36.03% impairment, 17.19 BTC shortfall) were confirmed by multiple sources. Two scored claims could not be verified (claim_findings[10], a multi-outlet attribution of the detection gap to Nomic's lack of monitoring that the sources do not make, and claim_findings[11], a placeholder-looking 2023-01-01 launch date), and three others are only partly supported (the 'two separate bugs' detail, the July 17 Tornado Cash date, and the freeze date). Two further claims could not be checked because the sources blocked the reviewer, which is a coverage limit and not counted against the page. The page also omits that Nomic remained offline with transfers disabled and the shortfall unresolved (omission_findings[0]), so it was judged one band more severe than the percentage implies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The percentage alone (2 of 11 scored findings, about 18%) implies the minor band. The review reports a material omission (omission_findings[0]): the page does not say Nomic stayed offline with IBC transfers disabled and the 17.19 BTC shortfall unresolved. Together with three partially supported findings and two high-priority coverage gaps, this warrants the significant band. The reviewer's low confidence (0.6) keeps the penalty at the mild end of that band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}