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 · Hyperdrive HL
- Sequence
- #3
- Score
- 45 → 35 (-10)
- Cluster
- mainnet-beta
- Slot
- 443525572
- Off-chain at
- 2026-08-27T11:02:39.767Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 13N6pV3DfcShbyKAeKFVj62awBucaBku5N6WsSQdLpmJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1213 chars)
{"actor":"judge","decided_at":"2026-08-27T11:02:39.020Z","decision":"review_revise","investigation_id":"dd592b49-5cdd-4dcf-b6aa-39f2c6ac9a89","new_score":35,"page_slug":"hyperdrive-hl","prev_score":45,"reason":"Every checkable claim on this page held up: the reviewer verified all 16 factual statements in the summary and timeline against outside reporting and found zero disputed or unverifiable items, so disputed_pct computes to 0.0%. But the review also flagged, at high priority, that the page itself contains no actual written content -- all seven sections are empty and cite no supporting sources (coverage_gaps[0]) -- and that it omits a materially relevant fact from a source it lists: Hyperdrive's contracts had passed multiple audits before the exploit that later drained the protocol, and the page never says so (coverage_gaps[1]). A page can have a perfect factual record and still fail to inform readers of the most decision-relevant thing its own cited source contains. That gap, not any false statement, is why this page does not clear a clean approval.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}