An exchange listing creates an operational commitment. Customers expect deposits to arrive, balances to reconcile, markets to function and withdrawals to work when demand increases. An asset can pass an initial review and still become unsuitable after its contracts, governance or liquidity change. The institutional question is therefore how an exchange maintains the basis for support throughout the asset's life.
Coinbase's published asset listing process separates legal, compliance and technical security review. Its listings page also describes moving into trading when liquidity conditions are met. Those are useful examples of distinct decision gates. They do not provide a transferable endorsement for another venue, jurisdiction or investment mandate.
Define exactly what is being approved
Start with the asset identifier, network, contract address and supported product. Trading a native token, holding a wrapped representation and offering a staking service create different dependencies. A business committee should receive a precise description of the proposed service, rather than an asset name and a market-capitalisation chart.
The legal analysis should identify the entity offering that service and the customers allowed to use it. A conclusion for one jurisdiction should not silently become a global conclusion. Keep a dated analysis of the actual activity, its restrictions and the facts that would trigger reconsideration. Record the evidence behind the conclusion and the person accountable for maintaining it.
Review powers as well as code
A technical review should map minting, pausing, freezing, upgrading and recovery powers. Identify the keys that exercise those powers, their control arrangements and any delay before changes take effect. An audit of one implementation does not establish that every subsequent implementation will behave the same way.
Ask the operating team to demonstrate deposits and withdrawals under realistic conditions. Include incorrect network selections, transaction reversals before the chosen confirmation threshold, node outages and unexpected token behaviour. The objective is to establish how customer liabilities will be reconciled to supported assets when the happy path fails. Our article on token identifiers and reference data explains why a familiar ticker is an inadequate operational identifier.
Treat launch liquidity as a separate gate
A technically supportable asset may still lack a credible market. Review executable depth, expected order sizes and the distribution of liquidity across participants. Reported volume alone cannot show whether an institutional order can be completed without a large price move. A launch committee should understand who supplies quotes and what commitments, if any, survive a volatile opening.
Consider a hypothetical asset with several market makers that all borrow inventory from the same treasury. Counting the firms individually would exaggerate independence. The diligence file should identify shared inventory, shared funding and withdrawal conditions. The exchange should also define when trading starts, which order types are permitted initially and who can pause the market.
Write the continuing review before launch
Approval should include monitoring triggers. Examples include a contract upgrade, a material change in token supply, a significant loss of market depth or a new concentration of administrative control. Decide which triggers produce an alert, which require a fresh decision and which justify restricting a product pending review.
An annual calendar is helpful but incomplete. Event-driven review matters because the facts supporting approval can change between scheduled meetings. Preserve the launch baseline so reviewers can distinguish a known limitation from a new deterioration. A review that merely repeats the original questionnaire may miss precisely the changes that matter.
Make the exit process operational
A restriction or delisting decision affects open orders, unsettled trades, customer communications and withdrawal availability. Set the sequence in advance. Establish who authorises each step, how balances are retained and what happens if the network is no longer usable. Customers need dates and supported actions, while staff need a reconciled inventory and an escalation route.
The decision record should contain the evidence reviewed, unresolved conditions, approval owners and reopening triggers. That turns listing into a maintained service obligation rather than a marketing milestone. For related institutional perspectives, Anthony Bassili's speaker profile provides an asset-management context; it is not an endorsement of any particular listing process.