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 · Bit.com
- Sequence
- #3
- Score
- 52 → 42 (-10)
- Cluster
- mainnet-beta
- Slot
- 425414167
- Off-chain at
- 2026-06-09T22:00:32.815Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HXY9kgZFEz78DxoP2vLL6zVcJkvb1LpCwXEyGSCsVFCz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1350 chars)
{"actor":"judge","decided_at":"2026-06-09T22:00:32.462Z","decision":"review_revise","investigation_id":"cc3fbcec-6e6a-4760-96d9-3cb179d61864","new_score":42,"page_slug":"bit-com","prev_score":52,"reason":"The core narrative — that Bit.com was a legitimate Matrixport-operated exchange that conducted an orderly phased wind-down in late 2025 through March 2026, followed by Matrixport rebranding as BIT — is well-supported by multiple independent sources and remains credible. However, the review identified a concrete factual error in the disambiguation section: claim_findings[19] found that the entity flagged by the British Columbia Securities Commission is 'bestbitex.com,' not 'bitex.com' as the page states, and no UAE attribution was found at the cited BCSC URL. Additionally, claim_findings[15] found that the cited 51% year-over-year trading volume decline figure does not appear in the sources attributed to it (MEXC News 358004, FX Empire), making this a materially unsupported data point. Two high-priority coverage gaps remain open: post-March-31 user recovery outcomes and community reports on actual wind-down experiences, both of which may now be resolvable given the June 2026 review date.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}