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
- Sequence
- #3
- Score
- 18 → 8 (-10)
- Cluster
- mainnet-beta
- Slot
- 443521512
- Off-chain at
- 2026-08-26T15:36:28.941Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6rXGrXoCDkPWe93Y7gUxaNoJyExMQVRdfxkDKsRkTHu8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1873 chars)
{"actor":"judge","decided_at":"2026-08-26T15:36:28.292Z","decision":"review_revise","investigation_id":"e3ad1666-117b-460f-add3-88e6cde00c95","new_score":8,"page_slug":"allbridge-core-second-flash-loan-exploit-via-same-unpatched-vector","prev_score":18,"reason":"Fact-checking confirmed the large majority of this page's discrete claims — dates, dollar figures, TVL impact, fund-movement details, and the 2023 incident's specifics — against independent outlets and, in several cases, directly against Allbridge's own postmortem text. However, the page's central allegation embedded in its own title — that the July 2026 exploit ran through the same vector left unpatched since 2023 — rests on a claim the review found to misstate its sources: the sentence stating that two outlets 'reported that the single-pool fix explicitly missed Solana' (claim_findings[21]) is disputed, because both cited articles actually present this as an open, unexplained question rather than a confirmed fact, and a closely related claim making the same underlying point (claim_findings[20]) is independently rated only partially supported for the same reason. The page also does not reflect Allbridge's subsequent public commitment to a full architectural overhaul away from liquidity pools, or a third Allbridge exploit reported in mid-August 2026 that struck the very remediation path adopted after this incident (coverage_gaps, stale findings at claim_findings[31] and [39]). Because the sourcing problem sits at the evidentiary core of the page's framing rather than in a peripheral detail, and because material context postdating the page's research window is missing, the page is sent back for revision rather than approved outright or denied.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}