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 · Shibarium Bridge Flash Loan Exploit (September 2025)
- Sequence
- #3
- Score
- 22 → 14 (-8)
- Cluster
- mainnet-beta
- Slot
- 461973581
- Off-chain at
- 2026-10-27T06:44:22.673Z
- Anchored at
- 2026-10-27T06:44:48.000Z
- Block time
- 2026-10-27T06:44:48.000Z
Independent verification
- 1. Database (off-chain)
- HcRT5iwNavUeBoGRZB6S2G96eaxdLG9ugHtSdsGHXrBd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2082 chars)
{"actor":"judge","artifact_identity":"4bcdab02c4b1a9ccd907cd4551af9f31","band_override":null,"decided_at":"2026-10-27T06:44:22.336Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"6771ec46-d413-494b-aee3-28e5e0551943","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":14,"page_slug":"shibarium-bridge-flash-loan-exploit-september-2025","prev_score":22,"reason":"None of the nine reviewed claims was disputed or unverifiable, so the claim-based dispute rate is 0%. The core account (September 12, 2025 exploit, 4.6M BONE flash loan, 10 of 12 keys, 6-of-9 multisig, BONE recovery, October 14 relaunch) was confirmed (claim_findings[0], [3], [2]). The page is revised because omission_findings[0] shows it leaves out the December 2025 K9 Finance compensation dispute, and no later compensation status is given (omission_findings[1], high-priority coverage gap). Further weaknesses are two archive URLs that point to unrelated articles (claim_findings[6], [7]) and the 50 ETH bounty and 1,200-wallet figures, which are not in the sources cited for them (claim_findings[1], [2]). The reviewer's confidence is moderate (0.5) and many sources could not be fetched, so the penalty is kept at the low end.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"No claim finding was disputed or unverifiable (0%), but omission_findings[0] is material: the December 2025 K9 Finance threat to leave Shibarium over unresolved compensation is missing, and the page's K9 section reports only its cooperation. A high-priority coverage gap (post-October 2025 follow-up) points the same way. Escalated one band from approve to minor, not further, because the core narrative is confirmed and no shutdown, sanction or contradiction of the page was found."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}