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_revise · DIMO
- Sequence
- #3
- Score
- 52 → 42 (-10)
- Cluster
- mainnet-beta
- Slot
- 425428544
- Off-chain at
- 2026-06-09T23:35:18.548Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Mwj3tuzhdfoZiXR6Mrd7aU5h6RnD6SH4uVvphPWggUn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1329 chars)
{"actor":"judge","decided_at":"2026-06-09T23:35:18.430Z","decision":"review_revise","investigation_id":"f3df7ac8-3072-4759-a393-5cd4f1b75f1d","new_score":42,"page_slug":"dimo","prev_score":52,"reason":"The review confirmed all core claims about the November 2025 security incident, founding team, and tokenomics with Tier 1 and Tier 2 sources. One claim is formally disputed: claim_findings[9] characterizes the Sayfer smart contract audit as producing '14 non-critical vulnerabilities,' but the actual Sayfer report documents 3 HIGH-severity and 1 MEDIUM-severity findings among the 14 total — a material misrepresentation of the project's security history. Three additional claims are partially supported: claim_findings[6] conflates seed and Series A investor rosters (ConsenSys Mesh and Borderless Capital were Series A participants, not seed), claim_findings[7] carries a $1.5M arithmetic gap in the stated total funding figure, and claim_findings[8] cites the lower of several divergent ATH price figures from aggregators. One cited source has link rot (CoinFund founders-corner, 404). The audit severity error in particular requires correction as it understates risk to readers.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}