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 · TON Blockchain
- Sequence
- #10
- Score
- 66 → 66 (0)
- Cluster
- mainnet-beta
- Slot
- 464922869
- Off-chain at
- 2026-11-03T13:53:39.449Z
- Anchored at
- 2026-11-03T13:54:02.000Z
- Block time
- 2026-11-03T13:54:02.000Z
Independent verification
- 1. Database (off-chain)
- Es4YvMkThEXZvkS67YSAqjg2Uc5uV16tehD2Qf8R1xFZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1318 chars)
{"actor":"judge","artifact_identity":"5f569a99d4c2ddf7d993ebaf81fc28e8","band_override":null,"decided_at":"2026-11-03T13:53:38.801Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"1d62ae88-4b4d-4ccb-905a-a5a3badb9b77","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":66,"page_slug":"ton-blockchain","prev_score":66,"reason":"Two of eight claims were disputed (25%): the Article 205.1 maximum sentence is given as 15 years while the cited source says life imprisonment (claim_findings[0]), and the timeline says two outages happened within a single day when they were on consecutive days (claim_findings[2]). The core SEC history, the May 2026 Telegram takeover and the Gram announcement were confirmed. The page also overstates uncertainty about the Gram rename date and the FSB charge date, and treats the rename as upcoming when it took effect on June 15, 2026 (claim_findings[1], claim_findings[5], omission_findings[0]); these are minor. No shutdown, exploit or sanction contradicts the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}