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
- 8 → 8 (0)
- Cluster
- mainnet-beta
- Slot
- 462279520
- Off-chain at
- 2026-10-28T00:48:47.891Z
- Anchored at
- 2026-10-28T00:49:56.000Z
- Block time
- 2026-10-28T00:49:56.000Z
Independent verification
- 1. Database (off-chain)
- QsKMvU7LwwkpeTrDydNcDhnDPr9qqdDpjVoxvrVfRHm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1498 chars)
{"actor":"reviewer","artifact_identity":"fefcd9e37389e146bb094c30537e29e6","decided_at":"2026-10-28T00:48:47.781Z","decision":"review","disputed_pct":0,"findings_hash":"DmyqiXfaKgfrRsCDeo7HRB8BGGLavy6FcJjDerLJgVk9","investigation_id":"2c868a62-22c9-4050-8b38-3e0b960dec83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":8,"omissions":{"material":1,"total":1},"page_content_hash":"7231d56394f016db87b76f95b07afb5b5e30c02ae7f2d6144766b0e343b90606","page_slug":"june-2026-cross-chain-bridge-exploit-127m-three-protocols","prev_score":8,"reason":"The page's central framing, that the $127M three-protocol exploit is unverified and likely fabricated or garbled, holds up: the Nadcab post exists and my searches found no independent coverage. Syscoin details match Rekt News exactly. Weak points: the Humanity Protocol mechanism and asset breakdown (seven keys, 3-of-6 Safe, Hyperlane ProxyAdmin, 18,510 ETH, 1,548 BNB) are not in the cited CoinDesk page as fetched; the Nadcab summary presents the 03:54 detection time as the end of the attack and omits the post's internal contradictions. KelpDAO, Taiko, CoinGabbar and most other items were not re-fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}