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 · Key Coin Assets Ltd
- Sequence
- #3
- Score
- 2 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 443510619
- Off-chain at
- 2026-08-25T03:00:55.354Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A3KFWqnvrqvXFvZUSgsdvpfz9D5tKhA1rs7NpMm3x5YM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1689 chars)
{"actor":"judge","decided_at":"2026-08-25T03:00:55.007Z","decision":"review_revise","investigation_id":"408f5863-f16b-4698-95f0-9d97a80692e1","new_score":0,"page_slug":"key-coin-assets-ltd","prev_score":2,"reason":"Recomputed disputed_pct is 0% (38 of 39 claims confirmed, 1 partially_supported, 0 disputed), which on its own would support approval. However, the single partially_supported finding is not a minor date or trivia point: it concerns the page's 'Current Status' assertion that Key Coin Assets Ltd is 'in compulsory liquidation' as settled fact (claim_findings[30]). The reviewer directly checked the live Companies House register and a third-party insolvency aggregator and found the company still listed as 'Active' with no winding-up filings recorded, and the aggregator describing the matter as still at petition stage. The underlying event -- a winding-up order granted 11 August 2026 -- is well corroborated by the primary Insolvency Service release and independent press, so this looks like registry-update lag rather than a fabricated or false claim. But the page presents current legal status as settled when public records had not yet caught up, which matters on a page making fraud allegations against a named, real company. Combined with a high-priority coverage gap explicitly calling for this discrepancy to be reconciled or acknowledged (coverage_gaps: 'Current company registry status verification'), this pushes the page into the revise band rather than a clean approval, even though the numeric disputed share is 0%.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}