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
#5
Score
27 → 27 (0)
Cluster
mainnet-beta
Slot
457874419
Off-chain at
2026-10-17T02:42:44.903Z
Anchored at
2026-10-17T02:42:47.167Z
Block time
—

Independent verification

1. Database (off-chain)
3oJDfrPvWQJ47Y4UuNj8jSeV9krMzJqUcR3Z5zA58YfJ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1763 chars)
{"actor":"reviewer","artifact_identity":"134e459b7281667a3bf7353ff6acddeb","decided_at":"2026-10-17T02:42:44.681Z","decision":"review","disputed_pct":0.0769,"findings_hash":"DyD8rMp5pe4rr6pTHF8Vsvfbe4s5AVHyrYStgSbViQYS","investigation_id":"7e8253f1-08c8-469e-8644-ab5dfced3c12","mode":"findings_only","new_score":27,"page_content_hash":"97f1ab8f40a62b02b6c5292f4d3737f9bbce273cb69a5fe5c290bf564fa648ed","page_slug":"summer-finance-summer-fi","prev_score":27,"reason":"The page's core factual claims -- the July 6, 2026 exploit mechanics, loss amounts, flash loan size, BA Labs response timeline, premeditation window, Tornado Cash laundering pattern, and July 15 wind-down -- are strongly corroborated by the official post-mortem/forum retrospective (where accessible) and by independent outlets including rekt.news, The Block, and PublicAML, in several cases matching the page's own granular figures (e.g., the 9.5% NAV inflation) almost exactly. The two issues found are minor: a dead timeline source_url caused by a one-character typo ('tornado-crash' vs 'tornado-cash'), and a shutdown-rationale sentence that omits a detail present in the page's own cited source (that company capital was held in the affected vaults). A nuance in the summary also blends the gross depositor loss figure with the attacker's net-gain figure. No claims were found to be fabricated, contradicted by credible sources, or significantly stale. Coverage gaps exist around on-chain verifiability, pre-exploit security history, and regulatory/legal follow-up, none of which is unusual for a page built mainly from post-incident news coverage.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}