A cryptocurrency exchange is a market-facing venue or system that connects participants with trading processes for digital assets. For builders, operators, and institutions, the essential distinction is that trading, asset control, and settlement are related but separate functions: the exchange label alone does not say which entity performs each one or how they connect.
What a cryptocurrency exchange does in the market
At the infrastructure level, an exchange gives participants a way to access a market-facing trading platform. Access can occur through direct interaction with a platform or through a cryptoasset service provider. This describes a connection between participants and trading, not a universal design for the systems behind it.
A market environment can be mapped conceptually as participants and access interfaces connected to trading systems, alongside relationships involving custody, settlement, data, and external services. Those relationships vary by arrangement, so the map is a guide to questions rather than a claim that every venue has the same components or architecture.
The distinction matters because an exchange is not simply a synonym for every service associated with a digital-asset trade. A venue’s market role concerns access to trading; custody concerns asset control; settlement concerns completing obligations or transfers. These roles can be organized within one provider or distributed across multiple firms and services.
Some centralized exchanges illustrate how functions can overlap: a centralized operator may combine third-party trading, proprietary trading, margin lending, token issuance, and custody services. This is not a description of every exchange, and a combined business model does not erase the need to identify each function and its boundaries.
The participants and interfaces around an exchange
The participants connected to an exchange can include individuals, institutions, and service operators. Their access may be through a market-facing platform directly or through a provider that connects them to it. The interface is the point of access; it does not, by itself, establish who holds assets or which system completes settlement.
A practical infrastructure map separates at least three connections. First is participant-to-platform access: how a person or organization reaches the trading system. Second is the trading system itself: where trading activity is processed or recorded. Third are the supporting relationships, which may include custody, settlement, data, and external services. The details differ among arrangements, so a general diagram cannot establish which party is responsible for a particular function.
The same caution applies to provider labels. Some cryptoasset service providers may combine trading, custody, lending, market-making, and other services, but that list should not be read as a description of every provider or account. One provider might handle several parts of a market relationship, while another arrangement may separate them. To understand a specific venue, readers need to identify the legal or operational entity behind each role and review current documentation for the applicable arrangement.
How trading, asset control, and settlement fit together
A useful conceptual sequence begins when a participant accesses a trading system and submits an instruction. The system processes trading activity and records or communicates an outcome. This sequence describes the relationship among components; it does not specify a particular order type, matching method, record format, or settlement design.
Execution, asset control, and settlement answer different questions. Execution asks what happened to the trading instruction within the venue’s process. Asset control asks where the relevant assets are held and who or what can authorize movement. Settlement asks how resulting obligations or transfers are completed. A trade record alone does not answer the asset-control question or establish how a later transfer is settled.
In a common centralized-exchange model, a customer typically transfers funds and their custody to the exchange before trading on an internal order book. Custody and legal ownership arrangements nevertheless vary by platform and jurisdiction, so this general model cannot be applied automatically to an individual venue.
The practical implication is to trace records and control separately. A trading account entry may describe activity within a venue’s system, while asset control and settlement may involve other arrangements. Do not infer that an internal trade necessarily corresponds to an immediate blockchain transaction, or that a venue’s trading function means it also controls every asset or settlement step. The evidence available for a specific venue must establish those connections.
Infrastructure standards also distinguish settlement systems and central securities depositories as roles separate from other financial market infrastructure functions, with guidance addressing linked settlement obligations and custody-related risk. This is a general conceptual distinction, not a classification of every crypto exchange under a particular framework.
Where exchanges sit alongside other crypto market infrastructure
An exchange environment can relate to market data, custody, settlement, and external services, but the responsible systems and providers vary. A venue’s connection to a blockchain is therefore a separate question from whether it offers market-facing trading. Where blockchain settlement is involved, the relevant chain and any intermediary mechanisms must be identified from the specific arrangement rather than assumed from the word “exchange.”
Liquidity pools provide a useful boundary example. A Uniswap v2 liquidity pool uses deposited reserves of a token pair as the inventory from which swaps execute, with liquidity-provider shares representing contributions. That is a specific constant-product AMM example, not a universal description of all pools or exchange designs.
This distinction helps keep the infrastructure map precise: a pool-based swap mechanism is not simply another name for a centralized venue. Some decentralized exchanges implement trading through smart contracts and liquidity pools, with transactions settling when included in a blockchain block. Order-book, auction, intent-based, cross-chain, and hybrid designs can follow different execution paths.
The trading venue, interface, and settlement layer need not be identical. A system may distribute or combine these layers differently. As a result, describing an exchange as “on-chain” or “off-chain” without specifying which function is meant may obscure whether the label refers to access, trading records, execution, custody, or settlement. This explainer does not assess order-book mechanics, liquidity measurement, market-maker activity, or API implementation; those are separate questions from mapping the exchange’s infrastructure role.
Questions to resolve when assessing an exchange’s infrastructure role
For a specific venue, investigate the connections rather than relying on a category label:
- Which legal or operational entity is responsible for each function, and what jurisdiction and status apply?
- Which access interfaces connect participants with the trading platform?
- Which systems process trading activity and record the resulting transactions?
- Where are assets held, who controls them, and how does that arrangement relate to trading records?
- What process completes settlement, and which external services or systems participate?
- Are custody, settlement, data, or other functions provided by the venue or by separate firms?
These are due-diligence questions, not conclusions about a particular provider. Assessing an exchange or related provider requires identifying the responsible entity, relevant jurisdiction and legal status, functional boundaries, custody and settlement arrangements, applicable terms, and current evidence for operational or protection claims.
Fees, availability, yields, security controls, recovery, service terms, and compliance claims also require current, specific documentation. Their presence or absence cannot be inferred from the general infrastructure model. This system-level map is a starting point for research, not a venue ranking, recommendation, or assessment of trading suitability.