Skip to main content
AVOID.NET
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 · Rug Republic — Coordinated Pump.fun / Solana Bundle-Rug Cluster
View on Solana ↗
Sequence
#3
Score
2 → 0 (-12)
Cluster
mainnet-beta
Slot
443505076
Off-chain at
2026-08-08T00:55:57.915Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GniGL7zDKk4rhZCtK6KtQqGwP8h5K5qKzNGbdCXFce1m
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1811 chars)
{"actor":"judge","decided_at":"2026-08-08T00:55:57.553Z","decision":"review_revise","investigation_id":"9da57c16-5080-4c4a-967b-1bb96e7ee468","new_score":0,"page_slug":"rug-republic-coordinated-pump-fun-solana-bundle-rug-cluster","prev_score":2,"reason":"The reviewer found a disputed_pct of 19.2% across 26 evaluated claims, placing this page in the revise band. The well-sourced components — Solidus Labs platform-wide fraud statistics, Pine Analytics sniper data, and Aguilar v. Baton RICO litigation details — are confirmed by Tier 1 and Tier 2 sources. However, three accuracy problems drive the penalty: claim_findings[3] conflates two separate wallets from the underlying source to assert a single entity holding 29,834 token deployments and $3.8M in profits, which is a factual mischaracterization; claim_findings[18–19] misdate the South Korean CATFI prosecution as 'mid-2025' in the section body and '2026-02-01' in the timeline when the actual arrests and charges occurred in May 2026, an error of roughly one year and 3.5 months respectively; and claim_findings[4] (unverifiable) references a 'Deployer_X7' sub-cluster label that does not appear in any cited source, while the cited article uses 'Deployer_3X' with no matching figures. Additionally, claim_findings[22] identifies the primary Arkham on-chain evidence URL as returning 403 Forbidden, removing independent access to the most specific cluster evidence. The page's own 'Source Confidence Limitations' section (claim_findings[25], confirmed) partially offsets these issues by acknowledging that core Rug Republic statistics rest on community Medium articles without a formal Arkham publication.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}