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 · Allbridge Core Second Flash-Loan Exploit (July 2026)
- Sequence
- #10
- Score
- 0 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 462277630
- Off-chain at
- 2026-10-28T00:41:56.182Z
- Anchored at
- 2026-10-28T00:43:15.000Z
- Block time
- 2026-10-28T00:43:15.000Z
Independent verification
- 1. Database (off-chain)
- H7X4cdi9doaSWfrrBUnJb6qbMQQPi3gCQ5Zcs5NgXX2k
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1429 chars)
{"actor":"judge","artifact_identity":"be8df3cb25b4515515cac2a592df694c","band_override":null,"blocked_count":1,"decided_at":"2026-10-28T00:41:55.906Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"f74f4088-dfe6-458b-8b9f-d6ac9d197312","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"allbridge-core-second-flash-loan-exploit-july-2026","prev_score":0,"reason":"The core incident facts (about $1.65M loss, Kamino flash loan, protocol pause, LP withdrawal advice) were confirmed by CoinDesk (claim_findings[0]). One of four checkable claims could not be confirmed (claim_findings[3], the three-month CCTP and LayerZero transition), which puts the disputed share at 25%. Separately, the page states the BNB-only fix as settled fact while the cited TechTimes article is more hedged (claim_findings[1] and [2], partially supported). The reviewer's confidence was low (0.4), so the penalty is kept at the lower end of the band. A high-priority gap remains: no post-July status update is cited. One claim (claim_findings[4]) was excluded because its sources blocked the reviewer.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":4,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}