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 Trade
View on Solana ↗
Sequence
#1
Score
10 → 10 (0)
Cluster
mainnet-beta
Slot
418756680
Off-chain at
2026-05-10T04:40:46.214Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CnTSrvaRyN74ko3QveZy8yrhkimEUSRWK4Lmc5AjoSC3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (996 chars)
{"actor":"reviewer","decided_at":"2026-05-10T04:40:46.125Z","decision":"review","investigation_id":"6c0e3163-225d-4120-a3c9-f112d15456a4","new_score":10,"page_slug":"drift-trade","prev_score":10,"reason":"The core factual record — two incidents, $14.5M in May 2022 and approximately $285M on April 1, 2026, both on Solana — is substantiated by multiple Tier 1 sources. The primary weaknesses are: (1) the entity name 'Drift Trade' is a sub-brand slug used by DeFiLlama but not the canonical name ('Drift Protocol') used in all authoritative reporting; (2) the sole cited URL (DeFiLlama's hacks filter page) returns HTTP 403 and cannot be verified as a live citation; and (3) material context is absent, including DPRK attribution for the 2026 hack, the ambiguous (non-malicious) nature of the 2022 incident, and post-hack recovery and legal developments.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}