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
- 38 → 23 (-15)
- Cluster
- mainnet-beta
- Slot
- 463288805
- Off-chain at
- 2026-10-30T12:40:50.970Z
- Anchored at
- 2026-10-30T12:41:18.000Z
- Block time
- 2026-10-30T12:41:18.000Z
Independent verification
- 1. Database (off-chain)
- BSU4hDD5LfZeNedJLgGAiyfuGA5VUf7tT1eBJf7uqLPN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2440 chars)
{"actor":"judge","artifact_identity":"a2c85649a10a8915e82c7d3d93d44751","band_override":null,"decided_at":"2026-10-30T12:40:50.734Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2727,"investigation_id":"14aa179b-7594-4ae0-8858-5ee069efca15","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"page_slug":"osmosis-allbtc-nomic-bridge-double-spend-exploit-september-2026","prev_score":38,"reason":"The core incident facts on the page (June 25 minting, about 40.65 nBTC minted, 22.65 BTC frozen, 36.03% of collateral impaired, 74-day disclosure gap, flaw originating in Nomic's code) were confirmed by the reviewer (claim_findings[4], [7]). However, the page's summary and its remediation section say the fix had not been executed. A later report dated October 29, 2026 says Osmosis governance passed the proposal (claim_findings[0], [1]; omission_findings[0]), so the page's current-status conclusion is out of date. Smaller issues also apply: the 671 ETH Tornado Cash figure is credited to eGamers, which does not report it; the 25-transfer count, the Nomic documentation details and the 2022 and 2023 history could not be checked; and the page relies only on secondary news sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"score_limit":{"applied":-15,"limited":false,"proposed":-15,"rule":"second_opinion_agreed","second":-18},"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"Computed from claim_findings, 3 of 11 findings are unverifiable (not_found) and none are marked disputed, giving 27%, which is the minor band. The reviewer also found that the page's summary and its high-severity section 'Proposed Governance Remediation Remains Unexecuted' are out of date (claim_findings[0] and [1], stale). subject_status.contradicts_page is true and omission_findings[0] is material, because an October 29, 2026 report says the remediation proposal passed. This changes the page's main conclusion about the current state of the exploit, so the percentage band understates the problem. Escalated to significant, at the lenient end of that band because the update is a single secondary-source report and the core incident facts are confirmed."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}