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 · ThalaSwap
- Sequence
- #5
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 443520292
- Off-chain at
- 2026-08-26T11:12:54.370Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7RtzThQaLGqWXuiHYfK3RJ5NScY8fpxgP95J5mP1ZXB4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1435 chars)
{"actor":"judge","decided_at":"2026-08-26T11:12:54.202Z","decision":"review_approve","investigation_id":"9ef17dd6-b7aa-4c1a-ae5c-c52a6a15cc62","new_score":62,"page_slug":"thalaswap","prev_score":62,"reason":"The reviewer confirmed 10 of the page's 12 factual claims about the November 2024 ThalaSwap exploit against Thala's own post-mortem and independent outlets, including the $25.5 million loss, the $11.5 million asset freeze, the $300,000 bounty, the roughly 6.5-hour full recovery, and the OtterSec re-audit and rate-limit remediation. One claim was disputed (claim_findings[9]): the page implies the attacker received a $40,000 payment in addition to the bounty, when the primary source states that amount was personal compensation paid to the Thala founders, not the attacker — a payment-recipient misattribution rather than a dispute of the core incident facts. One claim about ThalaSwap V3's current TVL and the date it became the primary venue (claim_findings[10]) was only partially supported due to imprecise sourcing. With a disputed rate of about 8% ((1 disputed + 0 unverifiable) / 12), the page falls within the approval band, and the open coverage gaps are medium/low priority items about post-2025 developments rather than accuracy problems with what is currently published.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}