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
#5
Score
63 → 63 (0)
Cluster
mainnet-beta
Slot
457744301
Off-chain at
2026-10-16T18:53:10.130Z
Anchored at
2026-10-16T18:53:36.389Z
Block time
—

Independent verification

1. Database (off-chain)
bPnqtxnjwftgVZ1d6j3ceq3hmaRTisDCVZWnJbtZaPN
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1927 chars)
{"actor":"reviewer","artifact_identity":"57b7beacd166c8010bd852bd5050b783","decided_at":"2026-10-16T18:53:09.961Z","decision":"review","disputed_pct":0.3846,"findings_hash":"9Ee88ZTivkaV3wwVJR1xEdjF7B474BfQZPDKZmjkyTDb","investigation_id":"69488b83-ebdf-40f0-8308-e1d2007a0d7b","mode":"findings_only","new_score":63,"page_content_hash":"d1f8904f880dbe8e00e2ae525fab7cc5f52688890e420dd86acccfc586dcadec","page_slug":"zrx-0x-protocol","prev_score":63,"reason":"The page's highest-severity claims hold up well: the September 2023 CFTC settlement against ZeroEx (date, co-respondents, $200,000 penalty, leveraged-token theory) and the January 2026 SwapNet/Matcha Meta exploit (date, dollar figure, affected-user count, Verichains attribution, core-contract non-involvement) are all independently corroborated by primary and reputable secondary sources, as is the 2019 samczsun vulnerability disclosure. However, the page contains one clear two-year date error that repeats in both prose and the timeline: it states the 0x v4 governance vote was approved in January 2023, when multiple sources including 0x's own blog place it in January 2021 (the '2,300+ holders' figure is itself accurate for that 2021 vote). It also overstates the ICO's backer/address count (13,000+ vs. the consistently reported ~12,000), narrows its own cited source's mid-2025 ZRX price range ($0.21-$0.25 vs. the source's stated $0.20-$0.30), and rests several Matcha-scale claims (130 sources, 16 chains, top-three ranking) on a now-dead DEXTools source that could not be independently corroborated. The April 2021 $2.40 near-ATH figure is supported by its cited source but conflicts with a dated contemporaneous price snapshot and with every price aggregator consulted, none of which records any 2021 peak at all.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}