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 · Dritan Kapllani Jr.
- Sequence
- #4
- Score
- 3 → 3 (0)
- Cluster
- mainnet-beta
- Slot
- 457525879
- Off-chain at
- 2026-10-16T05:47:22.470Z
- Anchored at
- 2026-10-16T05:47:30.039Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EK5MBy6oCciMB13F9L9rpmZA5WEK4Um8yFHrMPGEFpEk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2338 chars)
{"actor":"reviewer","artifact_identity":"c31214e00c908169e6e7ef1b1cbfce21","decided_at":"2026-10-16T05:47:22.165Z","decision":"review","disputed_pct":0.5714,"findings_hash":"ChV9teGuNLthxizpoYJhd71a5o7vuEWCfRNtqR4NCEiP","investigation_id":"141dbe93-b5b4-4e8b-a03a-bcfc26ab6fde","mode":"findings_only","new_score":3,"page_content_hash":"b73d460effb0c3031b4f0e7361d13baea2be50a253e1320c2e27dd8313afde95","page_slug":"dritan-kapllani-jr","prev_score":3,"reason":"The page's core narrative is well supported by multiple independent outlets: the ~$19M aggregate theft figure, the 2025 cluster ($5.85M across five thefts), the March 14, 2026 185 BTC theft (~$13M), the Exodus wallet's $5.3M inflow and peak balance, the April 23 Discord 'band 4 band' reveal, the DOJ case against Johnston and Tardibone, Johnston's guilty plea, and Kapllani's unresolved CC-1 status are all corroborated by at least one tier-1 or multiple tier-2 sources. However, several concrete errors recur: the page repeatedly calls the May 11, 2026 charging document a 'criminal complaint' when the government's own press releases describe a grand jury 'indictment' (four occurrences); the Johnston guilty-plea date is given as June 10 when converging secondary reporting points to June 9 (three occurrences); a timeline entry misdates John Daghita's arrest to March 1 when it was reported as March 4; and the page attributes an August 2024 $243 million Genesis-creditor theft to Daghita, when that theft was independently and specifically attributed by ZachXBT and the DOJ to three different, separately charged individuals. The page's own cited source for the Exodus wallet's age also implies the wallet was created the day after the theft, not a month before it as the page states. Several highly granular on-chain figures (specific ETH amounts, exchange-deposit-address count, Discord usernames) could not be verified because the primary ZachXBT thread and the CCN source article were inaccessible to this review. Two of four accepted community submissions carried no retrievable content to check against their incriminating label. No prompt-injection attempts directed at this reviewer were found in the accepted submissions.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}