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 · DEXX
- Sequence
- #4
- Score
- 43 → 43 (0)
- Cluster
- mainnet-beta
- Slot
- 466749005
- Off-chain at
- 2026-11-08T02:34:25.792Z
- Anchored at
- 2026-11-08T02:34:44.000Z
- Block time
- 2026-11-08T02:34:44.000Z
Independent verification
- 1. Database (off-chain)
- 6TwKP7PqBjWnHXtYTFqeXxcDn88pCjzB78JssqET6n2m
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1462 chars)
{"actor":"judge","artifact_identity":"f8a507ffb2b21d7268059babc19bde4d","band_override":null,"decided_at":"2026-11-08T02:34:25.432Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"d2393658-2e61-48b5-aade-38c8857d81b4","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":43,"page_slug":"dexx","prev_score":43,"reason":"Of six claims checked, one (the Thala Labs ranking, claim_findings[5]) could not be supported and is internally inconsistent with the page's own $30M loss figure, which puts disputed plus unverifiable at 1 of 6 (about 17%). Two other claims were only partly supported: the 8,848 and 7,205 victim-address figures were not found in the fetched source (claim_findings[0]), and the 80% revenue pledge dates to Dec 6, not Dec 14 (claim_findings[4]). The core allegations (plaintext key storage, SlowMist figures, the $21M to $30M revision, the LBank coalition) were confirmed. The penalty is kept small because the reviewer's confidence is low (0.4) and most cited sources were not checked, but a high-priority gap on the platform's current status and payout progress after February 2025 keeps this at revise rather than approve.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}