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
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 463288800
- Off-chain at
- 2026-10-30T12:40:50.792Z
- Anchored at
- 2026-10-30T12:41:17.000Z
- Block time
- 2026-10-30T12:41:17.000Z
Independent verification
- 1. Database (off-chain)
- ANsh161rgxddr8aJP5mC2WrHHEhvNWGUjLHqhRHGjur1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1445 chars)
{"actor":"reviewer","artifact_identity":"a2c85649a10a8915e82c7d3d93d44751","decided_at":"2026-10-30T12:40:50.734Z","decision":"review","disputed_pct":0.2727,"findings_hash":"BSz6VeNuvv4mgivg1UrQLK6dss8Q76gFpnrP32cDf9kN","investigation_id":"14aa179b-7594-4ae0-8858-5ee069efca15","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":1,"total":2},"page_content_hash":"772a4d9832e2064e68f8722d9e41aede0ac011b6698ce0bf2002c13ddca0f11a","page_slug":"osmosis-allbtc-nomic-bridge-double-spend-exploit-september-2026","prev_score":38,"reason":"The core incident facts (June 25 minting, about 40.65 nBTC minted, 39.84 BTC counted as collateral, 22.65 BTC frozen, 36.03% impaired, 74-day lag, Nomic as the origin of the flaw) match the sources I fetched. The page is stale on remediation: an October 29, 2026 report says the governance proposal passed, while the page says it had not been executed. The Tornado Cash attribution to eGamers is unsupported, though Protos has the figure. The 25-transfer detail, the Nomic documentation details and the 2022 and 2023 history were not verified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}