Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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_approve · Crypto.com
View on Solana ↗
Sequence
#5
Score
1658 (+42)
Cluster
mainnet-beta
Slot
426514222
Off-chain at
2026-06-14T23:15:44.300Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
3f6MbCav7FW3C2tudJrTSSz9hzDXXaiYaj7pVSjZNpv3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1769 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:44.133Z","decision":"review_approve","investigation_id":"4353b260-3c61-49c0-b2b6-baf8e07bd172","new_score":58,"page_slug":"cryptocom","prev_score":16,"reason":"This is a severity-calibration review: the page content is accurate (0% disputed claims, all six claim_findings confirmed as supported), but the trust score band is demonstrably too harsh. The current score of 16-28/WARNING treats Crypto.com as a near-fraudulent entity. The review establishes that the two primary loss events — the January 2022 hack (claim_findings[0]) and the 2023 Scattered Spider breach (claim_findings[4]) — were suffered by Crypto.com at the hands of third parties, not perpetrated by it, and in both cases no user funds were permanently lost. The SEC investigation (claim_findings[1]) was closed with no enforcement action in March 2025. These three factors collectively account for most of the WARNING-band weight and are miscategorized severity anchors. The remaining genuine concerns are real: the March 2025 CRO token reissuance against 77.97% community opposition via concentrated validator power (claim_findings[3]) is a material governance failure warranting CAUTIONARY designation, and the CEO Ensogo history is a legitimate red flag. A delta of +30 moves the score meaningfully toward the reviewer's recommended 58/CAUTIONARY without fully adopting the top of that band, preserving a residual penalty for the governance failure and non-disclosure of the Scattered Spider breach (claim_findings[4]). The page remains published with no status change; content accuracy is not in question.","score_delta":42,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}