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.

Decision
review_revise · Ionic Protocol
View on Solana ↗
Sequence
#4
Score
53 → 53 (0)
Cluster
mainnet-beta
Slot
462188751
Off-chain at
2026-10-27T19:26:47.732Z
Anchored at
2026-10-27T19:27:28.000Z
Block time
2026-10-27T19:27:28.000Z

Independent verification

1. Database (off-chain)
5c6shS9XVEHWmLNiyucuvwzb9WsQF3WNfxckXkygb9U5
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2040 chars)
{"actor":"judge","artifact_identity":"b669700f5a1ec0fa3089305f7b1ea373","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:26:47.434Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"43255326-3258-4cc6-b6b3-c293918c5c60","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"ionic-protocol","prev_score":53,"reason":"The core account holds up: the fake-LBTC social-engineering exploit, the $6.9M and $8.6M loss figures and the Tornado Cash laundering match Halborn and Rekt News (claim_findings[0], [1]). Two points need correction. The 1,204 ETH / $3.2M bridged figure is attributed to Halborn, which says about $3.5M (claim_findings[2]). The closing section's statement that maintenance status is unclear is out of date, since DefiLlama lists the protocol as deprecated (claim_findings[4], omission_findings[0]). Because the deprecated-status source is secondary and could not be fetched directly, the adjustment is small. One market-data claim could not be checked because the source blocked the reviewer, which is a coverage limit and not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"By claim count no finding is disputed (0 of 5 counted findings; one source_blocked market-data finding excluded), which implies approve. omission_findings[0] is rated material: DefiLlama lists the protocol as deprecated with data ending June 2025, while the page says only that maintenance status is unclear (claim_findings[4], stale). The reviewer's status source is a search snippet and Ionic announced a Metal L2 deployment in June 2025, so the penalty is held at the bottom of the minor band and no status change is applied."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}