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 · Boop (boop.fun)
View on Solana ↗
Sequence
#3
Score
2828 (0)
Cluster
mainnet-beta
Slot
423482124
Off-chain at
2026-06-01T00:21:10.556Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
7pcwFWerk7ub988Gm3MBCWGrkKnBYfNZtwFPxEd2mnra
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1480 chars)
{"actor":"judge","decided_at":"2026-06-01T00:21:10.230Z","decision":"review_approve","investigation_id":"5077e653-5f0c-48aa-b6d3-697cda882dc8","new_score":28,"page_slug":"boop","prev_score":28,"reason":"The reviewer evaluated 33 claims and found zero outright disputed findings, with a computed disputed_pct of 9% — within the approve band. The 6 partially supported claims (claim_findings[1], [6], [7], [21], [23], [34]) involve minor quantitative variances between data sources (ATH price feed discrepancy, a trading-fee destination detail, point-in-time DeFi metrics) rather than material inaccuracies contradicted by a more credible source. The 3 unverifiable claims (claim_findings[8], [27], [31]) concern a future roadmap expansion, an imprecise announcement date in the timeline, and a comparative graduation rate statistic — all peripheral to the page's core risk narrative. All high-severity claims — CZ's credential dispute, the FTX clawback lawsuit naming Dinghua Xiao confirmed by Bloomberg Law (claim_findings[15], [16]), the airdrop early termination (claim_findings[19]), and the ~99% token price collapse (claim_findings[2]) — are confirmed by Tier 1 or Tier 2 sources. Reviewer confidence is 0.82. One high-priority coverage gap on smart contract security audit status is noted and should prompt expansion, not a penalty.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}