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 · xToken
- Sequence
- #4
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 464445314
- Off-chain at
- 2026-11-02T09:29:23.839Z
- Anchored at
- 2026-11-02T09:29:44.000Z
- Block time
- 2026-11-02T09:29:44.000Z
Independent verification
- 1. Database (off-chain)
- CDL4ei42UkVjkJ5DnJabDZ4BsBbeRFRd6jRHSuzSMo4Y
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1424 chars)
{"actor":"judge","artifact_identity":"b0265ece28da6c02567ccaa93db093c5","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T09:29:23.588Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"e1f52b35-22bd-40ff-b8ca-12bded5dbd8d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"page_slug":"xtoken","prev_score":56,"reason":"The core facts of both 2021 exploits (loan sizes, stolen assets, the access-control flaw and the audit timing) were confirmed against rekt.news and Halborn (claim_findings[0-4]). About 29% of checkable claims could not be verified: the ZachXBT flag and 10/100 trust score have no supporting source (claim_findings[5]), and the 99.84% token decline does not match the stated price of $0.0000244 against a roughly $1.36 peak (claim_findings[6]). The compensation figures could not be checked because the source was blocked, so they were left out of the percentage. The page also does not establish whether the protocol is still operating, a high-priority gap. Reviewer confidence was moderate, so the penalty stays at the lower end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}