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 · Strike
- Sequence
- #4
- Score
- 34 → 34 (0)
- Cluster
- mainnet-beta
- Slot
- 457621253
- Off-chain at
- 2026-10-16T11:29:23.066Z
- Anchored at
- 2026-10-16T11:29:49.096Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HZE3u4wYRmj1qH7qZBKSkz9Gvv9tiNvHjZoasCq4ZXBb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1899 chars)
{"actor":"reviewer","artifact_identity":"38c68166e9da1d14159796db84423772","decided_at":"2026-10-16T11:29:22.904Z","decision":"review","disputed_pct":0.1111,"findings_hash":"GsebMf1jV64Sw1cSTnsRu6mQdzwUEhh5btPFWp6ZpqYg","investigation_id":"2475fba5-c3ac-4164-9093-6998e57de151","mode":"findings_only","new_score":34,"page_content_hash":"7ce6bed783185831d014113aeea8e9e46e90a8a0b311cf64eea60f523d48707b","page_slug":"strike","prev_score":34,"reason":"Most atomic claims on this page are well supported by the cited reporting: the 2023 breach-and-denial sequence, the USDT/'cash' balance practice for non-US users, the March 2026 NYDFS licensing, and the JPMorgan account closure and disclosure dates all check out against independent sources, with dates matching precisely in the JPMorgan case. The most important problem is staleness in the Twenty One Capital merger section and summary: both describe Jack Mallers as currently serving as CEO of both Strike and XXI amid an active, unresolved conflict, but the proposed three-way merger was publicly called off in July 2026 and Mallers resigned as XXI's CEO at that time — a fact the page does not reflect anywhere, including its timeline. Secondary issues include an unsupported attribution of the $2.1B credit facility specifically to Tether (the page's own cited source does not make that attribution), an overstated 'analysts noted' framing around a JPMCoin competitive-motive theory not found in any of the section's cited sources, a dead/content-drifted citation for the Strike FAQ (though the underlying USDT claim is independently supported elsewhere in the same section), and an unverifiable claim about a 'Zap Solutions Holdings, Inc.' parent entity with no supporting source anywhere on the page.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}