Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#2
Score
42 → 42 (0)
Cluster
mainnet-beta
Slot
443509098
Off-chain at
2026-08-19T04:00:06.685Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
A7HPJvsFmATq6G5qJxEtTEYPtUMqhHc1C4AdTxv8amYV
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1421 chars)
{"actor":"reviewer","decided_at":"2026-08-19T04:00:06.482Z","decision":"review","investigation_id":"9ef17dd6-b7aa-4c1a-ae5c-c52a6a15cc62","new_score":42,"page_slug":"thalaswap","prev_score":42,"reason":"This page is unusually well-sourced: nearly every timeline claim about the November 15, 2024 exploit — including exact PST timestamps, wallet-address prefixes, dollar figures, and the two-line-patch root cause — was verified verbatim against Thala Labs' own post-mortem (retrieved via Wayback Machine) and corroborated by independent security-firm and news coverage. No unhedged allegations of wrongdoing were found; the page consistently frames the incident as an exploit the protocol suffered, not fraud it committed, and it accurately reports the full, same-day recovery of all $25.5M. Two minor defects were found: the claimed November 16 publication date for the detailed Medium post-mortem conflicts with that article's own self-reported November 26, 2024 byline, and the 'mid-2026 $2.23M TVL' figure, while traceable to a real data point, reflects unusually volatile TVL (which has since roughly halved on the same listing) rather than a stable current state. This review could not audit the page's actual section prose because the input supplied blank section content.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}