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 · Zora
View on Solana ↗
Sequence
#5
Score
71 → 71 (0)
Cluster
mainnet-beta
Slot
459441699
Off-chain at
2026-10-21T01:13:47.426Z
Anchored at
2026-10-21T01:13:52.247Z
Block time
—

Independent verification

1. Database (off-chain)
Nhi9S22cUeB1q8gsfJqGHveBQ7KX6HHiJGGzGvMTTGZ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1813 chars)
{"actor":"reviewer","artifact_identity":"a6bd97b5dbf8d6c610d2ffc40fd04852","decided_at":"2026-10-21T01:13:47.266Z","decision":"review","disputed_pct":0.087,"findings_hash":"7hyFSyMgbNTcN93zsVWhHKN5PkaGTvV3VLqif2FqaxMM","investigation_id":"917edc91-8570-4e0d-9dde-93d7ed92d823","mode":"findings_only","new_score":71,"page_content_hash":"8a93345a16a0200c74d1c716bdd606a5636de5c63ccbd916e245c33f392046d4","page_slug":"zora","prev_score":71,"reason":"The page is well-sourced and notably well-hedged: it explicitly labels the shutdown rumour as unretrieved/unverified rather than asserting it, and flags where aggregator price data conflict. Every load-bearing claim I checked — founding year, Coinbase Ventures backing, $60M/three-round raise, June 2023 L2 launch, April 2025 token launch with 10B supply, the October 2025 Robinhood listing and fee cut, the August 2025 ATH, the Karst upgrade date, the October 2026 liveness gaps, and the Zero Network mix-up — was independently confirmed against live sources. The main issues found are minor: (1) the L2BEAT archive_url snapshot (dated 2026-05-15) is stale relative to the July/October 2026 facts it is cited to support, even though the live L2BEAT URL does support them; (2) the claimed July 2026 ZORA price range could only be confirmed against September-October 2026 data on the cited aggregator; (3) Bybit's own page could not be fetched to verify its ATH figure directly, though the figure matches CoinGecko's BMD pair closely. No disputed or stale claims were found. Coverage gaps exist around on-chain/treasury analysis, chain fee/revenue data, and named leadership, none of which undermine the claims actually made.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}