Skip to main content
AVOID.NET
← 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
#3
Score
8 → 0 (-15)
Cluster
mainnet-beta
Slot
443520612
Off-chain at
2026-08-26T11:29:28.807Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
D769M2sbQxkeyv2AFEt4jcRW6JRFkpPkxcdHqExCmHTR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1760 chars)
{"actor":"judge","decided_at":"2026-08-26T11:29:28.608Z","decision":"review_revise","investigation_id":"cb4fa2c8-da5a-4b47-b070-7b61d3112ebd","new_score":0,"page_slug":"pumpdotfun","prev_score":8,"reason":"None of the page's 23 checked claims were rated disputed or unverifiable, so the raw dispute rate is 0%, which on its own would support approval. But the review also flagged three high-priority coverage gaps and three citations that have gone stale, and the spec allows either of those findings to push a page from approval into revision even when the dispute rate is low. The most serious is claim_findings[10]: the page's timeline says exploiter Jarett Dunn was 'released on bail' in May 2024 and stops there, while the page's own listed sources report his later guilty plea, an attempt to withdraw it, a bail-breach jailing, and an eventual six-year prison sentence. That is a materially wrong account of a named, living person's current legal status, built from sources the page already cites. The review also found a UK FCA warning notice described as a regulatory 'ban' (claim_findings[4]), a Solidus Labs liquidity-collapse proxy presented as a proven finding of 'rug pulls or fraud' (claim_findings[7], [19]), stale revenue figures roughly 35% below current reporting (claim_findings[2]), and a court-order date off by two days from the page's own cited source (claim_findings[22]). No single item meets the bar for denial, but together they show a page that has not kept pace with its own sourcing and periodically overstates what its sources support, which warrants revision rather than a clean pass.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}