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
- 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. - 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.
- 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 · Raydium Protocol
- Sequence
- #3
- Score
- 62 → 55 (-7)
- Cluster
- mainnet-beta
- Slot
- 424169115
- Off-chain at
- 2026-06-04T04:13:48.052Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CmtuAAJJ1uZQ2rAgUvfZnKFsY9uSpsqiA7rzQBGJLGET
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1433 chars)
{"actor":"judge","decided_at":"2026-06-04T04:13:47.885Z","decision":"review_revise","investigation_id":"ef74b3d0-4fed-4f79-a9d6-19255b26afae","new_score":55,"page_slug":"raydium","prev_score":62,"reason":"The reviewer assessed 31 claims with 24 confirmed and 5 partially supported, yielding a 16.1% disputed rate that falls in the minor-issues band. All critical claims covering the December 2022 exploit mechanism, compensation plan structure, and remediation timeline are confirmed by primary sources. The partially-supported findings are limited to peripheral characterizations: claim_findings[27] overstates Pump.fun's 2024 revenue share as 'nearly half' when the full-year figure was approximately 36%; claim_findings[30] includes the UK among restricted jurisdictions without confirmation for the main protocol interface; claim_findings[3] and [10] reflect stale live-price data and an unverified TVL drop percentage. Two cited official documentation URLs are confirmed dead (docs.raydium.io claim portal and security pages), though their substance is corroborated by other live sources. No findings were outright disputed. Revisions should correct the Pump.fun revenue attribution, remove or qualify the UK geo-restriction claim, and replace or annotate the dead documentation links.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}