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
- 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. - 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.
- 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_revise · Access Protocol
- Sequence
- #3
- Score
- 55 → 47 (-8)
- Cluster
- mainnet-beta
- Slot
- 423507990
- Off-chain at
- 2026-06-01T03:12:29.494Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HtkvmDBcsKQy5ghKyxMqPpZSHCzjNXRHPYiD1Fc9mLJ8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1575 chars)
{"actor":"judge","decided_at":"2026-06-01T03:12:29.282Z","decision":"review_revise","investigation_id":"06a710e0-1974-421b-a85e-f8a1f6561728","new_score":47,"page_slug":"access-protocol","prev_score":55,"reason":"The review confirmed all core claims about entity identity, team background, funding, token mechanics, regulatory status, and GitHub repository details. No claim was found to be directly contradicted by a more authoritative source (disputed_pct by strict count: 0%). The revision flag is driven by three correctable data issues: (1) the circulating supply figure of 43 billion ACS is materially stale — both CoinMarketCap and CoinGecko show approximately 49.35 billion as of late May 2026, affecting claim_findings[19], claim_findings[24], and timeline[6]; (2) the 350,000 subscriber and 288 active creator figures (claim_findings[7] and claim_findings[27]) are unverifiable through any Tier 1 or Tier 2 source, with the only contemporaneous third-party figure (220,000 from October 2023) materially lower; and (3) the timeline entry for the July 2024 all-time low (claim_findings[22]) is now stale, superseded by a new all-time low of approximately $0.0001651 recorded March 30, 2026. Three priority-high coverage gaps — on-chain TVL data, audit firm portal verification, and post-2024 publisher activity — support revision rather than approval. Reviewer confidence of 0.82 supports a moderate, non-escalating penalty.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}