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 · Tinyman
- Sequence
- #3
- Score
- 52 → 47 (-5)
- Cluster
- mainnet-beta
- Slot
- 425436500
- Off-chain at
- 2026-06-10T00:27:48.455Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- E6mLcYTH3HJuUsuFvemZF6c8kDUtHjph96tAH7YsGZxi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1408 chars)
{"actor":"judge","decided_at":"2026-06-10T00:27:48.265Z","decision":"review_revise","investigation_id":"0f8ef13b-c75f-411c-a011-e1e6771bb825","new_score":47,"page_slug":"tinyman","prev_score":52,"reason":"The review found zero disputed claims across 18 checked, with all core facts about the protocol, the January 2022 exploit, and the recovery response confirmed by Tier 1 sources. Four claims were rated partially_supported, all involving minor peripheral discrepancies: the transaction count in claim_findings[10] (page says 16, TRM Labs reports 17), a slight overstatement in claim_findings[3] attributing all $3M losses to wrapped BTC/ETH when ALGO and arbitrage losses are included, an unspecified day within August 2021 in claim_findings[7], and an approximate characterization of the v2 audit scope in claim_findings[16]. One citation (coin.fyi, Tier 3) is link-rotted and the v1.1 relaunch date it supported is therefore unverifiable. A high-priority coverage gap flags the absence of any post-exploit law enforcement outcome. These issues are editorial in nature and do not impugn the accuracy of the page's core narrative; a light revision to correct the transaction count, soften the loss attribution wording, and replace the dead citation is warranted.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}