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 · ThalaSwap
- Sequence
- #4
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 443520288
- Off-chain at
- 2026-08-26T11:12:54.276Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BXyWJW1S6Kp7mzTbGwJtc5FSoEVb4DSQu1TChMo9do4w
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1038 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:12:54.202Z","decision":"review","investigation_id":"9ef17dd6-b7aa-4c1a-ae5c-c52a6a15cc62","new_score":62,"page_slug":"thalaswap","prev_score":62,"reason":"The page's account of the November 2024 ThalaSwap exploit is closely and precisely corroborated by Thala's own post-mortem and multiple independent outlets (Halborn, Cointelegraph, The Block, Cybernews, Quadriga Initiative), including exact timestamps, addresses, frozen-asset figures, and remediation steps. The one substantive defect is a mischaracterization of the $40,000 amount in the recovery timeline, which the primary source attributes to personal compensation for the Thala founders rather than an additional payment to the attacker; the closing claim about ThalaSwap V3's TVL and date of ascendance is directionally correct but its specific date and cited-source alignment are weak.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}