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 · Dango
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425433443
- Off-chain at
- 2026-06-10T00:07:42.685Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BjrVkwJrWKqPfgT5XNA98ejLH7unNYrjTfe7z9Bu2L4z
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1050 chars)
{"actor":"reviewer","decided_at":"2026-06-10T00:07:42.617Z","decision":"review","investigation_id":"79a41b54-63cf-4342-8c1b-516bf780f51d","new_score":52,"page_slug":"dango","prev_score":52,"reason":"The Dango investigation page's core factual claims — the $3.6M seed round, the April 13 2026 exploit mechanics ($1.9M USDC via insurance fund sign error), the $410,010 bridged to Ethereum, chain pause with SEAL-911 engagement, and white hat fund return — are all confirmed by multiple independent sources. Three claims are only partially supported: the specific investor entity name (Delphi Labs vs. Delphi Ventures, minor), the January 2025 testnet 2.0 campaign start date (evidence suggests a later launch), and the specific April 15 resume date post-exploit. The most significant structural issue is that all six section content fields are empty, leaving 12 cited URLs unanchored to any visible claim text.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}