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 · Deguard
- Sequence
- #5
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 464789208
- Off-chain at
- 2026-11-03T05:56:58.459Z
- Anchored at
- 2026-11-03T05:57:28.000Z
- Block time
- 2026-11-03T05:57:28.000Z
Independent verification
- 1. Database (off-chain)
- 4B8jmmiwLK4yhrHfATDwhKjgH4RpmHKbv13XwG2ruc6j
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1357 chars)
{"actor":"reviewer","artifact_identity":"6dfd6efc577cd082e6c17a32741ce754","blocked_count":3,"decided_at":"2026-11-03T05:56:58.357Z","decision":"review","disputed_pct":0.1429,"findings_hash":"8digqhRxkA3u4SewWuJiXCNWQfS6gQ7wUgsFUGPRp9z2","investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_content_hash":"25603df5ca1711599fa9647c6097f228a3503845c42becad55065daa7c4f0dca","page_slug":"deguard","prev_score":51,"reason":"The page is heavily hedged and most checked claims hold: the anonymous team, unnamed audit and iOS inconsistency on iq.wiki, the DappBay Red Alarm label, and the 404 on deguard.io. One wording error: 'does not resolve' contradicts a 404, which means the server responded. The 'Inaccessible Website' flag was not seen on the DappBay detail page, which even offers a visit link. The Cyberscope, Venom and academic claims could not be read (source blocked) and are not scored. No shutdown, exploit or sanction found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}