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 · Tia
- Sequence
- #4
- Score
- 42 → 30 (-12)
- Cluster
- mainnet-beta
- Slot
- 443526097
- Off-chain at
- 2026-08-27T13:10:49.056Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BVeYjUr43F44dqcbxBHKKYJT2yBZ2whuyMC13KxguVv5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2118 chars)
{"actor":"judge","decided_at":"2026-08-27T13:10:48.697Z","decision":"review_revise","investigation_id":"4a9ed1f3-fadc-4508-b6d8-8d34901e8588","new_score":30,"page_slug":"tia","prev_score":42,"reason":"Disputed_pct works out to 5 of 27 claims (3 disputed + 2 unverifiable) = 18.5%, which sits inside the 10-30% band, so this is a revise, not a deny or a clean approve. The weight comes from two disputed items with real financial consequences: claim_findings[15] shows the page's Series A&B/Seed/core-contributor allocation percentages match neither its own cited CryptoRank source nor Celestia's official docs, instead aligning with an uncited aggregator that dilutes the numbers against a different supply base -- a coherent but unexplained denominator swap, reinforced by a matching high-priority coverage gap on the same point. claim_findings[3] states TIA has a fixed one-billion max supply when the token has already inflated past that figure, confusing genesis supply with a cap. A smaller but concrete error, claim_findings[5]'s '500 hours' community service figure, is directly contradicted by the page's own cited Wikipedia source (320 hours). The two unverifiable findings (claim_findings[7], [18]) and two stale price figures (claim_findings[2], [14]) are lower-weight by design -- the unverifiable ones stem from source rate-limiting/access blocks rather than contradiction, and the stale ones reflect data drift, not error at time of publication -- so they push the delta toward the higher end of the minor-issues range without justifying a band change. Per the band table, under_investigation and delisting are gated to 30%+ disputed_pct; at 18.5% neither applies, and the high-priority coverage gaps (on-chain forensic verification, denominator clarity) argue for expansion rather than a harsher verdict since the page's core narrative facts (launch, ATH, sybil-airdrop stats, Polychain buyout, Lotus upgrade, regulatory posture) were independently confirmed.","score_delta":-12,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}