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 · Mixin Network
- Sequence
- #4
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 462182893
- Off-chain at
- 2026-10-27T19:06:27.948Z
- Anchored at
- 2026-10-27T19:06:39.000Z
- Block time
- 2026-10-27T19:06:39.000Z
Independent verification
- 1. Database (off-chain)
- 4SirrSzACJgoQo4xVu6sLnETueRxi9av3tzvXTn9zPVH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1330 chars)
{"actor":"judge","artifact_identity":"dec8d6e9058c56f9e49231664db7a84e","band_override":null,"decided_at":"2026-10-27T19:06:27.681Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"e12ac5bb-f642-49d6-8467-1c72ad1d83bb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"page_slug":"mixin-network","prev_score":63,"reason":"The core hack facts (date, roughly $200M loss, asset breakdown, exploiter data, and the February 2026 Tornado Cash movement) were confirmed against sources (claim_findings[0-4]). Two of ten checked claims (20%) were disputed or unverifiable: the October 2025 repayment update is cited to a Bitget article from February 2024 that does not contain it (claim_findings[5]), and the no-enforcement claim could not be verified (claim_findings[9]). The MDTu September 2026 deadline has also passed without the page saying whether it was met, a minor omission. The subject is still operating, so the page is not contradicted. Several background claims were not checked, which limits confidence.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}