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

EXCHANGE DOCUMENT RUN

Crypto.com

Document run splits App, Exchange and Onchain, maps selected regional entities, timestamps fee evidence and bounds the 2022 reserve package.

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

Crypto.com App and Exchange documentary surfaces, with Onchain used only to prove category separation; no derivatives or live route assumed available.

EDITORIAL OUTPUT

ASSESSMENT

The critical test is scope discipline. Crypto.com produces enough material to classify its surfaces and selected regional entities, but a single fee, custody or regulation result for the entire brand would fail reproducibility.

AUDIENCE

SUITABLE FOR

Readers prepared to record country, product surface, tier and eligibility before comparing a transaction path.

DECISION VARIABLE

PRIMARY TRADE-OFF

Multiple service surfaces expand capability while multiplying the protocol variables required for a valid 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 / Onchain names a Cayman provider; US, Singapore and Dubai materials identify other service entities.

LIMIT / The map is incomplete without the user’s product and location.documented
CU

CUSTODY AXIS

DOCUMENT / The App is documented as custodial and Onchain as self-custody.

LIMIT / This does not establish asset safeguarding or current reserves for every Exchange entity.documented
CX

COST AXIS

DOCUMENT / The 9 July 2026 Exchange schedule displayed 0.250% maker / 0.500% taker Level 1; EEA App pricing differs.

LIMIT / A dated example cannot predict the user’s tier, spread or route total.documented
OP

OPERATIONS AXIS

DOCUMENT / Security and public registers are available for selected regions; a 2022 AUP snapshot is linked.

LIMIT / Documents do not measure current uptime, support or solvency.documented
OPEN TEST PROTOCOL →
SUPPORTING SIGNALS

STRENGTHS

  • First-party App/Onchain distinction
  • Published regional entity and regulator records
  • Dated Exchange and EEA App fee disclosures
BOUNDARY CONDITIONS

LIMITATIONS

  • Product surfaces cannot share one result
  • Margin and derivatives are eligibility-sensitive
  • The public PoR reference is a December 2022 AUP snapshot

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

Surface split

App, Exchange and Onchain are distinct objects.

NEXT RUN / Select only one product and jurisdiction.DOCUMENTED
X-02

Entity routing

Several region-specific entities are documented.

NEXT RUN / Match account agreement to an authoritative register.DOCUMENTED
X-03

Fee capture

Product-specific fee schedules are timestamped.

NEXT RUN / Repeat with actual tier, order and withdrawal network.DOCUMENTED
X-04

Assurance bound

The public reserve artefact is dated December 2022.

NEXT RUN / Do not convert it into present solvency assurance.DOCUMENTED

ANALYSIS OUTPUT

Protocol interpretation

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

A-01

P0 / Three surfaces

The App, Exchange and Onchain cannot enter one experimental subject. Crypto.com’s own material identifies the App as custodial and Onchain as self-custodial, while the Exchange is a separate trading interface. A merged score would combine incompatible recovery and intervention mechanisms.

SOURCES / Crypto.com Help · Crypto.com
REVIEWED
A-02

P1 / Provider routing

Onchain terms name Onchain Wallet Limited in the Cayman Islands and describe special North American arrangements. A US entity document plus MAS and VARA registers add other service-specific nodes. The resulting map is useful, but each edge still needs a product and market parameter.

SOURCES / Crypto.com · Crypto.com · MAS · VARA
REVIEWED
A-03

P2 / Fee timestamp

On 9 July 2026 the Exchange schedule provided a Level 1 example of 0.250% maker and 0.500% taker. The EEA App publishes a different schedule. The protocol can reproduce the document observation, not a permanent fee claim or the realised cost of an unexecuted order.

SOURCES / Crypto.com · Crypto.com Help
REVIEWED
A-04

P3 / Feature eligibility

Exchange materials describe spot and, where permitted, margin or derivative functions. Documentary presence passes a capability check only; jurisdiction, qualification and account configuration decide whether the feature is actionable. Performance and liquidation behaviour remain outside the paper run.

SOURCES / Crypto.com · Crypto.com · VARA
REVIEWED
A-05

P4 / Assurance date

The public proof-of-reserves page points to agreed-upon procedures from December 2022. AUP evidence is bounded by specified procedures, assets and date and is not an audit opinion. The lab marks this artefact historical and refuses to extrapolate it to August 2026 solvency.

SOURCES / Crypto.com
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

App and Exchange will be tested as separate routes.

The documentation supports a product-boundary experiment.

USE

A named MAS/VARA entity is relevant.

Official registers provide scopeable inputs.

AVOID

One brand-wide custody/fee output is required.

The surfaces are materially different.

AVOID

A 2022 reserves procedure must prove current solvency.

The temporal and scope gate blocks that conclusion.

Surface lock

Objective
Prevent App/Exchange/Onchain mixing.
Fixed inputs
Custodial App or Exchange; Onchain excluded from exchange run.
Procedure
Save surface, region and account state.
Document baseline
Provider explicitly distinguishes custody models.
Pass artefact
Every screenshot/receipt identifies surface.

SOURCES / Crypto.com Help · Crypto.com

Entity/permission match

Objective
Resolve operator and activity.
Fixed inputs
One target market and chosen surface.
Procedure
Match terms/entity disclosure to MAS/VARA or other authoritative record.
Document baseline
Named entities and activities differ by market.
Pass artefact
Entity, permission, condition and product align.

SOURCES / Crypto.com · MAS · VARA

Custody transition

Objective
Trace asset across branded products.
Fixed inputs
App, Exchange and one external self-custody address.
Procedure
Record ledger/control state before and after each transfer.
Document baseline
App is custodial; Onchain is user-custodied.
Pass artefact
Every boundary, restriction and chain transaction is visible.

SOURCES / Crypto.com Help · Crypto.com

Security control challenge

Objective
Test passkeys/MFA/whitelist behaviour.
Fixed inputs
No-value account with controls fixed.
Procedure
Enable controls, add address, recover device and attempt withdrawal.
Document baseline
Security page describes controls/certifications.
Pass artefact
Delays, notifications and bypasses reconcile to claims.

SOURCES / Crypto.com

Assurance-date gate

Objective
Prevent certification/PoR overstatement.
Fixed inputs
Current security claims and December 2022 reserve material.
Procedure
Record report/certificate issuer, system, period, scope and exceptions if available.
Document baseline
Provider presents certifications; cited PoR is historical.
Pass artefact
Only artefact-supported scope reaches output.

SOURCES / Crypto.com · Crypto.com

App/Exchange cost

Objective
Compare product economics.
Fixed inputs
EUR 1,000, same asset/account/five-minute window.
Procedure
Capture App quote/spread, Exchange fee/fill and both exit quotes.
Document baseline
Separate fee schedules exist.
Pass artefact
Final withdrawable asset amount reconciles.

SOURCES / Crypto.com · Crypto.com Help

Funding/external exit

Objective
Measure integrated journey limits.
Fixed inputs
One rail, asset and network.
Procedure
Timestamp funding, internal transfer, whitelist, release and chain arrival.
Document baseline
Documentation shows integrated surfaces but not runtime quality.
Pass artefact
Asset path and every hold/fee are complete.

SOURCES / Crypto.com Help · Crypto.com Help

Execution/API separation

Objective
Test quoted App versus order-book Exchange.
Fixed inputs
Same economic notional and market window.
Procedure
Record quote, depth, fill, slippage, cancellation and API scope.
Document baseline
Surfaces use different execution models.
Pass artefact
No blended result; each route has reproducible output.

SOURCES / Crypto.com · Crypto.com Help

Privacy by surface

Objective
Map identity/permission/telemetry differences.
Fixed inputs
Fresh App and Onchain installations, default permissions.
Procedure
Capture KYC, device/contact permissions, service requests and controls.
Document baseline
Custody and identity needs differ.
Pass artefact
Every surface has its own data-flow output.

SOURCES / Crypto.com Help · Crypto.com

Support/dispute by entity

Objective
Measure accountable escalation.
Fixed inputs
One App and one Exchange policy question for named market.
Procedure
Record channel, owner, response, governing terms and external route.
Document baseline
Registers establish entities, not remedy performance.
Pass artefact
Entity-specific written outcomes are obtained or failure logged.

SOURCES / MAS · VARA · Crypto.com

DECISION ENVIRONMENTS

Run the product as a user would decide.

D-1

EEA retail buyer

Environment / Verified App account.

Variables / EUR 1,000 asset purchase.

Output / Quote/spread/exit receipt.

PUBLISHED
D-2

Exchange trader

Environment / Same user and asset/window.

Variables / Order-book market/limit.

Output / Fee/fill dataset.

PUBLISHED
D-3

Ecosystem transfer

Environment / App→Exchange→external.

Variables / One asset/network.

Output / Custody/hold trace.

PUBLISHED
D-4

Regional complainant

Environment / Named Foris entity.

Variables / Security/fee question.

Output / Remedy output.

PUBLISHED

CHANGE SIGNALS

Timeline affecting the rig.

  1. Cited reserve AUP date.

    Current solvency output blocked.

  2. VARA licence issued to named Dubai entity.

    Permission resolver includes activity/condition.

  3. Product/security/register inputs refreshed.

    Runtime matrix ready.

ALTERNATIVE RIGS

Test another object when the variable changes.

Coinbase

A narrower custodial route is desirable.

Trust Wallet

The required output is multi-chain self-custody.

STOP GATE

MEDIUM CONFIDENCE

BASIS
Product documents and official registers support the surface/entity baseline.
BLOCK
Controlled runs for cost, transfer, control, privacy and remedy are published as fixed protocol outputs.
CHANGE CONDITION
Current assurance plus clean repeatable product runs raises confidence; boundary ambiguity or failed exit lowers it.

METHOD

Control discipline.

  1. One product per run.
  2. One entity/activity per register match.
  3. Use matched economic inputs.
  4. Keep assurance scope and runtime behaviour separate.

CHANGE LOG

Rig revisions.

Added ten product-separated protocols and four regional user scenarios.

FAQ

Protocol questions.

Is Onchain in the exchange run?

No.

Can VARA evidence be globalised?

No.

Is 2022 PoR current audit evidence?

No.

Are App and Exchange costs interchangeable?

No; matched runs are required.

SRC

Primary-source register

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

ARTEFACTS