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_revise · Thai-Southeast Asia $520M Cross-Chain Crypto Scam Network
- Sequence
- #3
- Score
- 0 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 462039468
- Off-chain at
- 2026-10-27T10:37:49.185Z
- Anchored at
- 2026-10-27T10:38:18.000Z
- Block time
- 2026-10-27T10:38:18.000Z
Independent verification
- 1. Database (off-chain)
- 6fGZb7A4EgVHRK8JXM3BptxqX5wM8qjzfUBQzwppYQCg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1480 chars)
{"actor":"judge","artifact_identity":"01b1ae60508cc35d00cc9ad3467ecfda","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T10:37:48.881Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"5bc4cc20-d576-4169-ab53-c291255d8016","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"thai-southeast-asia-520m-cross-chain-crypto-scam-network","prev_score":0,"reason":"The headline figures ($520M, 500+ wallets, ~$14M losses, 32 blockchains, $234M pre-labeled) were confirmed against Elliptic and Crypto Briefing (claim_findings[0], [1], [4]). Two of ten scored claims (20%) could not be confirmed: the report author and June 18 publication date (claim_findings[2], [3]), and the earliest verified coverage is dated June 20, before the stated June 24. The Drift attribution is worded more firmly than Elliptic's own hedged language (claim_findings[7]), a minor omission. One finding on Huione and FinCEN was not checked because the source was blocked, and it is excluded from the percentage as a coverage limit rather than a defect. No claim was disputed, and no material omission or subject-status contradiction was reported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}