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
- #7
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 462280265
- Off-chain at
- 2026-10-28T00:51:54.094Z
- Anchored at
- 2026-10-28T00:52:36.000Z
- Block time
- 2026-10-28T00:52:36.000Z
Independent verification
- 1. Database (off-chain)
- FXv9aLzvUPzzxGXEySCEnnXDiTXyUeNq12Dy4aJ7ed1q
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1426 chars)
{"actor":"reviewer","artifact_identity":"e6f8433dbe9260b148447d8a3f1ddaab","decided_at":"2026-10-28T00:51:53.975Z","decision":"review","disputed_pct":0.2,"findings_hash":"98wg3B2ToACw7jb2jCm88N65SVjoFS4fDXX1rt16CvRj","investigation_id":"30fb1b89-f9c9-4690-8e88-091075aef49e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":2,"total":3},"page_content_hash":"8269410a845e066c19d0c8580c0b7176cce5462fd3e7fadb1061d41fe5013874","page_slug":"kelpdao-layerzero-bridge-exploit-april-2026-dprk-lazarus","prev_score":0,"reason":"The core factual narrative holds: exploit size and timing, Lazarus/TraderTraitor attribution with its hedging, the Arbitrum freeze, the TRM figures and the lawsuit. The main problem is staleness. The page treats the frozen ETH as undisposed and outside DeFi United. Since then the Arbitrum DAO voted to release it, and a court order restricts it. The page also omits the resumption of rsETH operations. The '9-of-12' council vote has no support in the cited sources. Only a subset of claims was checked, and a few fetches were partial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}