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
55 → 55 (0)
Cluster
mainnet-beta
Slot
464447071
Off-chain at
2026-11-02T09:35:46.180Z
Anchored at
2026-11-02T09:36:00.000Z
Block time
2026-11-02T09:36:00.000Z

Independent verification

1. Database (off-chain)
CfSPrayuVWvfd7QfUPgd4yNNYxWqsJWJjFBF2aWmAM4K
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1250 chars)
{"actor":"reviewer","artifact_identity":"3adb14428f4c50941090a50551fc5724","blocked_count":1,"decided_at":"2026-11-02T09:35:46.113Z","decision":"review","disputed_pct":0.3333,"findings_hash":"G5p5HvTtuFdrAXWtRJfTLayw2cV4TgYTzFdxf9G3MyQK","investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_content_hash":"892e791bcf3b210e7035e396875b290622ab08bb515ccd04f3970a510e3d7e20","page_slug":"unleash-protocol","prev_score":55,"reason":"The core incident (about $3.9M, multisig takeover, unauthorized upgrade, 1,337 ETH to Tornado Cash, operations paused, no recovery plan) is well corroborated. The 34-transaction and 11-12 hour detail was not found in the sources I read. The launch date and team page are unverifiable, and the cited team docs URL now 404s. Several sources were not fetched, such as DefiLlama and the TVL figures.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}