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 · Dritan Kapllani Jr.
- Sequence
- #9
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 464430545
- Off-chain at
- 2026-11-02T08:36:37.586Z
- Anchored at
- 2026-11-02T08:37:01.000Z
- Block time
- 2026-11-02T08:37:01.000Z
Independent verification
- 1. Database (off-chain)
- 5PFHMZWqYxwaA77vRaLJKsY8tCwVVpMz6LDh1uyx1Gh5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1467 chars)
{"actor":"judge","artifact_identity":"afd2297ac06894c1471d1ea9ca619793","band_override":null,"decided_at":"2026-11-02T08:36:37.243Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"141dbe93-b5b4-4e8b-a03a-bcfc26ab6fde","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"dritan-kapllani-jr","prev_score":26,"reason":"Of 9 claims reviewed, 6 were confirmed against Tier 1 and Tier 2 sources, and the page attributes its core allegations to ZachXBT with appropriate hedging. One claim could not be verified (claim_findings[7]: the California victim and impersonation detail) and two were only partly supported (claim_findings[6]: both cited outlets report time served and none reports a 25-month term, so 'reports differ' is unsupported; claim_findings[8]: the FDIC OIG release does not use the 'Co-Conspirator 1' label). That puts the disputed share at about 11%, the low end of the minor band. A high-priority gap remains because no primary court record is cited for the Co-Conspirator 1 description. The omission about Johnston's cooperation is minor, and the review found nothing that contradicts the page about Kapllani's status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}