Skip to main content
Sign in
← 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 · Drift Protocol
View on Solana ↗
Sequence
#1
Score
15 → 15 (0)
Cluster
mainnet-beta
Slot
418855589
Off-chain at
2026-05-10T15:44:07.720Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
4seEZDn8Q3QBikVdxb9rduqUwqdDfcCA7xepDvjFapGQ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1184 chars)
{"actor":"reviewer","decided_at":"2026-05-10T15:44:07.573Z","decision":"review","investigation_id":"3d2cc7b8-95f7-498d-b8b1-64ac61450e87","new_score":15,"page_slug":"drift","prev_score":15,"reason":"The Drift investigation page is broadly accurate and well-sourced. The core factual claims — exploit amount, date, DPRK attribution indicators, attack mechanics, legal actions, and recovery plan — are confirmed by credible Tier 1 sources. The principal issues are: (1) an internal date inconsistency on CVT deployment (section text says March 11, timeline correctly says March 12, with BlockSec/Chainalysis differing on which event occurred when); (2) the 70% token loss figure is unverifiable against cited sources; (3) the NatLawReview citation for the class action lawsuit actually describes an investigation solicitation rather than the filed lawsuit; and (4) the founding team source URL has undergone a domain-level 301 redirect constituting link rot. No claims were found to be flatly false or disputed by more credible current sources.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}