Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#4
Score
18 → 18 (0)
Cluster
mainnet-beta
Slot
457727670
Off-chain at
2026-10-16T17:53:27.199Z
Anchored at
2026-10-16T17:53:36.328Z
Block time
—

Independent verification

1. Database (off-chain)
YV1FN1TM7m3Eu5xzmWpucDfGQHPt1pvGd6GireAdDjz
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2105 chars)
{"actor":"reviewer","artifact_identity":"bddc4645afeaf13760bbe2b3fa05f8fb","decided_at":"2026-10-16T17:53:26.879Z","decision":"review","disputed_pct":0.2917,"findings_hash":"3yhF7HQvJx9a9vJAU2C35B9wCMKqEBvLH6AwB4idgfgF","investigation_id":"4feace03-6746-48e9-a625-9cd1ac6e6351","mode":"findings_only","new_score":18,"page_content_hash":"1d44daa70517f2a4a082fc81be21979331ed1b7781b2d11d98285aaa06e274a2","page_slug":"summer-finance-summer-fi-lazy-summer-protocol-flash-loan-exploit-and-shutdown","prev_score":18,"reason":"The large majority of this page's factual claims are well supported by multiple independent tier-1 and tier-2 sources (Rekt.news, The Block, CoinDesk, Verichains, The Defiant, Bitget, Bitcoin.com News) that I fetched directly, including precise figures for the flash loan amount, share-price inflation, per-vault losses, TVL, and SUMR price decline. One finding is disputed: the claim that Verichains' post-mortem analysis found 'all wallets were funded via the same origination path' is not supported by the Verichains post itself, which explicitly disclaims analyzing wallet funding; that finding instead appears to belong to Cyvers per independent reporting. A handful of granular details — the exact April 6, 2026 wallet-funding date, the 'Guardian multisig — an 8-of-6 multisig' configuration (which is a mathematical impossibility as worded), minute-level incident-response timestamps, the exact shutdown-announcement quote, and the specific SIP proposal numbers — could not be independently verified, chiefly because the cited official Summer.fi blog posts returned HTTP 503 on every direct fetch attempt and the Wayback Machine mirrors were unreachable from this environment. These should be treated as open items rather than confirmed errors. Coverage gaps include the absence of independent on-chain fund-tracing past July 9, 2026, no discussion of pre-incident audit history, and no mention of regulatory/law-enforcement follow-up.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}