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 · Juicebox V3
- Sequence
- #5
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 457846778
- Off-chain at
- 2026-10-17T01:02:50.549Z
- Anchored at
- 2026-10-17T01:03:00.986Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 52vwWaNgnDigE5k987tFnob9JVECxe31kvATRVwyEfdd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1732 chars)
{"actor":"reviewer","artifact_identity":"ad755506be27f0799de855fe8d984032","decided_at":"2026-10-17T01:02:50.228Z","decision":"review","disputed_pct":0.1429,"findings_hash":"78R9oiWmZxub47DKkG7ekJ29kmhMEKSnncEy5QxGUUkn","investigation_id":"aa4a488c-c321-4985-82b4-91bf919259f1","mode":"findings_only","new_score":63,"page_content_hash":"50bbbc46c67083e5a5bfdfb7d9d2fb72fee1acd7617e2d797c46d6ce5f2738cc","page_slug":"juicebox-v3","prev_score":63,"reason":"The page's historical and technical backbone -- the Code4rena V3 and Buyback Delegate audit findings, the V3/V3.1/V3.1.1/V3.1.2 deployment dates and fixes, the May 2022 JBFundingCycleStore postmortem, the ConstitutionDAO figure, and the April 2022 AssangeDAO 583.755 ETH transfer -- is well-supported by primary sources fetched directly during this review and is accurate in its core facts. Weaknesses cluster around two newer, less-sourced sections: the claim that JBX is listed on Coinbase, MEXC, and Bitget is contradicted by MEXC's own 'Unlisted' designation and by CoinGecko/CoinMarketCap market data showing JBX trades almost exclusively on Uniswap V3 with minimal volume; and the entire ZachXBT section rests on an unsourced flag that the page itself admits cannot be substantiated. A secondary issue is that the page attaches a 2024 CoinTelegraph report about a later, unrelated AssangeDAO transfer to its narrative of the 2022 events, conflating two distinct incidents. The April 2026 exploit claim is accurately attributed to a single DeFiLlama database entry (confirmed), though no independent corroborating write-up exists.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}