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 · Neutrl
- Sequence
- #2
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 443525724
- Off-chain at
- 2026-08-27T11:06:12.185Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- ARmcQc3ddKtDfFeX2Z6xTLyuU3izJeJqzenMfNMnsUuL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1369 chars)
{"actor":"reviewer","decided_at":"2026-08-27T11:06:11.567Z","decision":"review","investigation_id":"929433df-9a9d-4af5-9512-099ea30a94c9","new_score":45,"page_slug":"neutrl","prev_score":45,"reason":"The page's summary and timeline are largely accurate against independent outside sources — the seed round, launch metrics, and March 2026 DNS-hijack narrative all check out in substance — but sources_used is empty and all 7 sections have empty content, so 'confirmed' here means verified against the open web, not against any evidence the page itself supplies; the section scaffolding (headings and source lists for funding, launch, hijack, campaign, resolution, counterparty risk, and partnerships) implies analytical coverage the page does not actually deliver. Two dated claims are disputed: the USDX comparison event is dated Nov 1, 2025 versus independently reported Nov 3-7, 2025, and the LayerZero OFT integration is dated May 1, 2026 versus a LayerZero announcement whose timestamp decodes to roughly Nov 2025 — both align with the first-of-month placeholder pattern. The TVL figure of $136M is a real, traceable figure but stated without an as-of date against a metric that has since ranged from roughly $89M to $217M.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}