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_approve · TurtleDex
- Sequence
- #3
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 423509434
- Off-chain at
- 2026-06-01T03:22:03.133Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Nbb4Sk5woMDU4pvTEbFcauWcVjbWwYGLrLX9BSmgrn2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1441 chars)
{"actor":"judge","decided_at":"2026-06-01T03:22:02.932Z","decision":"review_approve","investigation_id":"3a329e32-515f-4fb4-bfdb-95c8537dbdda","new_score":2,"page_slug":"turtledex","prev_score":2,"reason":"The reviewer examined 27 claims and found zero affirmatively disputed by a more credible source, yielding a disputed_pct of 7%, well within the approval threshold. All core TurtleDex allegations — the $2.5M presale raise, the March 19 liquidity drain, the nine-wallet ETH conversion, the JetFuel partnership, the TechRate audit, and the confirmed absence of fund recovery — are supported by multiple Tier 2 sources. The five partially-supported findings are peripheral: claim_findings[16] names the wrong Twitter handle for the on-chain analyst (@DefistalkerAlt vs. @DefiStalker), claim_findings[26] places the comparative Meerkat Finance rug pull one day late (March 5 vs. March 4), claim_findings[21] cites the wrong article for the SlowMist audit claim, and claim_findings[13] may reference an operator wallet rather than the canonical token contract address. None of these affect the substance of the exit scam documentation. One link-rot instance (CoinTelegraph URL) was noted and is minor. No high-priority coverage gaps were identified. Reviewer confidence of 0.82 supports the finding.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}