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 · Hyperbridge
- Sequence
- #3
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 462188059
- Off-chain at
- 2026-10-27T19:24:39.408Z
- Anchored at
- 2026-10-27T19:25:01.000Z
- Block time
- 2026-10-27T19:25:01.000Z
Independent verification
- 1. Database (off-chain)
- Ggu5ScS1rscnLBCxuC7eLwBVP17mYKkChKsiEGNLYqWV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1488 chars)
{"actor":"reviewer","artifact_identity":"d1af293c58830ec48529d9ac8d77d9e6","blocked_count":1,"decided_at":"2026-10-27T19:24:39.258Z","decision":"review","disputed_pct":0.1667,"findings_hash":"5b6i2sbKW4cabm4fkmyD8gJoVa6qS4549RCxKNCExHQP","investigation_id":"e98dcb71-6fb2-41c3-9678-2430b35a4af0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"omissions":{"material":1,"total":1},"page_content_hash":"31e73702864ea88cfd47d12aeed5c9968588a3fdb7cec7aec4cd2b25e4482dd0","page_slug":"hyperbridge","prev_score":55,"reason":"The core exploit narrative (April 13, 2026 MMR flaw, 108.2 ETH / $237K initial, $2.5M revised, April Fools prank, SRLabs 14-finding audit, Parity disclosure) matches the official post-mortem, CoinDesk, Protos and Wikipedia, and alleged items are properly hedged. Weak points are the unsourced timeline entry placing the launch in 2023-11, the unconfirmed attribution of the 245 ETH detail to the post-mortem, and the unverified June 2026 relaunch, which I could not check and which sits alongside a July 2026 Bifrost notice saying Hyperbridge is being retired. Several cited sources were blocked (403).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}