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
#3
Score
22 → 14 (-8)
Cluster
mainnet-beta
Slot
462186565
Off-chain at
2026-10-27T19:19:33.782Z
Anchored at
2026-10-27T19:19:41.000Z
Block time
2026-10-27T19:19:41.000Z

Independent verification

1. Database (off-chain)
67nyhWYAVjALpZC87MAor5pjRgPKPTqamDKAsxV3i3ZK
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1580 chars)
{"actor":"judge","artifact_identity":"af5b78b7b91d37d012d0e98667886ae2","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:19:33.484Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"d5038ea6-f6da-4298-a96e-65d8691cf8e0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":14,"page_slug":"splash-optim-finance-oada-cardano-stableswap-exploit","prev_score":22,"reason":"The core incident facts (amounts drained, net loss, pool remainder, the three missing validator checks, Optim's Sept 13 and Sept 15 statements) were confirmed against CryptoSlate (claim_findings[0], [5], [6]). Of 8 countable findings, 2 could not be verified (claim_findings[1] TVL drop, claim_findings[7] no disclosed attacker addresses), giving 25% disputed; one further finding was excluded because the source blocked the reviewer. Three claims were only partly supported: the Sept 15 patch date is inferred (claim_findings[3]), the Minswap snapshot was taken hours after the attack (claim_findings[4]), and the Catalyst Fund 11 funding has no cited source (claim_findings[8]). The page also rests on secondary news with high-priority gaps in primary sources and on-chain data, so a small penalty applies; no omission or status change contradicts the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}