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.

Sequence
#2
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
465103399
Off-chain at
2026-11-04T00:39:16.877Z
Anchored at
2026-11-04T00:39:35.000Z
Block time
2026-11-04T00:39:35.000Z

Independent verification

1. Database (off-chain)
DHMLUz2XUtrsH2uEwSkA5YH6cXWRchivHBeMSz4moffp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1220 chars)
{"actor":"reviewer","artifact_identity":"eb8bcec16e2da07c3035af74742bbc78","decided_at":"2026-11-04T00:39:16.812Z","decision":"review","disputed_pct":0.4286,"findings_hash":"2QMckUdcN7pEj5vjGHiwgKrWbaK6znx1jNmjHHwWboQU","investigation_id":"613516de-3e59-4110-bc78-249afc6bfd7b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"omissions":{"material":0,"total":1},"page_content_hash":"cc041c1b91d95c4a1abfd8ee44e0797d6adc9c56e4756b101a02a7da008b99a9","page_slug":"fake-trezor-support-social-engineering-282m-heist","prev_score":0,"reason":"Core facts (date, amounts, attack vector, laundering route, Monero impact, ZeroShadow freeze) are supported by reachable sources. One timeline date is wrong (Feb 16 vs the Feb 14 source), a $2M attribution figure could not be found, and Tornado Cash use is omitted. Limited sample of claims checked; many were not individually fetched.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}