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 · Ionic Protocol
View on Solana ↗
Sequence
#3
Score
53 → 53 (0)
Cluster
mainnet-beta
Slot
462188601
Off-chain at
2026-10-27T19:26:47.577Z
Anchored at
2026-10-27T19:26:56.000Z
Block time
2026-10-27T19:26:56.000Z

Independent verification

1. Database (off-chain)
8mjeu1dRhwiFQSMdBFZzM4qECAU7H8s2wH2WAEtRrVi5
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1365 chars)
{"actor":"reviewer","artifact_identity":"b669700f5a1ec0fa3089305f7b1ea373","blocked_count":1,"decided_at":"2026-10-27T19:26:47.434Z","decision":"review","disputed_pct":0,"findings_hash":"GK6VyFo5ejT4YV5WnuSbrd7MkP69cA2g3MYpL14AG9wz","investigation_id":"43255326-3258-4cc6-b6b3-c293918c5c60","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"omissions":{"material":1,"total":1},"page_content_hash":"aa1161c5964d5ec02b14f083bc980e536c430bd0fa44fc88491794f18e30fbde","page_slug":"ionic-protocol","prev_score":53,"reason":"The core narrative holds: the fake-LBTC social-engineering exploit, the $6.9M and $8.6M loss figures, the 250 tokens, the 0.01 ETH starting balance and the Tornado Cash laundering match Halborn and Rekt. Two weaker points: the 1,204 ETH / $3.2M figure is attributed to Halborn, which says about $3.5M, and the final section's status statement is stale given DefiLlama's deprecated label. Only a small sample of claims was verified, and several sources were blocked or not fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}