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
26 → 26 (0)
Cluster
mainnet-beta
Slot
468707126
Off-chain at
2026-11-12T23:20:15.654Z
Anchored at
2026-11-12T23:20:36.000Z
Block time
2026-11-12T23:20:36.000Z

Independent verification

1. Database (off-chain)
BHxsKyLsjmsFiK3fEm4zCyd9m3xKoUe7QXxmQHKwbaqp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1391 chars)
{"actor":"reviewer","artifact_identity":"49df0cc0539510fc4921c22754bd169b","blocked_count":1,"decided_at":"2026-11-12T23:20:15.603Z","decision":"review","disputed_pct":0.25,"findings_hash":"Hcv5WQXKKUHJ6VndhF47cRCyDesdcYSbrysTBT2dzrGb","investigation_id":"e5cf3900-a013-4931-bdac-fdaf77d5471b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":26,"omissions":{"material":0,"total":1},"page_content_hash":"58a841f83d7dd4e2e69affcae2c0124af53d1ee9670799b06a05851ff680042f","page_slug":"defrost","prev_score":26,"reason":"The core incident narrative (two-stage Dec 2022 exploit of about $12M, owner-key mechanics, CertiK/PeckShield/DeFiYield rug pull allegations, team denial, fund return) is corroborated by CoinDesk, Halborn and search results, and the page properly labels the allegations as unproven. One internal inconsistency was found: 'Christmas Eve' is attached to Dec 23. Current-status figures and the De.Fi named-individual claims could not be verified in this time-limited pass. No contradicting current status was found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}