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 · Terra 2.0
- Sequence
- #3
- Score
- 12 → 7 (-5)
- Cluster
- mainnet-beta
- Slot
- 426261329
- Off-chain at
- 2026-06-13T19:21:41.460Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- ArFnFrwNFqzKBoqXAY3pDmUz75qLaJ2oFcrcQ4WqoTtm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1245 chars)
{"actor":"judge","decided_at":"2026-06-13T19:21:41.252Z","decision":"review_approve","investigation_id":"c63276f5-7405-40aa-b76a-a6ba2204fae5","new_score":7,"page_slug":"terra-20","prev_score":12,"reason":"All 22 claims were checked; 16 are fully confirmed by Tier 1 sources and 0 are disputed. The five partially-supported findings are minor in scope: four involve off-by-one-day date discrepancies (claim_findings[15], claim_findings[26]) or a small numerical understatement in peak LUNA supply (claim_findings[11]), with the most material error being the Interpol Red Notice date listed as September 1 rather than September 25-26, 2022 (claim_findings[16]). The 79% year-over-year token decline figure (claim_findings[8]) was not independently verified at that exact magnitude but is directionally accurate. A small score penalty of -5 is applied to reflect the partially-supported findings. Three high-priority coverage gaps are noted — particularly that all eight page sections carry empty content and heading fields — but per policy these indicate needed expansion rather than grounds for denial.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}