Skip to main content
Sign in
← 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 · Anza
View on Solana ↗
Sequence
#2
Score
74 → 74 (0)
Cluster
mainnet-beta
Slot
423507968
Off-chain at
2026-06-01T03:12:27.924Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
6jvDCsfZ34RpCErjvAust7dsSLAxsU9nqMgaeb7QMd4Z
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1180 chars)
{"actor":"reviewer","decided_at":"2026-06-01T03:12:27.767Z","decision":"review","investigation_id":"83fa375e-fe5d-4d90-8113-e50091f2a566","new_score":74,"page_slug":"anza","prev_score":74,"reason":"The Anza investigation page is largely accurate and well-sourced, with all major claims confirmed or partially confirmed by credible sources. Three notable inaccuracies were identified: (1) the Funding section incorrectly states Anza has not disclosed its funding source, when a Solana Foundation grant was publicly confirmed by the CEO at launch; (2) Agave 3.0 is described as 'released to testnet in late 2025' when it was in fact recommended for full mainnet deployment in October 2025; and (3) Rotor is characterized as 'replacing' Turbine when Anza's own documentation frames it as a refinement with Turbine remaining in the initial deployment. No claims were found to be actively disputed by credible counter-sources. The 86% Agave-derived stake figure is slightly stale for the 'late 2025' timeframe given rapid Frankendancer growth.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}