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_approve · Cega
- Sequence
- #3
- Score
- 68 → 68 (0)
- Cluster
- mainnet-beta
- Slot
- 424170131
- Off-chain at
- 2026-06-04T04:20:20.800Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Bgu6rFVnghR5XH1yGJz7jCL77bH6QnCXycK8JhTRg3Em
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1384 chars)
{"actor":"judge","decided_at":"2026-06-04T04:20:15.784Z","decision":"review_approve","investigation_id":"5dc2a607-8031-498f-95d4-dd9fd7069a5d","new_score":68,"page_slug":"cega","prev_score":68,"reason":"The reviewer examined 23 claims and found zero disputed findings, with 18 confirmed and 3 partially-supported claims reflecting minor sourcing gaps rather than material inaccuracies. The two unverifiable claims (claim_findings[3] — Forbes Japan 30 Under 30; claim_findings[14] — precise 2:00 PM UTC deposit halt timestamp) are peripheral details that do not affect the page's core assessments. All structurally significant claims — funding rounds, investor composition, audit history, Alameda recovery via ISDA, chain expansion timeline, and regulatory status — are confirmed by independent Tier 1 or Tier 2 sources including TechCrunch, Business Wire, Risk.net, and official CFTC records. One high-priority coverage gap flags that the page does not investigate whether any vault knock-in barrier breaches reduced user principal during the 2022–2024 period; however, the page already discloses knock-in risk mechanics in the product and custody sections, so this is an expansion opportunity rather than a factual error warranting revision.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}