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 · Hyperbridge
- Sequence
- #4
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 462188064
- Off-chain at
- 2026-10-27T19:24:39.590Z
- Anchored at
- 2026-10-27T19:25:02.000Z
- Block time
- 2026-10-27T19:25:02.000Z
Independent verification
- 1. Database (off-chain)
- CJuaipoHgMMmvgSZc854HviFPdw6imDQ75fxU82YSU5M
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2061 chars)
{"actor":"judge","artifact_identity":"d1af293c58830ec48529d9ac8d77d9e6","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:24:39.258Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"e98dcb71-6fb2-41c3-9678-2430b35a4af0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"hyperbridge","prev_score":55,"reason":"Of 14 claim findings, 13 count toward the percentage after leaving out one blocked source (the June 2026 relaunch, claim_findings[12]). None were disputed. Two were unverifiable: the 245 ETH attribution to the post-mortem (claim_findings[4]) and the unsourced September 2025 Polygon expansion (claim_findings[11]), giving about 15%. The core exploit narrative is confirmed by the post-mortem, CoinDesk and Protos, and alleged items are hedged. The page is revised and penalised toward the upper part of the minor band because the reviewer found a material omission, a July 2026 Bifrost notice saying Hyperbridge is being retired, and the page presents the June 2026 relaunch without caveat. Two timeline items are also weak: the unsourced November 2023 launch date (claim_findings[10]) and the unconfirmed April 16 production deployment (claim_findings[9]). A high-priority gap on current protocol status remains open.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The Bifrost retirement notice is a material omission, but it comes from a single partner rather than an official Polytope Labs or Hyperbridge notice, and the reviewer could not establish the protocol's current status (subject_status.contradicts_page is false). The minor band already applies and is set at the harsher end for this omission, so no further escalation is warranted."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}