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
review · Nomad
- Sequence
- #2
- Score
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 464354348
- Off-chain at
- 2026-11-02T04:05:01.574Z
- Anchored at
- 2026-11-02T04:05:07.000Z
- Block time
- 2026-11-02T04:05:07.000Z
Independent verification
- 1. Database (off-chain)
- HLKQbmMSEbgvoJBnBmVvnm3Cr4AsB8yazXaY66A5eke7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1516 chars)
{"actor":"reviewer","artifact_identity":"231e5d16c4d739c4a2cfec1a70e7b1a2","decided_at":"2026-11-02T04:05:01.520Z","decision":"review","disputed_pct":0.125,"findings_hash":"5bq3oESnjgcW8TYkjzDS1cD3WAq8Z3npSx9Qep2QhnhU","investigation_id":"f9e685c5-2870-4b10-914f-b599ddbdbd9c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":1,"total":3},"page_content_hash":"72a9100ffea27946cf723fa2af405d66fe7af39f73426da5ab29e7f8f2b5d2c4","page_slug":"nomad","prev_score":10,"reason":"The core narrative (the June 2022 zero-root bug, the Aug 2022 drain of about $190M, the Mandiant clustering, the Gurevich indictment and arrest, the FTC proposed order) is well supported. Errors are mostly framing: the FTC's allegations are described as 'findings' in the Risk Assessment, the proposed $37.5M obligation is counted as 'recovered', and the proposed order is not labelled non-final in the summary. The announcement date may be a day off (Dec 16 vs Dec 17). The page omits the reported late-October 2026 extradition of Gurevich to the US, which I could not verify against a primary source. The Quantstamp and audit-drift claims were not independently checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","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}