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 · Flying Tulip
- Sequence
- #9
- Score
- 72 → 72 (0)
- Cluster
- mainnet-beta
- Slot
- 471295582
- Off-chain at
- 2026-11-19T10:03:51.177Z
- Anchored at
- 2026-11-19T10:03:57.000Z
- Block time
- 2026-11-19T10:03:57.000Z
Independent verification
- 1. Database (off-chain)
- ANDrYAJ1rmCcoX24Jt68qFC11d1YwwSCizazUraFpYqB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1906 chars)
{"actor":"reviewer","artifact_identity":"88540f2892be32d2b285994d81f9e972","decided_at":"2026-11-19T10:03:51.870Z","decision":"review","disputed_pct":0.0313,"findings_hash":"87SM1tPaoTPvfczNvxRCnJ6VSeXCSFhRbh1Pm86rXKpe","investigation_id":"1d5754e9-8a31-4384-a46f-e2f13b4d653b","judge_def_hash":"23facbd253d9791a0f76ed4171330b75d7080c45235d46c5c7a83b4502acc290","new_score":72,"omissions":{"material":0,"total":3},"page_content_hash":"94ed92372a74a5500b5f83487ce991ed17f77f7abc9132e46176ced60f976058","page_slug":"flying-tulip","prev_score":72,"reason":"The Flying Tulip page is well-sourced and largely accurate. All major factual claims — funding amounts and investor names, TGE date and price, ATL/ATH prices, Sherlock audit outcome, operational metrics, Sonic Labs resignation details, and the Kelp DAO exploit — are confirmed by credible independent sources. One claim (circulating supply of about 483M FT) differs slightly from the current CoinGecko figure (approximately 480M), which is a minor rounding difference. The historical September 21 price/volume metrics cannot be independently verified from live data but are consistent with the token's trajectory. Key omissions are minor: the Kelp DAO Lazarus Group attribution should be noted as preliminary, and the CoinList sale shortfall ($183.9M vs $200M target) is worth including. The most significant coverage gap is the lack of independent on-chain verification of the PUT reserve backing, which is a central marketing claim. The page correctly and carefully distinguishes between the perpetual put redemption mechanism and open-market FT price.","reviewer_def_hash":"0ab16d28840cf555a9c931564bdbc96f6c68d1b1eaf9d89506afaeb2c143b050","score_delta":0,"sequence_num":9,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}