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 · DeFi Governance Attack Wave 2026
- Sequence
- #2
- Score
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 443523316
- Off-chain at
- 2026-08-27T03:34:57.989Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ad25RpqzNqBzEDkHE2yUvWdGqW27Bu4iNNMBFFgZwgqM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1208 chars)
{"actor":"reviewer","decided_at":"2026-08-27T03:34:57.908Z","decision":"review","investigation_id":"6b0b5653-4ab1-4c49-8ab8-cc603345bb23","new_score":10,"page_slug":"defi-governance-attack-wave-2026","prev_score":10,"reason":"All six named constituent incidents (BonkDAO, Term Finance, Token of Power, BarnBridge SMART Yield, Panther Protocol, Unicly) are independently corroborated by multiple credible outlets and are genuinely governance-mechanism attacks (malicious proposals, vote/quorum manipulation, or oracle-gated execution) rather than misclassified code bugs or key compromises. The page's overarching 'connected wave' framing and its $22M-$30M range, however, rest on a single vendor blog post (Blockaid) for their coherence, blend two different measurement scopes (a June 9-Aug 6 Blockaid tally that excludes Term Finance, versus a fuller list that includes it) without flagging the discrepancy, and go beyond how independent reporting characterizes governance attacks, which frames them as a rare, minority risk category rather than a coordinated wave.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}