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
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443517212
- Off-chain at
- 2026-08-25T22:11:12.671Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HJkMFoYJW4hcVcBJfnhRNeRLRndwrs3eusj5JA81Vb9S
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1142 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:11:12.520Z","decision":"review","investigation_id":"1b36e032-1618-4172-a80f-e475afaaf1a7","new_score":38,"page_slug":"stakedao-vsdcrv-deployer-key-exploit-may-2026","prev_score":38,"reason":"The page's core factual claims — the deployer-key root cause, the setPeer/LayerZero mint mechanism, the $91K realized versus $763B nominal mint disparity, the incident response timeline, and the SDGP-70 compensation figures — are consistently and independently corroborated by multiple outlets and, where available, primary governance documents. The 'deployer key' root cause is explicitly what StakeDAO's post-mortem and independent firms (Blockaid, PeckShield, BlockSec) reported, not an inference by the page. Weaknesses are narrow: an imprecise citation for the industry-wide '$770 million' DeFi-losses figure, an incomplete list of DEXs used by the attacker, and an unconfirmed final vote outcome for the more recent SDGP-75 borrower-compensation proposal.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}