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 · Q2 2026 DeFi Record Hack Wave
- Sequence
- #6
- Score
- 0 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 462182409
- Off-chain at
- 2026-10-27T19:04:44.172Z
- Anchored at
- 2026-10-27T19:04:57.000Z
- Block time
- 2026-10-27T19:04:57.000Z
Independent verification
- 1. Database (off-chain)
- J5PzLjMmiLgSPVbhjTwrVgvyEBeBtWwhNf2pZo4SQdUm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1726 chars)
{"actor":"judge","artifact_identity":"510147950fbe1b8b65b2fcb6ca115259","band_override":null,"decided_at":"2026-10-27T19:04:43.879Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"0180d047-73a2-45da-9503-dfef6cc4ea9d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"q2-2026-defi-record-hack-wave","prev_score":0,"reason":"Every checked claim matched its cited source (3 confirmed, 3 partially supported, 0 disputed), so the claim-level dispute rate is 0%. However, claim_findings[0] and claim_findings[1] show that the 83 incidents and $755.3M are a June 22 quarter-to-date snapshot that the page presents as the full quarter, and omission_findings[1] notes a later CertiK full-quarter figure of $807.5M. The page should date the snapshot and update to final totals. The Drift rebrand to Velocity DEX (omission_findings[0]) is minor, and the reviewer did not check many sub-claims.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"sequence_num":6,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"The percentage band is approve (0%: no disputed or unverifiable findings), but omission_findings[1] is material and coverage_gaps[0] is high priority. The page presents a June 22 quarter-to-date snapshot as the full April 1 to June 30 quarter, and the headline figures rest on that snapshot. Escalated to the minor band, not higher, because the figures match the cited source and the correction is a dating and framing fix."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}