Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Deguard
View on Solana ↗
Sequence
#6
Score
51 → 52 (+1)
Cluster
mainnet-beta
Slot
464789213
Off-chain at
2026-11-03T05:56:58.677Z
Anchored at
2026-11-03T05:57:29.000Z
Block time
2026-11-03T05:57:29.000Z

Independent verification

1. Database (off-chain)
3Dq5f2SKbgDVNsMEhvrH9FW51xSWsFQgqmfDhDisJ3gA
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1465 chars)
{"actor":"judge","artifact_identity":"6dfd6efc577cd082e6c17a32741ce754","band_override":null,"blocked_count":3,"decided_at":"2026-11-03T05:56:58.357Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"c346b0e9-500f-4078-90fe-b4647eab3df7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"deguard","prev_score":51,"reason":"Of 10 claims checked, 3 could not be read because the sources blocked the reviewer and are excluded; 1 of the remaining 7 (about 14%) could not be verified. The 'Inaccessible Website' flag on DappBay (claim_findings[2]) was not found on the detail page, and the page wrongly says deguard.io 'does not resolve' when it returns an HTTP 404 (claim_findings[3]). The core findings hold: the anonymous team, the DappBay Red Alarm high-risk label and the 404 on deguard.io were confirmed, and no shutdown, exploit or omission was found. A high-priority gap remains because no on-chain token or contract analysis has been done.","replaces_fact_checks":{"score_before_fact_checks":60,"undone":2},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":1,"score_limit":{"applied":-8,"limited":true,"proposed":-10,"rule":"second_opinion_agreed","second":-8},"scored_claims":7,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}