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 · Tinyman
- Sequence
- #4
- Score
- 47 → 47 (0)
- Cluster
- mainnet-beta
- Slot
- 459485644
- Off-chain at
- 2026-10-21T03:51:37.692Z
- Anchored at
- 2026-10-21T03:52:03.912Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5Le3XN8WM8NX4gDyeERFtsd7dR65SXaNqk3cpKVUffsv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2006 chars)
{"actor":"reviewer","artifact_identity":"159ad34f5d224ad5148fd97c4369ae39","decided_at":"2026-10-21T03:51:37.515Z","decision":"review","disputed_pct":0.1935,"findings_hash":"3w2Mr6svEgWfwk91n4qeaw37T44qqi2o5DJqzxCQKTDC","investigation_id":"0f8ef13b-c75f-411c-a011-e1e6771bb825","mode":"findings_only","new_score":47,"page_content_hash":"a1965d7277ff0d4d0a10c478a0b89e7878f9c077d9dd0a5c80fbd214ffb80b7c","page_slug":"tinyman","prev_score":47,"reason":"The page's core narrative -- the January 1, 2022 burn-function exploit, the roughly $3 million loss across 43 pools, the compensation program, and the v2.0 Tealish rewrite -- is well supported by Tinyman's own technical reports, TRM Labs, Halborn, and CoinDesk, and several granular figures (Account 1's exact token amounts, the 70% damage share, the 1.2M ALGO arbitrage figure, the 10%/investor compensation funding split with Borderless Capital, Meld Ventures and Jump Capital named) were independently corroborated. Two defects stand out: the audit-to-exploit gap is misstated as \"approximately ten weeks\" when the actual interval (Sept 21, 2021 to Jan 1, 2022) is about fourteen weeks, and the sole citation for the January 19, 2022 relaunch (coin.fyi) is now a dead link that redirects to an unrelated maintenance page, appearing in three places on the page. A handful of specific statistics -- the 19:03 UTC start time, the 90-95% liquidity-saved figure, the $210,000/12-wallet secondary-attacker breakdown, the ~250 affected LPs, and the exact exclusion block number -- could not be confirmed or refuted because the primary Medium sources blocked automated fetching and web.archive.org was unreachable in this environment; these are marked unverifiable rather than disputed. No evidence of post-2023 developments, regulatory history, or the disputed Choice Coin compensation claim is present on the page.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}