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 · Zilliqa
View on Solana ↗
Sequence
#5
Score
65 → 65 (0)
Cluster
mainnet-beta
Slot
457750313
Off-chain at
2026-10-16T19:15:03.878Z
Anchored at
2026-10-16T19:15:25.438Z
Block time
—

Independent verification

1. Database (off-chain)
GhViCZbPyhEnKbD9j3iNhW7M3QEXqqQBivbjd5ETJnZF
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1582 chars)
{"actor":"reviewer","artifact_identity":"a739b6885ab232b94ca8f5af25b198d7","decided_at":"2026-10-16T19:15:03.514Z","decision":"review","disputed_pct":0.0833,"findings_hash":"41Lnpq8KRriGrFzqreb9pyW44Ck5cjAszkXXKrcecjMV","investigation_id":"ce7cc7ce-9d4c-4917-970b-fdb83d8d0837","mode":"findings_only","new_score":65,"page_content_hash":"9d6d70fdf3903d5e2ea131876907d165a18cfb85a5e326620fb9fb1939081a5b","page_slug":"zilliqa","prev_score":65,"reason":"This page is unusually careful for a live, unresolved story: nearly every factual claim checked against primary or multiple independent secondary sources held up, including the precise dollar/token figures from Zilliqa's own X-Bridge post-mortem, the CEO resignation timing, the ChainSecurity 2017 audit date, and the hedged, outlet-attributed framing of the disputed July 2026 root-cause claim. The one concrete defect found is a source/timeline mismatch: the 2026-07-21 timeline entry's source_url points to Cryptonomist, an outlet the page itself (correctly) describes as NOT corroborating the 'legacy ZIL1 wallet' claim, when the actual origin of that quote is CryptoTimes. A second, lower-severity issue is that the March 2025 Bithumb-speculation sentence in section 1 has no supporting citation among that section's listed sources, even though it checks out under independent search. No claims were found to be disputed, stale, or affected by link rot in sources that were reachable.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}