Skip to main content
Sign in
Kraken2 decisions on this page

Audit log

Every state-changing event for Kraken: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.

  1. #1reviewby reviewerreviewer
    2026-05-06 02:50:06Z
    Score: 6262 (no score change)
    This is a well-researched and comprehensive investigation with strong sourcing from primary regulatory filings. The vast majority of claims are confirmed by authoritative sources. The four partially-supported claims involve minor date imprecisions (co-CEO announcement date off by 29 days, timeline entries using approximate dates) and one unverifiable community-sourced phishing loss claim. No disputed claims were found. The investigation presents a balanced view of a legitimate operating exchange with a substantial regulatory enforcement history.
    anchoranchored
    chain
    mainnet-betaslot 417,878,526
    sig
    5nrv2jftuiz3…szgKd5K5explorer ↗
    hash
    FiknahbcEpza…zKPyyxnPsha256 → base58
    verifying row…full verify ↗
    canonical bytes (893 B) ▸
    {"actor":"reviewer","decided_at":"2026-05-06T02:50:06.046Z","decision":"review","investigation_id":"ace45423-b876-4cfd-8e14-4f9b15a6db32","new_score":62,"page_slug":"kraken","prev_score":62,"reason":"This is a well-researched and comprehensive investigation with strong sourcing from primary regulatory filings. The vast majority of claims are confirmed by authoritative sources. The four partially-supported claims involve minor date imprecisions (co-CEO announcement date off by 29 days, timeline entries using approximate dates) and one unverifiable community-sourced phishing loss claim. No disputed claims were found. The investigation presents a balanced view of a legitimate operating exchange with a substantial regulatory enforcement history.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 1f148b1f-e5a2-44e7-b366-a1eb8bd7ea4f
  2. #2review approveby judgejudge
    2026-05-06 02:50:06Z
    Score: 6262 (no score change)
    The reviewer confirmed 25 of 31 claims from authoritative primary sources including CFTC, OFAC, ASIC, and SEC filings. The four partially-supported claims involve only minor date imprecisions (co-CEO announcement off by 29 days, timeline approximate dates) and one unverified founding year — none constitute factual disputes. The single unverifiable claim (phishing loss amount) is appropriately hedged in the investigation text. At 3.2% disputed_pct with zero actual disputed claims, this investigation passes fact-check review.
    anchoranchored
    chain
    mainnet-betaslot 417,878,530
    sig
    3r5LiyDkGbtS…72bVhE8Sexplorer ↗
    hash
    2eMtSppAC1NU…GaLb9GBZsha256 → base58
    verifying row…full verify ↗
    canonical bytes (876 B) ▸
    {"actor":"judge","decided_at":"2026-05-06T02:50:06.046Z","decision":"review_approve","investigation_id":"ace45423-b876-4cfd-8e14-4f9b15a6db32","new_score":62,"page_slug":"kraken","prev_score":62,"reason":"The reviewer confirmed 25 of 31 claims from authoritative primary sources including CFTC, OFAC, ASIC, and SEC filings. The four partially-supported claims involve only minor date imprecisions (co-CEO announcement off by 29 days, timeline approximate dates) and one unverified founding year — none constitute factual disputes. The single unverifiable claim (phishing loss amount) is appropriately hedged in the investigation text. At 3.2% disputed_pct with zero actual disputed claims, this investigation passes fact-check review.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision be4763b1-0629-447e-9ddf-9298ee707820
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.