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 · Wormhole
- Sequence
- #6
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 451868676
- Off-chain at
- 2026-09-30T05:21:10.560Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EAAj3TttFQRy3taYdqTyjoLsoqJka9xgHguCGTgXonex
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2021 chars)
{"actor":"reviewer","artifact_identity":"a843b406713fafdf332cf1c21d1ad56d","decided_at":"2026-09-30T05:21:10.341Z","decision":"review","disputed_pct":0.15,"findings_hash":"8hzJgztJvnd5mxuht6QmTMFRXkVYeNHS8hVbrN8WnAr3","investigation_id":"57924d6e-a4c7-4662-8069-3e5dd2071dba","mode":"findings_only","new_score":62,"page_content_hash":"0bd4d27bb722c8f1939dc84ad2ba73a1fc45beaf5030c632a4bd2974720306cf","page_slug":"wormhole","prev_score":62,"reason":"The page's core narrative — the February 2022 $326M exploit mechanism, Jump Crypto's 24-hour replenishment, the 2023 Oasis counter-exploit recovering ~$140M net, the November 2023 split from Jump Trading and $225M raise, the April 2024 W token launch, and Jump Crypto's unrelated 2024 CFTC/SEC regulatory troubles — is well-supported by the cited tier-1 and tier-2 sources and checks out against independent verification, including the technical exploit mechanics, on-chain addresses, and W tokenomics figures, which matched the official Wormhole blog exactly. Two distinct defects were found: the W token launch valuation conflates circulating market cap ($2.98B) with fully diluted valuation ($16.5B), understating FDV by roughly 5.5x, and repeats in both a section and the timeline; and the page twice misattributes the March 2024 New York proprietary-interest judgment to unnamed 'victims' when reporting indicates the claimant of record was Tai Mo Shan Limited (TMSL), the Jump Crypto entity that replenished user losses. The Immunefi bug bounty maximum ($5 million) could not be reconciled between conflicting current sources and is left unverifiable rather than corrected. No accepted community submissions exist to independently spot-check. Coverage gaps are moderate but not disqualifying: the page does not address attacker attribution/law enforcement status or the current disposition of the still-unrecovered balance.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}