Skip to main content
Sign in
← 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_revise · M2
View on Solana ↗
Sequence
#3
Score
49 → 39 (-10)
Cluster
mainnet-beta
Slot
423915109
Off-chain at
2026-06-03T00:08:12.975Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
97DHeD91wftVhknu2hrpG6z4nEGQr5yoNm5xYHLXMXoK
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1424 chars)
{"actor":"judge","decided_at":"2026-06-03T00:08:12.840Z","decision":"review_revise","investigation_id":"6a672e14-a70e-4dc9-aa88-79a170525ba6","new_score":39,"page_slug":"m2","prev_score":49,"reason":"The page's core factual record of the October 2024 hack is well-sourced and confirmed: amount, date, networks, response time, and customer reimbursement all hold up across multiple independent outlets (claim_findings[2] through claim_findings[6] all confirmed). However, claim_findings[0] is rated stale by a Tier 1 source — the ADGM public register shows M2's Financial Services Permission was formally withdrawn on August 26, 2025, yet the summary presents M2 as a currently licensed, operating exchange. This is the most material issue: a high-priority coverage gap that misrepresents the entity's current regulatory and operational status. Additionally, claim_findings[1] and claim_findings[7] are partially_supported — the page conflates the July 2023 original FSP grant with the November 2023 retail rollout announcement. The hack narrative itself requires no correction; what requires revision is the summary's active-present framing of M2's regulatory status and the addition of post-hack developments (license withdrawal August 2025, operational wind-down November 2025).","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}