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 · StakeDAO
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443519555
- Off-chain at
- 2026-08-26T07:06:20.967Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BedkNxUKBykJnTLoudLuwVCeKbazTAdrtUgwhnRgXEYP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1260 chars)
{"actor":"reviewer","decided_at":"2026-08-26T07:06:20.831Z","decision":"review","investigation_id":"e045ecc6-65b7-40c1-9c52-77ca12ab20a3","new_score":38,"page_slug":"stakedao","prev_score":38,"reason":"The page's core exploit mechanics (deployer-key compromise, LayerZero setPeer reconfiguration, ~5.44T vsdCRV mint, ~$91K extracted) are well corroborated by independent tier-1/tier-2 reporting, and it correctly limits Curve Finance's role to a swap venue and coordinating warning party without overstating its culpability, consistent with the separately-reviewed incident page. However, the page is materially stale: it treats the absence of a post-mortem and an unresolved compensation timeline as current facts, when StakeDAO in fact published a post-mortem (with a root cause — incomplete ownership handover — different from the 'hot key' theory the page speculates about) and executed a compensation plan for 242 addresses by July 9, 2026, roughly seven weeks before this review. The page also omits current TVL and operating-status data entirely and does not reference the dedicated incident investigation page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}