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 · KAITO
- Sequence
- #3
- Score
- 42 → 30 (-12)
- Cluster
- mainnet-beta
- Slot
- 443525910
- Off-chain at
- 2026-08-27T12:05:42.370Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CaCyM1nW6MM5ccWGsDiETxnGW3cPpDrSXWUoqF2HgUvY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1880 chars)
{"actor":"judge","decided_at":"2026-08-27T12:05:42.043Z","decision":"review_revise","investigation_id":"44a5d100-c0ea-4ae1-8203-a34a434b2e24","new_score":30,"page_slug":"kaito","prev_score":42,"reason":"Independent fact-checking confirmed the majority of the page's claims, including the core allegations: the March 2025 X account hack and manufactured short-selling scheme, ZachXBT's bot-spam scrutiny, the January 2026 X API ban and Yaps sunset, the 157,000-account ban figure, and the phishing scam write-ups (claim_findings covering sections 1, 2, 4, and 5). However, disputed claims equal 17.1% of all claims checked, placing the page in the minor-issues band. The most notable problems are self-inflicted: the page's stated peak FDV of 'near $2 billion' contradicts its own reported $2.88 all-time-high price times its own stated 1-billion token supply, which implies roughly $2.88 billion (claim_findings[26]); the timeline misdates the token's all-time high to launch day rather than the actual date a week later (claim_findings[32]); and the timeline dates a ZachXBT bounty announcement to January 2025 when the page's own cited source dates it to December 2025, an 11-month error (claim_findings[33]). A high-priority coverage gap notes that the page's top-level source list is empty even though each section's sources are populated and usable, meaning citations exist but aren't surfaced coherently at the page level (coverage_gaps[0]). None of the disputed items involve a fabricated or unsupported core allegation, and reviewer confidence (0.72) is moderate rather than high, so the page is held in the lower end of the revise band without triggering the 30% threshold that would warrant an investigation flag or delisting.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}