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
2 → 2 (0)
Cluster
mainnet-beta
Slot
443514712
Off-chain at
2026-08-25T13:44:18.146Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
7tdt7mUBsKMDLwwTxws4ARJaAbw32sTShxrFKSGxWGAn
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1090 chars)
{"actor":"reviewer","decided_at":"2026-08-25T13:44:17.758Z","decision":"review","investigation_id":"7b08e7ad-67e1-442e-b82a-62c08f9922d7","new_score":2,"page_slug":"mev-bot-scam-youtube-ai-trading-bot-campaign-2026","prev_score":2,"reason":"The page's technical and channel/wallet-specific claims are unusually well-supported and precisely match the primary SentinelOne/SentinelLABS report (exact hash, address, and URL matches), and it appropriately pushes back on an unsupported Solana-targeting claim rather than adopting it. The main problems are a recurring overstatement of total losses (page attributes 'exceeding $1 million' to SentinelLABS in three places, though SentinelLABS's own figure is 'more than $900k'), a minor address-count error in SlowMist-sourced figures, and one timeline entry (Q1 2024 'Nefture Security' loss figure) whose cited source does not contain the claim and whose firm attribution does not match any source found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}