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 · Q2 2026 Bridge Exploit Wave
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 457810093
- Off-chain at
- 2026-10-16T22:50:46.816Z
- Anchored at
- 2026-10-16T22:50:52.248Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5aBWVEbS9xnkpWtyVy1oqQHfENRJdVHvmSwqKjF6b3qb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1951 chars)
{"actor":"reviewer","artifact_identity":"ee8029207da2c459a53f132e710ef592","decided_at":"2026-10-16T22:50:46.627Z","decision":"review","disputed_pct":0.3,"findings_hash":"Co1ukAHTmMRxsKST3tY3q5xKUFPXEvqZipZZgXWWMyCp","investigation_id":"83dae395-6719-4cb4-b5fc-4a2b875617e0","mode":"findings_only","new_score":0,"page_content_hash":"acb51649fb2ffb21c6d7a67a7915ff776841a3888fa4c37081a3756b0e1c6a9a","page_slug":"q2-2026-bridge-exploit-wave","prev_score":0,"reason":"The page's incident-level reporting is generally solid and well-sourced: the Drift, KelpDAO, Hyperbridge, THORChain, Verus, Syscoin, and Taiko exploit mechanics, dollar figures, and dates were independently verified against primary/official sources (THORChain's and Hyperbridge's own postmortems, CoinDesk, TRM Labs, The Block) and matched closely. However, the page contains a clear internal math/categorization error: it attributes 76% of 'bridge-related losses' to Drift+KelpDAO, but Drift is not a bridge exploit by the cited source's own classification, and the combined figure actually corresponds to 76% of total quarterly losses, not bridge losses. The summary's $340M total bridge-loss figure also conflicts with the $351M figure given in the page's own Overview section and in the externally verified CoinTelegraph reporting. The THORChain section conflates the v3.19.0 upgrade's release date (June 9, correct) with the network's actual trading resumption, which multiple outlets place at June 23, not 'early June.' A handful of granular technical details (Hyperbridge's dispatchIncoming/TokenGateway.onAccept path, Verus's checkCCEValues function name, Drift's exact 500M CVT collateral figure) could not be independently corroborated and are marked unverifiable rather than disputed, since no contradicting source was found either.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}