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
- #4
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 457981348
- Off-chain at
- 2026-10-17T09:08:22.080Z
- Anchored at
- 2026-10-17T09:08:27.063Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EcreUdS5AZiUpb2WUrovvNGi42CjedUCAQzrqrF9LQcH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2298 chars)
{"actor":"reviewer","artifact_identity":"d1870114fe08e29a4e3a41c8911de3cf","decided_at":"2026-10-17T09:08:21.943Z","decision":"review","disputed_pct":0.1154,"findings_hash":"EocxLWEMKzYjomEZijjsQ3cGRaLjgoQfie1ZPHk4i4nL","investigation_id":"d93f8bac-a89c-4acf-9ac0-1ba862a52279","mode":"findings_only","new_score":2,"page_content_hash":"f3679b84b8939b464d767e604c32715dcfdd7e43ce02816fab465077310615f1","page_slug":"olpc-bnblabubu-token-pancakeswap-pool-exploit","prev_score":2,"reason":"The page's core narrative — a June 20, 2026 exploit of the OLPC/LABUBU pool on PancakeSwap V2 via a pre-planted decimalsValue parameter and a resulting reserve desynchronization — is well corroborated by multiple independent tier-2 outlets and is not contested. Specific figures (burn amounts, USDT extracted, the exact decimalsValue integer, the $60.03M June DeFiLlama total) check out against sources. Three issues stand out: (1) the page asserts as settled fact that 633.4 ETH was bridged to Ethereum and deposited into Tornado Cash, but AMBCrypto and a CoinDesk-sourced KuCoin report explicitly found no evidence of this for this specific incident, a conflict the page does not acknowledge, appearing in the summary, the Fund Movement section, and the timeline; (2) the page states that 'security researchers and analysts widely characterize' the sequence as a premeditated rug pull, when the underlying reporting shows this framing is driven mainly by social-media speculation rather than a confirmed consensus among named security firms, which have generally stopped short of confirming intent; (3) the timeline assigns exact calendar dates (2026-05-05, 2026-05-06) to events that sources describe only as 'approximately 46 days before' and 'a few days later,' presenting invented precision, with the one-day gap between the two dates in tension with Odaily's 'a few days later' framing. A cited source (Bitcoin World) has gone dead (HTTP 410) though an archive copy is already on file. Overall the page is largely accurate but overstates certainty on two narrative-shaping claims (rug-pull consensus, Tornado Cash) and introduces false precision in its timeline.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}