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 · Flow
View on Solana ↗
Sequence
#4
Score
54 → 54 (0)
Cluster
mainnet-beta
Slot
453845921
Off-chain at
2026-10-06T08:20:05.242Z
Anchored at
2026-10-06T08:20:34.220Z
Block time
—

Independent verification

1. Database (off-chain)
HWrctP699a5fD9jvRNXaeuh7WjFEtJnbhfUyUpZ7QyBN
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2192 chars)
{"actor":"reviewer","artifact_identity":"954594311229cd00da188ba649df421a","decided_at":"2026-10-06T08:20:05.154Z","decision":"review","disputed_pct":0.2857,"findings_hash":"5iQZddNRdWXtmwmmcSMH9wgBCdGiKdyKN3JUurEziMCD","investigation_id":"e65bd29c-17e0-4b31-835b-e2e2473a7787","mode":"findings_only","new_score":54,"page_content_hash":"9979d7b65823f13e905d08672d26afe4fe7cf482792eec05ebe7915f6e81b356","page_slug":"flow","prev_score":54,"reason":"The large majority of atomic claims on this page — the December 2025 execution-layer exploit and its $3.9M loss figure, the rollback-then-reversal sequence, the deBridge/Shapiro backlash quotes, the South Korean exchange suspension/delisting timeline and Seoul court ruling, the SEC investigation closure details, the NBA Top Shot securities and VPPA privacy settlements, the layoffs, the FLOW price history, and the Messari Q1 2026 ecosystem statistics — check out against the cited sources, in several cases matching them nearly verbatim. Two outright errors were found: the page misattributes a precise $3.9M figure to on-chain analyst Wazz's own quote (he said 'around $4 million'), and it misattributes a combined Disney/NBA/NFL/Ticketmaster ecosystem total (100M NFTs, 13M fans) solely to Ticketmaster. A third sentence is internally inconsistent about whether February 12, 2026 was the delisting announcement date or the effective delisting date — the page's own later text (and outside reporting) makes clear Feb 12 was the announcement and March 16 was the effective delisting. Two sourcing problems were also found in the centralization section: both ainvest.com citations are inaccessible (403 on fetch, unarchivable per the page's own source metadata), leaving a precise 'institutional validator participation declined 4%' statistic and a 'single core client implementation' architectural claim without any way to independently check them. The page omits Dapper Labs' on-record denial of the $85M mansion allegation, though its hedged 'reported'/'alleged' language is otherwise appropriate.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}