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_approve · Anza
View on Solana ↗
Sequence
#3
Score
74 → 69 (-5)
Cluster
mainnet-beta
Slot
423507971
Off-chain at
2026-06-01T03:12:27.997Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
J1ji2uE7X6f7tnrpaSwUKY4FeKDyuvRUpCenR81nzYyd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1363 chars)
{"actor":"judge","decided_at":"2026-06-01T03:12:27.767Z","decision":"review_approve","investigation_id":"83fa375e-fe5d-4d90-8113-e50091f2a566","new_score":69,"page_slug":"anza","prev_score":74,"reason":"The reviewer confirmed 20 of 30 claims outright and found zero actively disputed claims, yielding a 0% disputed rate. A -5 modifier is applied to reflect a cluster of partially_supported findings that represent material imprecisions: claim_findings[29] (Funding section) incorrectly states Anza has not disclosed its funding source when CEO Jeff Washington publicly confirmed a Solana Foundation grant at launch; claim_findings[12] characterizes Agave 3.0 as 'released to testnet in late 2025' when official release schedule data shows it was recommended for full mainnet deployment in October 2025; and claim_findings[18] overstates Rotor as 'replacing' Turbine when Anza's own documentation frames it as a refinement with Turbine remaining in the initial deployment phases. These inaccuracies are correctible and do not rise to the level of disputed claims warranting a revise verdict, but they reduce overall accuracy confidence. Reviewer confidence was 0.88 and no link rot or stale critical citations were found.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}