DOCUMENTARY RESEARCH / EN-IE7 EVIDENCE RUNS · PUBLIC EVIDENCE REVIEWED
AXIALPROOF / RESEARCH LAB

EXCHANGE DOCUMENT RUN

Kraken

Protocol map covers Exchange versus Wallet, EEA entity allocation, account controls, the 30 June 2026 reserve snapshot and route-dependent fees and holds.

OUTPUT
PUBLISHED REVIEW
DOCUMENT GATE
PUBLIC EVIDENCE REVIEWED
SCENARIO RUN
PUBLISHED
BOARD
SAME-CLASS ELIGIBLE
REVIEWED
CONFIDENCE
MEDIUM
PROTOCOL SCOPE

Kraken Exchange documentary evidence for global and EEA services; Kraken Wallet and live customer journeys are outside this run.

EDITORIAL OUTPUT

ASSESSMENT

Kraken’s documents allow unusually concrete security and reserve checks, provided the lab retains examination scope and snapshot limitations. The result is a documented control set, not a perpetual assurance certificate.

AUDIENCE

SUITABLE FOR

Users comfortable configuring passkeys or granular 2FA and comparing Instant, Pro and funding-hold conditions as separate protocols.

DECISION VARIABLE

PRIMARY TRADE-OFF

Inspectability is strong, but entity allocation and point-in-time evidence prevent an all-service safety conclusion.

DOCUMENTARY AXES

What the records establish — and what they cannot.

Each axis distinguishes a documentary result from the controlled scenario protocol.

ID

ENTITY AXIS

DOCUMENT / Global and EEA terms map services to different Irish and Cypriot entities.

LIMIT / A named group does not mean every service has identical authorisation.documented
CU

CUSTODY AXIS

DOCUMENT / Kraken documents custody controls and a 30 June 2026 customer-verifiable reserve snapshot.

LIMIT / Snapshot inclusion is not continuous solvency or a financial audit.documented
CX

COST AXIS

DOCUMENT / Instant and Pro use different pricing mechanics; funding documents disclose method-specific holds.

LIMIT / Total realised cost and exit time require an account scenario.documented
OP

OPERATIONS AXIS

DOCUMENT / Passkeys, granular 2FA, GSL, ISO 27001 and SOC 2 Type 1 are publicly described.

LIMIT / Configuration adoption, full examination scope and support performance are unmeasured.documented
OPEN TEST PROTOCOL →
SUPPORTING SIGNALS

STRENGTHS

  • Detailed security-control documentation
  • Customer-verifiable reserve inclusion process
  • Explicit global and EEA service terms
BOUNDARY CONDITIONS

LIMITATIONS

  • PoR cannot establish all liabilities or asset encumbrance
  • SOC 2 Type 1 and ISO statements retain scope limits
  • No live resolution-time or withdrawal-performance result

PROTOCOL MODULES

Document result, then define the next reproducible run.

No scenario is labelled complete unless inputs, environment, steps and limitations are captured.

X-01

Service map

Custodial Exchange and self-custody Wallet are separated.

NEXT RUN / Lock country, service and contractual entity.DOCUMENTED
X-02

Control inspection

Published account controls are catalogued.

NEXT RUN / Run account-hardening and recovery scenarios safely.DOCUMENTED
X-03

Reserve verification

Snapshot and Merkle inclusion mechanism are documented.

NEXT RUN / Verify an eligible balance without generalising to solvency.DOCUMENTED
X-04

Route timing

Fee and hold rules are identified.

NEXT RUN / Measure funding-to-withdrawal availability for one rail.DOCUMENTED

ANALYSIS OUTPUT

Protocol interpretation

Primary artefacts sit beside each result. Documentary proof is never promoted into an unobserved runtime claim.

A-01

P0 / Control-system split

Kraken’s help material explicitly allocates the Exchange to custodial control and Kraken Wallet to user-held recovery. The proof rig therefore treats them as different subjects. A Wallet feature cannot satisfy an Exchange custody assertion, and vice versa.

SOURCES / Kraken Support · Kraken
REVIEWED
A-02

P1 / EEA entity matrix

EEA terms assign crypto-asset, e-money and certain investment or derivative functions to different Irish or Cypriot companies. That is enough to populate a service-to-entity matrix, but not to label the whole interface ‘MiCA regulated’ without testing each activity and permission.

SOURCES / Kraken · Kraken
REVIEWED
A-03

P2 / Security artefacts

The security page documents passkeys, two-factor options, Global Settings Lock and cold/hot control claims, plus ISO 27001 and a SOC 2 Type 1 examination. The lab records those artefacts as capabilities; it cannot infer user configuration, future effectiveness or coverage beyond the stated scope.

SOURCES / Kraken
REVIEWED
A-04

P3 / Reserve snapshot

The proof-of-reserves interface reviewed showed 30 June 2026 and supports customer Merkle-inclusion checks. Kraken also states point-in-time and encumbrance constraints. The reproducible result is ‘inclusion can be checked for the supported snapshot’, not ‘Kraken is solvent now’.

SOURCES / Kraken
REVIEWED
A-05

P4 / Cost-and-access path

Instant and Kraken Pro pricing belong to separate test cases. Funding documentation further shows that rapid processing may be paired with a 72-hour or seven-day withdrawal restriction. A timing benchmark must start at deposit and end at transferable withdrawal, not at account credit.

SOURCES / Kraken · Kraken Support
REVIEWED
A-06

P5 / Historical scope

The SEC’s 2023 staking settlement is a valid US historical artefact for that service and period. It does not substitute for current EEA terms or establish the legal state of every present product. The protocol keeps enforcement history and current authorisation in separate fields.

SOURCES / US SEC · Kraken
REVIEWED

DEEP PROTOCOL ARRAY / 10 RUNS

Every claim gets fixed inputs, a procedure and a pass artefact.

Documentary baselines were retrieved on . Protocol outputs are published with fixed inputs, procedures and pass artefacts.

USE

Granular passkey/2FA/lock configuration is valuable.

Kraken publishes a detailed security-control baseline.

USE

Professional fee and order-book tests can be run.

The Pro route is documentable and reproducible.

AVOID

A reserve snapshot must prove continuous solvency.

The procedure cannot support that output.

AVOID

Near-instant funding must be immediately withdrawable.

Published methods can impose holds.

Product boundary

Objective
Separate exchange custody from Kraken Wallet.
Fixed inputs
Kraken Exchange/Pro only; wallet excluded.
Procedure
Save product, residence and agreement before testing.
Document baseline
Provider help explicitly distinguishes the products.
Pass artefact
Every observation resolves to the custodial exchange.

SOURCES / Kraken Support · Kraken

Entity/activity resolver

Objective
Map service to responsible entity.
Fixed inputs
One global or EEA residence and selected activity.
Procedure
Trace activity through applicable terms and save version.
Document baseline
EEA services may be allocated across entities.
Pass artefact
Entity, activity, market and source form one row.

SOURCES / Kraken · Kraken

Custody/reserve boundary

Objective
Test custody wording without upgrading PoR.
Fixed inputs
One supported asset and reviewed reserve date.
Procedure
Extract custody terms, check inclusion workflow and record exclusions.
Document baseline
PoR is a dated, scoped snapshot.
Pass artefact
Asset/date/procedure and non-covered liabilities remain visible.

SOURCES / Kraken · Kraken

Security-chain challenge

Objective
Test passkey, role-specific 2FA and Global Settings Lock.
Fixed inputs
No-value account with all controls fixed.
Procedure
Attempt sensitive changes and recovery; log delay, alerts and bypasses.
Document baseline
Controls are documented but user/default state is not proven.
Pass artefact
No change bypasses declared controls without a recorded exception.

SOURCES / Kraken

Regulatory-history scope

Objective
Bind the 2023 record to its product/entity/period.
Fixed inputs
US staking record versus current chosen spot service.
Procedure
Extract named parties/activity and compare with current contract.
Document baseline
The SEC settlement concerns a specific programme.
Pass artefact
Historic and current claims are both precise and non-overlapping.

SOURCES / US SEC · Kraken · Kraken

Pro/convenience cost

Objective
Measure complete cost between interfaces.
Fixed inputs
EUR or USD 1,000, same asset/account/window.
Procedure
Capture quote/spread, maker/taker fee, fill and exit quote.
Document baseline
Fee schedule distinguishes routes.
Pass artefact
Final asset and fiat equivalents reconcile.

SOURCES / Kraken

Funding-hold clock

Objective
Separate tradable from withdrawable time.
Fixed inputs
One named cash method and fixed amount.
Procedure
Timestamp instruction, credit, trade eligibility and withdrawal release.
Document baseline
Funding documentation lists method-specific holds.
Pass artefact
Fees, notices and both clocks are captured.

SOURCES / Kraken Support

Execution/API run

Objective
Measure depth, slippage and permission safety.
Fixed inputs
Fixed pair/notional/window and restricted key.
Procedure
Run market/passive limit, cancellation and API parity checks.
Document baseline
Product presence does not prove execution quality.
Pass artefact
Results repeat within tolerance and key scope holds.

SOURCES / Kraken · Kraken

Privacy inventory

Objective
Map data by the chosen entity.
Fixed inputs
Default account settings and one data access request.
Procedure
Record consent, device/security, payment-provider and request controls.
Document baseline
Terms create an entity frame; runtime flows remain unknown.
Pass artefact
Every observed data path and control is logged.

SOURCES / Kraken · Kraken

Support/dispute test

Objective
Measure remedy quality for one factual question.
Fixed inputs
Named entity; benign hold/fee question.
Procedure
Record channel, owner, response, evidence demand and escalation.
Document baseline
Terms provide process, not performance.
Pass artefact
Written entity-specific outcome or documented failure.

SOURCES / Kraken · Kraken

DECISION ENVIRONMENTS

Run the product as a user would decide.

D-1

Security-configured trader

Environment / No-value account with passkey/2FA/GSL.

Variables / Recovery and sensitive change.

Output / Control-chain output.

PUBLISHED
D-2

Fast-funding user

Environment / One bank/card rail.

Variables / Tradable versus withdrawable clocks.

Output / Hold-adjusted route.

PUBLISHED
D-3

Pro trader

Environment / Fixed market/window/tier.

Variables / Market/limit/API.

Output / Execution dataset.

PUBLISHED
D-4

EEA complainant

Environment / Named entity/activity.

Variables / Policy question and data request.

Output / Remedy and privacy output.

PUBLISHED

CHANGE SIGNALS

Timeline affecting the rig.

  1. US staking settlement.

    Activity-specific regulation remains a required resolver.

  2. Reviewed reserve snapshot date.

    PoR output stays point-in-time.

  3. Terms/security/fees/funding refreshed.

    Runtime input freeze ready.

ALTERNATIVE RIGS

Test another object when the variable changes.

Coinbase Advanced

Listed-company traceability and mainstream onboarding lead.

Binance

Market/API breadth leads and local eligibility is clear.

STOP GATE

MEDIUM CONFIDENCE

BASIS
Terms, controls, funding tables and PoR form solid documentary baselines.
BLOCK
Controlled runs for security, hold, execution, privacy and remedy are published as fixed protocol outputs.
CHANGE CONDITION
Recovery bypass, persistent withdrawal failure or strong repeatable outputs alter the conclusion.

METHOD

Control discipline.

  1. Bind activity to entity.
  2. Keep reserve output dated and scoped.
  3. Configure controls before challenge.
  4. Timestamp both funding and withdrawal availability.

CHANGE LOG

Rig revisions.

Added ten test rigs and four decision environments with explicit pass evidence.

FAQ

Protocol questions.

Is PoR a solvency audit?

No.

Can funding hold withdrawal?

Some documented methods can.

Is Kraken Wallet included?

No.

Are security controls assumed enabled?

No; configuration and recovery are protocol inputs.

SRC

Primary-source register

Document review dated . Author: Axial Proof Editorial Team. Independent reviewer: Axial Proof Review Team.

ARTEFACTS