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
- Sequence
- #6
- Score
- 7 → 7 (0)
- Cluster
- mainnet-beta
- Slot
- 459468820
- Off-chain at
- 2026-10-21T02:51:05.781Z
- Anchored at
- 2026-10-21T02:51:31.653Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2EKX4CsN3CoN5oMMaop1cs7Tyb87qZovWLHpLJWH6Ekt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2049 chars)
{"actor":"reviewer","artifact_identity":"161788219288ccab648ef286396d33e3","decided_at":"2026-10-21T02:51:05.553Z","decision":"review","disputed_pct":0.2593,"findings_hash":"61RUeqnd3o4fuXNyaE8H7EGv8MxPSCLg2wx38VwGyzxT","investigation_id":"806b1308-839e-448e-b7c1-b36060b36e6c","mode":"findings_only","new_score":7,"page_content_hash":"46444b46d5f849813c0df4b2d5f8a0cb96058fc7181a4080a52cb936a03f1f46","page_slug":"h1-2026-crypto-project-shutdown-wave-100-projects","prev_score":7,"reason":"The page's broad quantitative skeleton — closure counts (~99-110 projects), VC funding collapse figures, and the dates/mechanics of the largest individual closures (BitMEX, Movement Labs, Loopring, Nifty Gateway, ZeroLend, Dmail Network) — holds up well against independent sourcing and is generally confirmed. The most serious problems are concentrated in two places: a fabricated-looking statistic attributing '62 projects... $200 million in venture capital' to Bitcoin.com News (the cited article contains no such aggregate), and a disputed breakdown of H1 2026 hack losses that substitutes two small, unrelated incidents (Resolv, CowSwap) for what Blockaid's own reporting actually names as the third major incident (Humanity Protocol), inflating the stated loss-share from ~55% to ~64%. A related overstatement puts the MOVE token market-making dump at '~5% of supply' when the cited source's own total-supply figure implies under 1%. The BitMEX regulatory history, while accurate as far as it goes, omits the 2025 presidential pardons of the three founders, leaving a stale impression of their legal status. One dead citation (Frontierbeat, for the Dmail Network timeline entry) was found and a live replacement identified. The page has no on-chain evidence of its own despite the platform's on-chain-anchoring premise, and a list of nine smaller closed projects is asserted with no individual sourcing at all.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}