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 · Revert Lend
- Sequence
- #3
- Score
- 48 → 33 (-15)
- Cluster
- mainnet-beta
- Slot
- 423949081
- Off-chain at
- 2026-06-03T03:53:50.531Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BiuWRX4pEbHJ57T9Cat1aZr8thkF2n2PHPRNxmTeXwWd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1380 chars)
{"actor":"judge","decided_at":"2026-06-03T03:53:50.337Z","decision":"review_revise","investigation_id":"4c26ba16-a016-41ac-894d-717867d71117","new_score":33,"page_slug":"revert-lend","prev_score":48,"reason":"The reviewer confirmed 8 of 15 claims and found 4 partially supported, but two claims (claim_findings[2] and claim_findings[13]) are unverifiable — both concern the same alleged January 29, 2026 exploit on Base chain for ~$50,000. This is a core security allegation that appears in both the summary and the timeline, yet no major hack tracker, on-chain transaction hash, post-mortem, or ZachXBT alert was located to support it. The reviewer notes the $50,000 figure may be conflated with a March 2026 Cantina bug bounty pool of identical size. Additionally, the Ethereum Mainnet launch date in timeline[10] is incorrectly placed as May 2026 when the confirmed date is June 2025, an 11-month error. Compounding these factual issues, all 7 section content fields are empty, meaning the page has no substantive narrative — a high-priority structural gap. The penalty is set at the top of the 10–30% band given the severity of an unverified exploit claim in the summary, the structural incompleteness, and the confirmed date error.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}