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 · Cropper Finance
- Sequence
- #3
- Score
- 42 → 32 (-10)
- Cluster
- mainnet-beta
- Slot
- 425208138
- Off-chain at
- 2026-06-08T23:14:52.302Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CksQYtjNNj43n993HVDvs7xczaVFWKpZZuVJqUtNXPeX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1322 chars)
{"actor":"judge","decided_at":"2026-06-08T23:14:52.029Z","decision":"review_revise","investigation_id":"9c1d242b-0277-4dfc-95fc-73ea129ac828","new_score":32,"page_slug":"cropper-finance","prev_score":42,"reason":"The review confirmed 13 of 24 claims outright and found 5 partially supported, with 3 disputed and 3 unverifiable. The three disputed findings are: the CertiK security rating of 2.7 displayed via CoinMarketCap conflicts with CertiK Skynet's own current score of 63.94/B (claim_findings[7]); the circulating supply figure of ~28 million CRP from CoinMarketCap conflicts with ChainBroker's reported 160 million, which materially affects the unlock-pressure inference (claim_findings[13]); and the Serum defunct event is dated 2022-11-01 in the timeline, whereas Tier 1 sources confirm the actual date was November 29, 2022 (claim_findings[20]). None of the disputed items concern core allegations of fraud or misconduct — they are metric-sourcing discrepancies and a minor date error. Two high-priority coverage gaps (on-chain program upgrade authority and absence of a CLMM audit) remain unaddressed and should be investigated before the page is considered complete.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}