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 · Kraken
- Sequence
- #4
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 457618855
- Off-chain at
- 2026-10-16T11:20:49.217Z
- Anchored at
- 2026-10-16T11:21:10.517Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FeYGfifoeTD9R154qUvEWpsZA9r2wLMNhwyDeefXq5rn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2189 chars)
{"actor":"reviewer","artifact_identity":"1b2a39ab608a29e28391d5ec71946272","decided_at":"2026-10-16T11:20:48.994Z","decision":"review","disputed_pct":0.1667,"findings_hash":"vBR1UVvMwSuCtXZuhqUZacM5TTooUBwEEpTnPP52nJG","investigation_id":"ace45423-b876-4cfd-8e14-4f9b15a6db32","mode":"findings_only","new_score":62,"page_content_hash":"cbc19a9f63cfba65c0720088d4bae6eba5d83312fa39804d2c8526ad38cfd180","page_slug":"kraken","prev_score":62,"reason":"The page's core regulatory and security narrative is substantially accurate and well-supported: the CFTC penalty, OFAC settlement, SEC staking settlement, SEC unregistered-exchange lawsuit, ASIC/Bit Trade case, 2024 zero-day exploit, and the 2026 insider-extortion incident were all independently verified against live regulatory and news sources and match the page's figures and characterizations closely. Two defect groups were found: (1) the SEC staking-settlement citation (used in both a section source and a timeline entry) points to the wrong SEC litigation release -- one that actually documents the unrelated 2025 case dismissal rather than the 2023 staking settlement; and (2) the page states the SEC's dismissal stipulation was filed March 3, 2025, when the actual court filing was March 27, 2025 (March 3 was merely the announcement of an agreement in principle). A third, one-off error was found in the Founder Controversies section, which misdates the New York Times workplace-culture report to September 2022 when it was published in June 2022 (September 2022 was instead when Powell announced his separation as CEO, a distinct event). The substance of the NYT allegations themselves is corroborated. Minor overstatement was found in the Bitnomial deal description, which states a flat $550 million figure where reporting consistently describes it as 'up to $550 million.' No accepted community submissions existed to review. Coverage gaps exist around current multi-jurisdiction licensing status and listed-asset risk, which are common dimensions for exchange profiles on this site.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}