Who may find this file useful
Security-conscious users who will configure strong account controls and distinguish Kraken Exchange, Kraken Pro and Kraken Wallet before acting.
Operator & custody investigation
Kraken
This investigation reads Kraken’s security, proof-of-reserves, entity and fee claims against the limits stated in its own primary documents.
Editorial assessment: Kraken presents a useful set of account-security controls and a comparatively inspectable proof-of-reserves process. The same evidence requires restraint: a snapshot is not a solvency audit, and EEA services may pass through different entities depending on the activity.
Editorial statusPublished review
Evidence reviewPublic evidence reviewed
Scenario testingScenarios published
ComparisonCategory matrix eligible
Reviewed
Evidence confidencemedium
The decision tension
The platform publishes meaningful control and reserve evidence, but the evidence is scoped, point-in-time and unable to answer every liability or service-quality question.
Documentary, not experiential
Public evidence has been reviewed; account, funding, trading, withdrawal and support scenarios are specified as controlled routes with defined inputs and records.
Evidence-backed strengths
What the record supports
- Documented passkeys, 2FA and Global Settings Lock controls
- Customer-verifiable proof-of-reserves snapshots
- Separate consumer and professional trading disclosures
Material limitations
What must stay qualified
- PoR does not prove unencumbered assets or continuous solvency
- Entities and permissions vary by service and region
- Funding speed can coexist with withdrawal holds; live scenarios are specified as controlled routes
Operator evidence file4 recorded fields
Exact product
Kraken Exchange is custodial; Kraken Wallet is a separate self-custody application.
Operating entity
Global and EEA terms allocate services across different entities; the relevant activity must be matched to its contract.
Custody and controls
Kraken documents platform and account controls plus point-in-time reserve verification, with explicit limitations.
Costs and exit
Instant and Pro pricing differ. Funding methods can impose 72-hour or seven-day withdrawal holds.
Investigative analysis
Claims, records and the gaps between them.
Each conclusion is tied to the primary records immediately below it. Links open the publisher’s original material.
One Kraken label covers distinct control models
Kraken’s own help centre distinguishes its custodial Exchange from Kraken Wallet, where the user holds the recovery material. This is not a cosmetic product split: it changes who can restore access, impose account restrictions and authorise transfers.
Sources: Kraken Support · KrakenEntity disclosure is detailed but activity-dependent
The EEA terms allocate crypto-asset, e-money and certain investment or derivative services among Irish and Cypriot entities. That granularity is useful evidence, yet it prevents a blanket claim that every feature a European visitor sees has the same permission or counterparty.
Sources: Kraken · KrakenSecurity claims contain both substance and scope
Kraken documents cold/hot-wallet practices, passkeys, granular two-factor authentication and Global Settings Lock, alongside ISO 27001 and a SOC 2 Type 1 examination. These records support the existence of controls; they do not show that every user enabled them or that the examination covered every product, threat and future period.
Sources: Kraken · KrakenProof of reserves answers a narrower question
The reserve page reviewed for this edition displayed a 30 June 2026 snapshot and a route for customers to check Merkle inclusion. Kraken also identifies point-in-time and encumbrance limitations. We therefore treat PoR as evidence about selected balances at a date, not a financial-statement audit or solvency guarantee.
Sources: KrakenFast funding can have a slow exit condition
Kraken’s fee schedule separates consumer Instant transactions from the Kraken Pro maker/taker model. Its funding documentation also records methods that may be processed quickly while imposing a 72-hour or seven-day withdrawal hold. Comparing only arrival time would omit the condition most relevant to an urgent exit.
Sources: Kraken · Kraken SupportHistorical regulation is part of the record, not today’s verdict
The SEC’s 2023 staking settlement is a primary record about a specific US service and period. It is material context but does not by itself establish the status of every current Kraken product. Current contracting terms and registers still need to be read beside that history.
Sources: US SEC · Kraken · KrakenClaim → evidence → gap
Ten claims placed under an accountable burden of proof.
Each module keeps the decision consequence beside the evidence and the unresolved gap. Primary material was retrieved on .
The user will configure passkeys, 2FA and Global Settings Lock.
Kraken documents a comparatively granular control set.
A professional order-book route and explicit fee schedule are priorities.
The documentary record supports a reproducible Pro scenario.
A reserves snapshot must prove continuous solvency.
The procedure is scoped and point-in-time.
Instant funding must always mean immediate withdrawal.
Published funding methods can carry 72-hour or seven-day holds.
01
01 / Product claim
- Claim under review
- Kraken Exchange and Kraken Wallet share one control model.
- Evidence on record
- Kraken distinguishes custodial exchange services from its self-custody wallet.
- Unresolved gap
- Wallet runtime is outside this file.
- Decision impact
- Choose intermediary custody or user-controlled recovery before comparing features.
Adjacent sources: Kraken Support · Kraken
02
02 / Entity claim
- Claim under review
- One Kraken company provides every EEA activity.
- Evidence on record
- EEA terms allocate services among activity-specific entities.
- Unresolved gap
- The reader’s actual feature and residence are not fixed.
- Decision impact
- Entity and permission must travel with the exact service.
03
03 / Custody claim
- Claim under review
- Account security controls remove custodial risk.
- Evidence on record
- The exchange holds assets while the user can configure access and withdrawal controls.
- Unresolved gap
- Segregation, insolvency outcome and live withdrawal handling are not established by settings pages.
- Decision impact
- Treat account takeover and platform counterparty risk separately.
04
04 / Security claim
- Claim under review
- Published controls are active for every customer.
- Evidence on record
- Kraken documents passkeys, multiple 2FA roles and Global Settings Lock.
- Unresolved gap
- Default state, recovery bypass and user configuration remain unobserved.
- Decision impact
- The live protocol must prove the control chain, not merely its menu presence.
Adjacent sources: Kraken
05
05 / Reserves claim
- Claim under review
- Proof of reserves is a full audit.
- Evidence on record
- The reviewed page presents a dated snapshot and user inclusion process.
- Unresolved gap
- Off-chain liabilities, encumbrance, future solvency and wider controls remain outside the procedure.
- Decision impact
- Use PoR as bounded evidence, never a solvency guarantee.
Adjacent sources: Kraken
06
06 / Cost claim
- Claim under review
- Kraken Pro fees describe every purchase.
- Evidence on record
- The schedule separates professional maker/taker and convenience routes.
- Unresolved gap
- Spread, rail and withdrawal cost are not measured together.
- Decision impact
- Compare complete receipts for a fixed account and time.
Adjacent sources: Kraken
07
07 / Exit claim
- Claim under review
- Fast deposit means liquid funds.
- Evidence on record
- Funding documentation lists method-specific holds.
- Unresolved gap
- Actual tradable and withdrawable timestamps are specified as fixed outputs.
- Decision impact
- Record both clocks before choosing a rail.
Adjacent sources: Kraken Support
08
08 / Execution/API claim
- Claim under review
- A professional interface proves better fills.
- Evidence on record
- The product and fees are documented.
- Unresolved gap
- Depth, slippage, API scope and cancellation are not observed.
- Decision impact
- No execution superiority is claimed without matched orders.
Adjacent sources: Kraken
09
09 / Privacy/remedy claim
- Claim under review
- A known operator makes support and privacy outcomes predictable.
- Evidence on record
- Terms provide an accountability frame.
- Unresolved gap
- Telemetry, data request and complaint performance are untested.
- Decision impact
- A named entity is necessary but not sufficient evidence of remedy quality.
10
10 / Regulatory-history claim
- Claim under review
- The 2023 staking settlement defines every current service.
- Evidence on record
- The SEC record concerns named US entities and a specific programme.
- Unresolved gap
- Current spot and non-US permissions require current records.
- Decision impact
- Preserve history without extending it beyond product, entity and period.
Accountable scenario file
What the next observation must record.
Each row specifies a fixed protocol with defined inputs and record.
Funding-hold clock
Fixed inputs: One entity, rail, amount and verified account.
Record: Deposit cost, tradable time, withdrawable time and notices.
PublishedSecurity-chain challenge
Fixed inputs: Passkey, 2FA and Global Settings Lock on a no-value account.
Record: Sensitive-setting change, recovery dependencies and delay enforcement.
PublishedPro execution
Fixed inputs: Fixed pair, notional and UTC window; market plus passive limit.
Record: Depth, spread, fee, fill, slippage, cancellation and API parity.
PublishedComplaint and data route
Fixed inputs: Named entity and one non-urgent written request.
Record: Consent controls, response owner, accuracy and escalation route.
PublishedChange timeline
Events that change the reading.
- US staking settlement announced.
Product-specific permissions remain a live diligence question.
- Reviewed proof-of-reserves snapshot date.
Reserve evidence must keep its asset and time boundary.
- Terms, security, fees and funding pages re-retrieved.
Scenario parameters can now be frozen.
Alternatives
When another responsibility model fits better.
Coinbase Advanced
Listed-company disclosure and a familiar retail route outweigh security-setting depth.
Binance
Broader markets/APIs are essential and the local entity is clearly available.
Conclusion control
Medium evidence confidence.
- Supported
- Current terms, fee/funding tables, security documents and a dated reserve process are traceable.
- Gap
- Runtime controls, holds, execution, privacy and remedy remain unobserved.
- What changes the conclusion
- A contract change, recovery bypass, repeated exit failure or strong controlled results would change the conclusion.
Method
How the burden of proof is applied.
- Bind service and residence to the correct terms.
- Record the reserve date and exclusions.
- Freeze security state, funding rail and market inputs.
- Separate control availability from configured, observed behaviour.
Change log
Material file revisions.
Added ten claim files and four reproducible control, funding, execution and remedy scenarios.
FAQ
Questions that survive the headline.
Is Kraken Wallet included?
No; it is self-custodial.
Does PoR prove solvency?
No; it is scoped point-in-time evidence.
Can instant funding delay withdrawal?
Yes, depending on the documented method.
Why configure Global Settings Lock?
It can slow sensitive changes; its recovery/bypass path is recorded as a fixed verification input.
Primary-source register
Reviewed on by Candid Ledger Editorial Team; independent editorial review by Candid Ledger Review Team.
- Kraken global terms of service — Kraken · retrieved 16 August 2026
- Kraken EEA terms of service — Kraken · retrieved 16 August 2026
- Kraken Wallet and Kraken Exchange differences — Kraken Support · retrieved 16 August 2026
- Kraken security practices — Kraken · retrieved 16 August 2026
- Kraken proof of reserves — Kraken · retrieved 16 August 2026
- Kraken fee schedule — Kraken · retrieved 16 August 2026
- Cash deposit options, fees and processing times — Kraken Support · retrieved 16 August 2026
- Kraken staking-as-a-service settlement — US SEC · retrieved 16 August 2026