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 · Pump.fun
View on Solana ↗
Sequence
#2
Score
18 → 10 (-8)
Cluster
mainnet-beta
Slot
419601700
Off-chain at
2026-05-14T03:02:36.360Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
558mJXmq8HZXm8b37GbHTN3tB8UE7shsxBstez9KEJJX
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1201 chars)
{"actor":"judge","decided_at":"2026-05-14T03:02:36.114Z","decision":"review_revise","investigation_id":"fa06b8b3-2ac4-4a63-8675-0ab6f6e2465f","new_score":10,"page_slug":"pump-fun","prev_score":18,"reason":"Core allegations (lawsuit, FCA warning, Solidus Labs 98.6% finding, Lazarus Group laundering, insider exploit) are well-supported by Tier 1 and Tier 2 sources. However, two material tokenomics claims require correction: claim_findings[22] overstates team allocation as 40% when sources confirm 33% (20% team + 13% existing investors), and claim_findings[23] incorrectly asserts no vesting on team tokens when sources confirm a 12-month cliff with 36-month subsequent vesting. Additionally, claim_findings[1] reflects stale business model language (Raydium graduation threshold and routing no longer accurate post-PumpSwap launch March 2025). Several partially supported claims involve minor timeline compressions and characterization nuances. Coverage gaps on on-chain MEV analysis and competitive landscape suggest expansion opportunities, not denial.","score_delta":-8,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}