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 · MoonHacker
- Sequence
- #4
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 465082245
- Off-chain at
- 2026-11-03T23:22:33.097Z
- Anchored at
- 2026-11-03T23:24:04.000Z
- Block time
- 2026-11-03T23:24:04.000Z
Independent verification
- 1. Database (off-chain)
- 7C6owSaBspHK6isYaZDo6yV7gghF6PZ4x8Z28vKGGdR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1256 chars)
{"actor":"judge","artifact_identity":"4de737a2c534224724ae7f61ff167ccf","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T23:22:32.845Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4444,"investigation_id":"0b5775ae-4d7b-40c9-b388-53a4f8c826e1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":48,"page_slug":"moonhacker","prev_score":48,"reason":"Of 9 countable claim findings (one was excluded because its source blocked the reviewer), 4 were disputed or unverifiable, about 44%. claim_findings[1] is disputed: the summary says stolen funds were routed through Tornado Cash, but sources and the page's own body say Tornado Cash only pre-funded the attacker's wallet. claim_findings[3], [8] and [9] (the Moonwell disavowal date, the ZachXBT flag and the deployer contact) could not be verified. The core facts (date, ~$320K USDC loss, root cause, addresses) were confirmed, so the penalty sits at the lower end of the band.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":9,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}