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
- 465101659
- Off-chain at
- 2026-11-04T00:33:03.599Z
- Anchored at
- 2026-11-04T00:33:22.000Z
- Block time
- 2026-11-04T00:33:22.000Z
Independent verification
- 1. Database (off-chain)
- 7LfP2hGySfuBZ5bxCjebrNoDW8o6khejd8eykAsywNHN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1317 chars)
{"actor":"reviewer","artifact_identity":"8cdc450867044e99c3398effd2dc130f","decided_at":"2026-11-04T00:33:03.522Z","decision":"review","disputed_pct":0.375,"findings_hash":"AibFTrRH7ywT4vDCbEKFSQkRV1wfkUKDGEgzU4i1CXE9","investigation_id":"4f885635-d130-4b30-975b-91055a2292bd","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":38,"page_content_hash":"bdc9475b1581625ce643216dcbeb42b2c656c92fc92773bafb4b10b2a3f4de22","page_slug":"thorchain-gg20-mpc-vault-exploit-may-2026","prev_score":38,"reason":"Core incident facts (date, node join, bond size, loss, halt behaviour, patch, restart date) match the official report and press coverage. One error was found: the exploit report date is May 20 per the official post, but the page says May 21 in the summary and timeline. The 'third major incident' framing conflicts with the page's own list of 2021 attacks. The 20% vault share is not sourced. Many secondary claims were not checked because of the time budget and 403 blocks.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}