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_approve · Deguard
- Sequence
- #8
- Score
- 52 → 60 (+8)
- Cluster
- mainnet-beta
- Slot
- 470685908
- Off-chain at
- 2026-11-17T21:34:02.687Z
- Anchored at
- 2026-11-17T21:34:10.000Z
- Block time
- 2026-11-17T21:34:10.000Z
Independent verification
- 1. Database (off-chain)
- Ge1WcnaHtZARPPH35g6Sm3TcAxW2bGgACqUqpjmEmQ6D
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1411 chars)
{"actor":"judge","artifact_identity":"12df3e00703a230cf0da11fcaa5bce21","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:34:02.378Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":60,"page_slug":"deguard","prev_score":52,"reason":"Four of the five claim_findings were checked and confirmed, including the DappBay Red Alarm rating (claim_findings[0]), the deguard.io HTTP 404 (claim_findings[1]) and the iq.wiki contents (claim_findings[2], [3]). The fifth (claim_findings[4], Cyberscope audit) was blocked by rate limiting and is excluded from scoring, leaving 0% disputed. The review found no shutdown, sanction or exploit and no omissions. The one high-priority coverage gap, on-chain token analysis, is already stated on the page as an open gap, so it suggests expansion rather than a penalty. Venom, AirdropAlert and Cyberscope sources were not re-checked, so the review is only moderately thorough.","replaces_fact_checks":{"score_before_fact_checks":60,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":8,"scored_claims":4,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}