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 · Dough Finance
- Sequence
- #4
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 464348033
- Off-chain at
- 2026-11-02T03:42:21.730Z
- Anchored at
- 2026-11-02T03:42:33.000Z
- Block time
- 2026-11-02T03:42:33.000Z
Independent verification
- 1. Database (off-chain)
- HWdvor72paiPRYRsbZKYChZ2dhtR8g1y3CmksQkNjZB1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1560 chars)
{"actor":"judge","artifact_identity":"9354074da8de166e80cc5f2af6f89b64","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T03:42:21.510Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3636,"investigation_id":"b907a69e-6917-4f90-ad0a-942808b657d0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"page_slug":"dough-finance","prev_score":35,"reason":"Of 12 claims checked, one could not be read because the source blocked the reviewer and was left out of the count; of the other 11, none were disputed and 4 could not be verified (36%), which falls in the significant-issues band. The core exploit facts (date, about $2.1M loss, calldata validation root cause, Tornado Cash deposits, recovery amounts) were confirmed by CertiK (claim_findings[0], [2], [3]). The ZachXBT section (claim_findings[7], [8]) appears to be taken from a different incident, the Railgun funding (claim_findings[1]) and the December 2024 shutdown date (claim_findings[10]) have no supporting source, and the Lopez filing date and trial status look wrong or out of date (claim_findings[9], [11]). The penalty is held to the middle of the band because the central facts hold, the reviewer's confidence is moderate (0.6), and the omissions found are minor.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}