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 · 0G Labs
- Sequence
- #3
- Score
- 48 → 43 (-5)
- Cluster
- mainnet-beta
- Slot
- 423951932
- Off-chain at
- 2026-06-03T04:12:43.589Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ae9emedccJMBu2RSFXy4eiZVwDenwuNjHwCJqqaCN2D6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1691 chars)
{"actor":"judge","decided_at":"2026-06-03T04:12:43.359Z","decision":"review_approve","investigation_id":"3130c295-97eb-43a7-a9c6-1ebf56a86276","new_score":43,"page_slug":"0g-labs","prev_score":48,"reason":"The review returned zero disputed claims across 17 checked (0.0% disputed rate), placing this page squarely in the approve band. All core allegations — the $325M funding total, the December 2025 smart contract exploit ($516K, exact token breakdown), CVE-2025-66478 exploitation, the October 2025 X account compromise, and the Conflux soft-rug community backlash — are independently confirmed by multiple sources including Tier 1 outlets. The four partially-supported findings are minor: two timeline date errors (claim_findings[6] dates the $290M announcement to 2024-12-01 when sources confirm November 13, 2024; claim_findings[8] dates the Ecosystem Growth Program to 2025-02-01 when the announcement was February 5, 2025), one clear placeholder date error on the post-mortem entry (claim_findings[14] lists 2025-12-01 for an event that could not have occurred before the December 11 exploit), and a mild characterization overstep on insider token allocations (claim_findings[16] — the page says 'undisclosed' but the more accurate framing is 'inadequately disclosed until community pressure prompted clarification'). A small score modifier of -5 reflects these correctable inaccuracies. One high-priority coverage gap exists (on-chain vesting analysis), which is appropriate for editorial expansion but does not affect the approve verdict.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}