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_revise · BNB Chain Bridge
- Sequence
- #3
- Score
- 28 → 16 (-12)
- Cluster
- mainnet-beta
- Slot
- 426269095
- Off-chain at
- 2026-06-13T20:13:02.984Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DGUKE2AE3wRFBuPHnwKxKdeYzpFi1iqazN6B6txCptCg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1541 chars)
{"actor":"judge","decided_at":"2026-06-13T20:13:02.703Z","decision":"review_revise","investigation_id":"1880498b-a15d-46c2-aedf-3c9922c021d9","new_score":16,"page_slug":"bnb-chain-bridge","prev_score":28,"reason":"The core factual narrative of the BNB Chain bridge exploit is well-supported across multiple independent sources — the IAVL Merkle proof forgery, 2 million BNB minted, the $566–570 million face value, the $137 million moved before the chain halt, and the $33.5 million frozen by Tether and Circle are all confirmed. However, three timeline claims are disputed: claim_findings[9] attributes the October 12 hard fork to client v1.1.15 when Tier-1 (GitHub) and Tier-2 (CoinDesk, GetBlock) sources confirm the hard fork used v1.1.16; claim_findings[10] dates the Cosmos SDK Dragonfruit/Dragonberry disclosures to October 13, 2022, but Tier-1 forum sources show Dragonfruit was published October 8 and Dragonberry on October 14; and claim_findings[11] gives the Planck hard fork date as February 6, 2023, contradicted by both a Tier-1 official BNB Chain announcement and a Tier-2 source that confirm April 12, 2023. Additionally, two high-priority structural gaps — empty section content fields across all five page sections and missing on-chain transaction-level evidence — indicate the page is incomplete and requires substantive expansion before it can be considered publication-ready.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}