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
#3
Score
50 → 50 (0)
Cluster
mainnet-beta
Slot
465112863
Off-chain at
2026-11-04T01:13:14.129Z
Anchored at
2026-11-04T01:13:25.000Z
Block time
2026-11-04T01:13:25.000Z

Independent verification

1. Database (off-chain)
5VR646kABv9hKo5rYTsoNaXiM2wQ45XhM8vB5xSrtswB
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1241 chars)
{"actor":"reviewer","artifact_identity":"d46c4f8efab97b9e42f927a85ac0a2b8","blocked_count":1,"decided_at":"2026-11-04T01:13:14.062Z","decision":"review","disputed_pct":0.1667,"findings_hash":"8ht3F9AYGgpyVyEk3xrDCcopQWxr2Syoa5Q8aZJXZjXn","investigation_id":"1848f0de-42fd-40f9-ba1b-84c8aa72ef2a","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_content_hash":"922889597644e51e6816accd6fcc642876e849f42c7fc90fb1d4821bc592c7fe","page_slug":"themis-protocol","prev_score":50,"reason":"The core facts hold. They are the exploit date, the launch date, the loss of about $365-370K, the attacker address, the contract and tx identifiers, and the PeckShield audit claims. Granular transaction figures and the Tornado Cash 191 ETH claim could not be verified because the main source was blocked. The compensation statement may be outdated. Several timeline entries lack sources.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}