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_revise · Daos.fun
View on Solana ↗
Sequence
#3
Score
42 → 32 (-10)
Cluster
mainnet-beta
Slot
423652998
Off-chain at
2026-06-01T19:11:52.630Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CqpC5WssuCH87TdVkUcosKr4KmJRvFbBUPphTZDoaGKD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1524 chars)
{"actor":"judge","decided_at":"2026-06-01T19:11:52.489Z","decision":"review_revise","investigation_id":"5d26f0bb-3afb-4dfe-81f0-b359d5ee5c90","new_score":32,"page_slug":"daosfun","prev_score":42,"reason":"The review's computed disputed_pct of 18% (1 outright disputed claim out of 28, with 7 partially supported) places this page in the minor-revision band. The sole disputed finding — claim_findings[26] — is a timeline date error: V3 'Pool Parties' is dated March 2025 on the page but evidence from multiple independent sources places the launch in November 2024, a four-month inaccuracy. Two high-priority coverage gaps push the penalty toward the upper end of the band: the April 2026 federal class action (SDNY, Burwick Law) against ai16z/ElizaOS creators, and the October-November 2025 AI16Z-to-ELIZAOS token migration with dilutive insider allocation — both directly relevant to daos.fun as the platform that hosted ai16z. Additionally, claim_findings[6] flags that @pmairca is an AI persona handle rather than Shaw Walters' operational account, a meaningful attribution error in sections[5] and timeline[1]. Core structural risk claims, custody model mechanics, NAV premium figures, and the AICC incident are well-supported by Tier 1 and Tier 2 sources. Reviewer confidence of 0.72 supports a decisive revision verdict without escalation to denial or investigation status.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}