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 · TON Blockchain
- Sequence
- #16
- Score
- 76 → 76 (0)
- Cluster
- mainnet-beta
- Slot
- 470679406
- Off-chain at
- 2026-11-17T21:10:11.139Z
- Anchored at
- 2026-11-17T21:10:45.000Z
- Block time
- 2026-11-17T21:10:45.000Z
Independent verification
- 1. Database (off-chain)
- cUCX4ZVRo4X5PyxsFYtCnQfeXuV4S5fBYEKtGJP2wmh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1429 chars)
{"actor":"judge","artifact_identity":"1ac91e0aa2eeac0eb5c89a633f0cb8d0","band_override":null,"decided_at":"2026-11-17T21:10:10.861Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"1d62ae88-4b4d-4ccb-905a-a5a3badb9b77","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":76,"page_slug":"ton-blockchain","prev_score":76,"reason":"Of 7 claim findings, 4 were confirmed and 3 were partially supported. None were disputed or unverifiable, so the disputed rate is 0%. The partial findings are minor: claim_findings[1] (2020 settlement details not visible in the fetched summary, not contradicted), claim_findings[5] ('Part 1.1' sub-part not visible in the TASS fetch, while the charge, wanted list and sentence range match), and claim_findings[6] (DOGS named as cause of the first outage only by an X user, explicit for the second). The only omission is minor and unverified (a July 14, 2026 t.me domain suspension headline), and no shutdown, exploit or sanction contradicts the page. Open coverage gaps (validator stake concentration, ecosystem scam risk) are medium priority and suggest expansion rather than denial.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":16,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}