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 · FQ1tyso61AH1tzodyJfSwmzsD3GToybbRNoZxUBz21p8
- Sequence
- #7
- Score
- 13 → 3 (-10)
- Cluster
- mainnet-beta
- Slot
- 424045789
- Off-chain at
- 2026-06-03T14:35:07.524Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- oF9MFi53rnMSjyCtQsGmsWu9Vs8Cveq3T7DGzms58b7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1427 chars)
{"actor":"judge","decided_at":"2026-06-03T14:35:07.323Z","decision":"review_revise","investigation_id":"c7da8465-6607-45d5-a0b8-37ba48362539","new_score":3,"page_slug":"fq1tyso61ah1tzodyjfswmzsd3gtoybbrnozxubz21p8","prev_score":13,"reason":"The page is broadly accurate on all core claims — token identity, ATH, current price collapse, fair launch mechanics, CertiK score, and team anonymity are all confirmed by Tier 1 sources. No claims carry a 'disputed' verdict. However, claim_findings[13] identifies a material framing error: the page attributes the November 2024 price surge partly to 'support from the ai16z decentralized AI fund,' when ai16z partner Shaw subsequently and explicitly disavowed the Eliza token launched on vvaifu.fun and launched a competing token. This overstated affiliation is the highest-severity accuracy issue and warrants correction. Two citations are also non-functional: the CoinLore price history page (claim_findings[29], 404 error) and the SEC press release cited in the regulatory section (claim_findings[26], 403 error); neither undermines the underlying claims, but dead links weaken the evidentiary record. The claimed April 2026 ATL date (claim_findings[14]) is unverifiable and appears to have since been superseded by a lower June 2026 ATL.","score_delta":-10,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}