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.

Decision
review · CYBERLEEK Token
View on Solana ↗
Sequence
#2
Score
8 → 8 (0)
Cluster
mainnet-beta
Slot
443510623
Off-chain at
2026-08-25T03:01:13.651Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HvX3R9xEEGo7aWBt4TY1gLvX6K1icvd3QithLXzVnGvx
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1384 chars)
{"actor":"reviewer","decided_at":"2026-08-25T03:01:13.535Z","decision":"review","investigation_id":"1e2462e5-693f-4f90-81f9-451e466d3552","new_score":8,"page_slug":"cyberleek-token","prev_score":8,"reason":"The page's core narrative — pre-built Solana token infrastructure preceding an alleged GTA VI leak, the DMCA subpoena campaign, and detailed wallet-cluster/profit analysis — is strongly corroborated by the cited Bitquery investigation and independently by Kotaku, GamesRadar+, CBR, Tom's Hardware, and other outlets found via search. The most substantive issue is a stale claim: the page describes an operator wallet as currently 'holding' 270 million tokens consistent with a gradual sell-off, but the page's own KuCoin source (cited elsewhere) reports those tokens were burned around Aug 22, 2026, a development omitted from the timeline. A minor internal inconsistency exists regarding whether certain trade/volume figures cover 'five days' or 'seven days.' Two claims could not be independently verified due to automated-fetch blocks (BeinCrypto, Bitcoin Foundation, both returning HTTP 403) and one Discord-handle list could only be partially corroborated. No claim was found to be actively contradicted by a more credible source.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}