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 · 0G Labs
- Sequence
- #2
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 423951926
- Off-chain at
- 2026-06-03T04:12:43.489Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H7H3eATz1dnYU9TN9c2W4pVYereEjpQ195XLfU3yGLg8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1199 chars)
{"actor":"reviewer","decided_at":"2026-06-03T04:12:43.359Z","decision":"review","investigation_id":"3130c295-97eb-43a7-a9c6-1ebf56a86276","new_score":48,"page_slug":"0g-labs","prev_score":48,"reason":"The 0G Labs investigation page is substantially accurate. The key facts — funding amounts, mainnet launch, X account compromise, smart contract exploit details (amounts, attack vector, CVE reference), and post-mortem security response — are all independently verifiable and confirmed. The primary issues are two incorrect timeline dates (the $290M financing announcement is dated December 1 but occurred November 13, 2024; the ecosystem program is dated February 1 but occurred February 5, 2025) and one post-mortem timeline entry with a date (2025-12-01) that predates the exploit it describes. The page also mildly overstates the insider token allocation issue as 'undisclosed' when the more accurate characterization is 'inadequately disclosed until community pressure prompted clarification'. No claims are flatly disputed by credible counter-evidence.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}