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.
- Sequence
- #2
- Score
- 4 → 4 (0)
- Cluster
- mainnet-beta
- Slot
- 426257413
- Off-chain at
- 2026-06-13T18:55:56.261Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 88mXag7LHkQg1aqxXam2ngALH4zwEGZG2tLxRAGSNCJ7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1153 chars)
{"actor":"reviewer","decided_at":"2026-06-13T18:55:56.155Z","decision":"review","investigation_id":"a6572085-f452-40d1-b238-b9699664fdfe","new_score":4,"page_slug":"solana-token-2022-permanent-delegate-rug-pull-factory","prev_score":4,"reason":"The investigation is well-sourced for its core factual claims: the Token-2022 Permanent Delegate mechanism is accurately described per official documentation, the September 2024 first-disclosure timeline and RED token case are confirmed, and the Solidus Labs and SolRugDetector statistics are accurately cited. The principal weaknesses are a disputed SLERF timeline entry (wrong SOL amount, wrong mechanism description), a one-month date error for the SEC CETU launch, and several unverifiable claims that rest entirely on a 404'd dev.to community post — a vulnerability the page itself acknowledges by labeling those claims 'alleged and low-confidence.' The SolRugDetector arXiv paper's submission date is also misrepresented as January 2026 when it was March 2026.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}