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
2 → 0 (-12)
Cluster
mainnet-beta
Slot
443523420
Off-chain at
2026-08-27T03:48:41.465Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
5JQjJgUCRkWfLa9sXw4d9c92aYUmCaf5ZiviFj3Hi31B
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1882 chars)
{"actor":"judge","decided_at":"2026-08-27T03:48:41.285Z","decision":"review_revise","investigation_id":"1620215f-f081-449c-b8c1-deed771b06ff","new_score":0,"page_slug":"mica-transition-impersonation-scam-wave-2026","prev_score":2,"reason":"The review found 3 of 25 factual claims (12%) disputed, placing this page in the minor-issues range rather than a serious-issues or denial range. The page's central premise -- a genuine wave of impersonation scams tied to the MiCA transition -- held up: it is grounded in on-the-record statements from ESMA, AMF and AFM to the Financial Times, not a single unverified source (claim_findings[0], claim_findings[1]). However, the review identified a claim that named exchanges Coinbase, Kraken and OKX were 'reportedly impersonated' with no source, including the page's own citations, actually saying so (claim_findings[13]) -- a more serious defect than a routine factual slip because it attributes a specific circumstance to identifiable businesses without evidence. It also found a Binance user-count figure that contradicts Binance's own contemporaneous disclosure by over 100 million users, apparently confusing a market-size estimate with an actual user count (claim_findings[14]), and a timeline entry that attributes a statistic to a source article that does not contain it (claim_findings[24]). A regulator, Belgium's FSMA, is placed under an 'entities impersonated' heading even though the source cited for it describes an unrelated enforcement action (claim_findings[12]). These are sourcing and attribution problems that require correction, not evidence the page's core reporting is wrong, so a revision request is warranted rather than escalation to under-investigation status or denial.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}