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 · Infini
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 462280084
- Off-chain at
- 2026-10-28T00:51:26.043Z
- Anchored at
- 2026-10-28T00:51:57.000Z
- Block time
- 2026-10-28T00:51:57.000Z
Independent verification
- 1. Database (off-chain)
- 2PG3jYDw84gbLQb48mwoySRwapK7k3MvbVUzpjSCH6zC
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1485 chars)
{"actor":"judge","artifact_identity":"f7cfb62ac82a3790c1fbe754aba4e467","band_override":null,"blocked_count":1,"decided_at":"2026-10-28T00:51:25.838Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"cd360476-a6ef-4cbc-a509-03bc959124c5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"infini","prev_score":53,"reason":"Of the 5 scored claim findings (one was excluded because its source blocked the reviewer), none were disputed but 2 could not be verified (claim_findings[4] and [5]), giving 40%, which falls in the significant-issues band. The core exploit account (admin role retained by a former developer, about $49.5M drained, Tornado Cash funding, 20% bounty) is confirmed by CertiK and Rekt in claim_findings[0] to [2]. The defects are an unsourced rumor naming a living co-founder's X handle, an unread laundering source, and CoinDesk attributions that the source does not support. Because reviewer confidence is modest (0.55) and only a sample was checked, the penalty is set at the mild end of the band. The September 2026 seed round omission is minor and the subject is still operating, so no severity override applies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}