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_approve · Atlantis Loans
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 465091574
- Off-chain at
- 2026-11-03T23:57:04.115Z
- Anchored at
- 2026-11-03T23:57:18.000Z
- Block time
- 2026-11-03T23:57:18.000Z
Independent verification
- 1. Database (off-chain)
- JDzab68UdQLy2sKg5RCVUeqHHPX7iSeAZ21k2jD7SnVj
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1457 chars)
{"actor":"judge","artifact_identity":"cb3c38d41b6582b4d4167198da30e53e","band_override":null,"blocked_count":3,"decided_at":"2026-11-03T23:57:03.823Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"5f3633bd-c615-44e1-a887-a95b3cbdcfea","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_slug":"atlantis-loans","prev_score":50,"reason":"Of 7 claim findings, 3 were unverifiable only because the sources (Medium, DeFiLlama) blocked the reviewer (claim_findings[4], [5], [6]) and are left out of the count. Of the remaining 4, none were disputed or unverifiable, giving 0% disputed. The core narrative (abandonment in April 2023, the June 2023 governance attack, $1.1M initial and $2.5M later losses) is confirmed by Rekt, Web3IsGoingGreat and Halborn. One timeline date for the $2.5M figure (claim_findings[2], June 12) is probably about a week too early, which is a minor correction rather than a challenge to the page. No omissions were reported and the page's shutdown status matches the sources. The large blocked share and the reviewer's moderate confidence (0.55) are coverage limits, not defects of the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":4,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}