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
27 → 27 (0)
Cluster
mainnet-beta
Slot
464443675
Off-chain at
2026-11-02T09:23:23.394Z
Anchored at
2026-11-02T09:23:54.000Z
Block time
2026-11-02T09:23:54.000Z

Independent verification

1. Database (off-chain)
H4cAxtVKQJaTeToVBVjykHvNReUSVfo2jwYBVDdyFS2j
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1483 chars)
{"actor":"reviewer","artifact_identity":"e1657028d151478c955c4ed503cca0ef","blocked_count":1,"decided_at":"2026-11-02T09:23:23.338Z","decision":"review","disputed_pct":0.1667,"findings_hash":"HKejGr5HVkr5gW8bBcWGGBDYxVXv8jTTfiKzrQMTYiKP","investigation_id":"f7b59df3-f122-43f3-923d-b37414889049","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"omissions":{"material":2,"total":3},"page_content_hash":"eaf62925b32e359aaf88df05e81df8f39cbea15f355465648c062d54fead950d","page_slug":"mica-transitional-period-expiry-unlicensed-eu-crypto-platforms","prev_score":27,"reason":"The core claims hold up: the July 1, 2026 end date, the Binance Reuters report of June 16, and the AMF and ESMA enforcement posture are consistent with sources and search results. The page is stale. It does not mention that Binance withdrew its Greek application on June 24, 2026, and it treats the deadline as upcoming when it has passed. 'Expire uniformly' overstates national periods. Register counts and the ESMA quotations could not be verified against primary sources. The timeline also lists the 2026-06-16 entry before the 2026-06-14 entry.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}