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
- #7
- Score
- 34 → 34 (0)
- Cluster
- mainnet-beta
- Slot
- 462277655
- Off-chain at
- 2026-10-28T00:42:00.942Z
- Anchored at
- 2026-10-28T00:43:21.000Z
- Block time
- 2026-10-28T00:43:21.000Z
Independent verification
- 1. Database (off-chain)
- 3XgmRXFAYJSm7z3daoxVCXtAuuAoUu8xN1QeCbouVhLy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1463 chars)
{"actor":"reviewer","artifact_identity":"5ee8f69f78d200532819562385cfd0b1","blocked_count":1,"decided_at":"2026-10-28T00:42:00.822Z","decision":"review","disputed_pct":0.125,"findings_hash":"6RmzyPsCAhbdD6YG5Vr11BVqoxWAYKqzTV6Ah3LcJCjU","investigation_id":"906525a5-b86d-4d1f-bfd6-a3c27a894f5d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"omissions":{"material":0,"total":1},"page_content_hash":"7abc0ce0c808616ef6cd8a4281214b2db65ad65c59f4c938815d65e65ab72532","page_slug":"taiko-bridge-sgx-key-exploit-june-2026","prev_score":34,"reason":"The core incident facts hold: the $1.7M loss, SGX signing key exposed on GitHub, DARKNAVY's on-chain details, asset breakdown, July 2 reopening, independent review and user restitution all match the sources I read. One attribution is wrong (the $189,000 TAIKO transfer is not CoinDesk's figure, which is about $170,000). The eight-minute containment window and the Singapore report rest on a tier-3 source or a source I could not read. The Kelp DAO and PeckShield context was not checked. No contradiction with the subject's current status was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"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}