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.
- Sequence
- #5
- Score
- 12 → 12 (0)
- Cluster
- mainnet-beta
- Slot
- 464377212
- Off-chain at
- 2026-11-02T05:26:42.798Z
- Anchored at
- 2026-11-02T05:26:50.000Z
- Block time
- 2026-11-02T05:26:50.000Z
Independent verification
- 1. Database (off-chain)
- 5JntjcPtFD96rPivWzcJcNHiDK1ioS2ZbEeEDMSq21DL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1898 chars)
{"actor":"reviewer","artifact_identity":"00aa59edcab07021fb708c6f2ca5dd2f","decided_at":"2026-11-02T05:26:42.651Z","decision":"review","disputed_pct":0.0333,"findings_hash":"Aq8wLr3v6RmbCtePopePs7EzqmhzkXacvRmpHQSMzvoM","investigation_id":"196749fe-765a-46f0-ae2c-ff225f75a1c9","mode":"findings_only","new_score":12,"omissions":{"material":1,"total":2},"page_content_hash":"6609e01a7c8dcc19a8fc103fdd7a6f138ebf0c78e11d6f2a845fca9ed92c19f5","page_slug":"liquid-network-elements-cache-bug-exploit-september-2026","prev_score":12,"reason":"The page is well-sourced and its major claims -- the Sept 6, 2026 date, the ~4,000 BTC/~$319M drain, the 95% reserve depletion, the 3,400 BTC return and 598.5 BTC retained as a self-declared bounty, Blockstream's refusal, the technical cache-collision root cause, the SideSwap peg-out mechanism, the Guillemet quote, and the structural/governance criticism from Protos and Spark -- all independently check out against the cited sources and additional outlets. The one clear defect is a sequencing error in the 'Scale of Loss' section, which frames the network's pause as following the Sept 7 partial return when contemporaneous reporting (including The Block's own Sept 6 article) shows the pause began immediately after the Sept 6 theft, before any funds were returned. The page's coverage thins out considerably after Sept 11, 2026; more recent reporting through at least Oct 11, 2026 shows peg-outs remained fully frozen more than five weeks after the incident with no restart date, which the page's vague 'final stages of recovery' framing risks understating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}