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 · UPay
- Sequence
- #5
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 461974842
- Off-chain at
- 2026-10-27T06:49:02.408Z
- Anchored at
- 2026-10-27T06:49:15.000Z
- Block time
- 2026-10-27T06:49:15.000Z
Independent verification
- 1. Database (off-chain)
- DM2SaunibwKAB8Qmxcoyz18XoomFfkazvmYjbFER1hzm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1400 chars)
{"actor":"reviewer","artifact_identity":"4bab9560665dd22a5dd3ffe6afea70bf","blocked_count":2,"decided_at":"2026-10-27T06:49:02.203Z","decision":"review","disputed_pct":0.1667,"findings_hash":"GoCSn3WznuGQyiJjFL7XsvH7DCNS2a4pgKbRw6HmPD3S","investigation_id":"3cc0429e-ec7e-404f-9e16-fb08e210271c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"omissions":{"material":0,"total":1},"page_content_hash":"7a4b1946983e772cf8e9b9c59108ec6ab8d53ec3951f5b9f7740742d52db31b6","page_slug":"upay","prev_score":53,"reason":"The core of the page holds up: the Oct 2, 2026 ZachXBT allegation, the Sept 9, 2026 OFAC designation of Xinbi and its details, the UK Mar 26 action and the absence of confirming evidence are all corroborated, and the page is properly hedged. Open problems: the Yang quote and internal-investigation claim rest on a source that was blocked (the other cited sources predate any response), the Dubai-based claim is not supported by any source I could read, and the 52 TRON addresses figure was not found in fetched sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":5,"subject_status":"rebranded","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}