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 · Sonne Finance
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 459487905
- Off-chain at
- 2026-10-21T04:00:05.447Z
- Anchored at
- 2026-10-21T04:00:10.179Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8CBGxUn8RFFHtLva2x7Ngv3uh3vcFCWTiP1zbYRZBFkc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1816 chars)
{"actor":"reviewer","artifact_identity":"d86d609df51be66342362f267bd178dd","decided_at":"2026-10-21T04:00:05.231Z","decision":"review","disputed_pct":0.3333,"findings_hash":"HTH4G8vnWiWZitwkKoEj8ckJ2xqcJJ8QE3sLZdSpxiTC","investigation_id":"46071ba8-e931-4806-addc-c35517a188ae","mode":"findings_only","new_score":52,"page_content_hash":"4f34e653fa543fa2da3063ca5f105a7f462acce16bc269a81268d7d895327c59","page_slug":"sonne-finance","prev_score":52,"reason":"The core narrative — a Compound V2 donation/precision-loss attack draining ~$20M from Sonne Finance on May 14, 2024, enabled by a non-atomic multisig deployment with a two-day timelock around the VELO market launch — is well supported and was independently confirmed down to the on-chain transaction timestamp. Technical mechanism details (flash-loan amount, 1-wei truncation, tx hash) check out against security-firm writeups. However, the Recovery section contains two serious defects: a quoted team statement that does not appear in the cited source or anywhere else found, and a claimed 'Nefture Security tracing analysis' of a negotiated $7.2M bounty settlement that traces back to a Medium newsletter-signup banner misread as a source — the actual cited article states a recovery looked unlikely. The 60%/$4.25M market-cap figure is also internally inconsistent with the page's own cited CoinDesk source (which gives ~$20M). One attacker address's dollar balance is overstated relative to the cited CertiK breakdown. Founder pseudonym and multisig threshold claims rest on very thin or no sourcing. The page is otherwise a solid, appropriately hedged writeup; the Recovery section specifically needs correction.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}