Why Exchanges Require a Market Maker Before Listing

An exchange does not earn from listing your token. It earns from people trading it, repeatedly, without complaining. A pair with no maker produces exactly the outcomes a venue hates: enormous slippage on modest orders, support tickets about fills, a chart that looks broken on the mobile app, and eventually a delisting review. The listing team is therefore assessing whether your pair will be tradeable, not whether your project is interesting.

That is why the liquidity question appears early in almost every application form, usually phrased as which market maker you have engaged and what depth they will commit to. An honest answer with a named provider and specific numbers moves an application forward faster than a roadmap section ever will.

Expect questions covering: the market maker's legal entity and track record, which other venues it quotes on, the committed spread and depth for your pair, quoting hours and uptime, the size of the liquidity allocation and whether it is loaned or retained, your circulating supply and unlock schedule, and confirmation that no wash trading or self-matching will occur.

Larger venues add operational items — API sub-account structure, designated contacts for incidents, and in some cases a market maker agreement provided directly to the exchange. Tier-one venues increasingly require the provider to be on their own approved maker programme, which is one reason provider selection should precede application submission.

Formally, few exchanges publish a rule saying you must retain a market maker. Practically, the requirement bites in three places: the application scoring, the listing agreement's liquidity covenants, and the post-listing review that can move a pair to a monitoring tag or delist it for insufficient volume and depth. You can decline to engage a provider, but you are then underwriting the book yourself, which is market making performed badly by a team with other priorities.

Smaller venues sometimes offer their own house liquidity in exchange for a fee or a token allocation. That solves the application question but leaves you with a single-venue dependency and no independent measurement of performance.

Engage the provider first and let it help draft the liquidity section. A desk that already quotes on the target venue knows what that venue's listings team expects, what depth numbers are realistic for your float, and how the fee tier affects whether tight quoting is even economic. Submitting numbers your provider has not agreed to is worse than submitting none.

Then present the commitment as a schedule rather than a paragraph: venue, pair, maximum spread, minimum depth at each band, uptime, and coverage hours. Attach the KPI schedule from your agreement. Applications that read like an operational document rather than a pitch get materially better treatment.

Maker rebates determine whether a desk can quote tightly on your pair without losing money on every fill. A provider that already holds a high maker tier on the venue can post narrower spreads at the same economics than one starting from the base schedule. When comparing providers, ask what maker tier they hold on each target venue — it is a harder credential than a client logo.

Some venues also run pair-specific liquidity programmes with enhanced rebates for newly listed assets. These are negotiated by the maker, not the issuer, but you should know whether your provider intends to apply and what that does to your economics.

Most exchanges run an informal review window after a new listing. Volume, depth, spread, and holder distribution are all observed, and the outcome shapes whether you get additional pairs, campaign support, or a quiet slide down the interface. Your provider's reporting should map directly onto whatever the venue is measuring so you can see problems before the exchange raises them.

This is also the window in which to renegotiate. If the book has been tight and volume is organic, a maker often has room to improve terms or add a venue at marginal cost. If it has been thin, you need that conversation documented well before any exchange review lands.

Tier-one exchanges tend to have the most explicit requirements: a named provider with an existing maker relationship on that venue, published depth and spread commitments, and sometimes a direct agreement between the provider and the exchange rather than only between provider and issuer. They also run the most rigorous post-listing reviews, with automated monitoring against the committed KPIs.

Tier-two and regional venues are often more flexible on paper but compensate with commercial terms — a listing fee, a token allocation, or a requirement to use their preferred liquidity partner. These arrangements can still work well, but they deserve the same scrutiny as an independent provider: ask for the same depth, spread, and uptime commitments in writing regardless of who is proposing them.

Smaller or newer venues sometimes have no formal liquidity requirement at all, which is not a benefit. A pair that lists without any committed depth on a venue with limited organic volume tends to trade thinly regardless, and the absence of a requirement often correlates with the absence of the monitoring that would catch problems early.

Exchanges sometimes ask for depth or spread numbers that are unrealistic for the actual float being listed. It is reasonable, and expected, to negotiate — proposing a phased commitment that tightens over the first ninety days as volume becomes clearer is a common and acceptable structure, and most listing teams have seen it before.

What is not advisable is agreeing to numbers your provider has not confirmed it can deliver simply to get the application approved. A missed commitment discovered during a post-listing review does more damage to the relationship than a modest, honestly stated target agreed up front. Put your provider directly in touch with the listing team where the venue allows it; technical questions are better answered by the desk that will actually be quoting.

Two venues nominally in the same tier can specify meaningfully different depth. A global spot exchange with heavy retail flow often wants tighter spreads near the top of book because its own users trade in small size and are sensitive to visible slippage on a mobile app. A venue skewed toward professional flow may care less about the tightest quote and more about consistent depth several bands out, because that is where its larger orders actually execute.

Regional exchanges frequently specify liquidity requirements denominated in the exchange's own base currency or stablecoin pair rather than in USD terms, which changes the practical depth figure once converted. Ask the listing team for the reference currency and measurement window explicitly, since a target quoted informally in a call and one written into the agreement sometimes differ.

Derivatives-adjacent venues that also plan to list futures on the same asset often want spot depth verified first, so the spot commitment can end up gating a second listing.

Beyond the liquidity section, reviewers typically work through token contract audits, circulating supply calculation methodology, treasury multisig structure, unlock schedule against the stated tokenomics, and whether any prior venue has flagged the project for wash trading or manipulation. The liquidity commitment is assessed alongside these items rather than in isolation, because a strong book on a token with unresolved supply questions still fails review.

Compliance-adjacent items also feature: sanctions screening on the founding team, jurisdiction of the issuing entity, and whether the token has security-like characteristics under the laws the exchange operates under. None of this is specific to market making, but a weak liquidity section combined with an incomplete compliance file is treated as a single pattern of an underprepared applicant, which slows the whole review rather than just the liquidity component.

For a tier-one venue, expect four to eight weeks from a complete application to a listing decision, assuming no material follow-up requests. Incomplete liquidity sections are one of the most common causes of an extended review, since the exchange has to come back with clarifying questions rather than approving on the first pass. Tier-two and regional venues can move faster, sometimes within two to three weeks, but often with less rigorous post-listing monitoring to offset that speed.

Once approved, technical onboarding — sub-account creation, API provisioning, treasury funding of the maker's inventory — typically runs one to two weeks in parallel with the exchange's own marketing preparation. Building the liquidity relationship before submitting rather than after approval removes this stage from the critical path entirely, since the provider can be funded and testing on the venue the day the pair goes live.

The most frequent error is naming a market maker in the application before that provider has actually confirmed the depth and spread figures being submitted. Reviewers occasionally contact the named provider directly, and a mismatch between what the issuer submitted and what the provider will confirm reads as either poor coordination or an exaggerated claim, neither of which helps the application.

A second common mistake is submitting a liquidity plan denominated in absolute token quantities without reference to circulating supply or float, which makes the commitment impossible for a reviewer to sanity-check quickly. A third is treating the liquidity section as a one-time submission rather than a living commitment — venues that run structured post-listing reviews expect updates if depth targets or venue coverage change materially after go-live.

Most listing teams monitor a narrower set of numbers than the full commitment schedule implies: time-weighted spread across the trading day, depth at the specified bands sampled at intervals rather than continuously, uptime as a percentage of exchange operating hours, and total volume relative to comparable recently listed pairs. Persistent underperformance on any one of these, rather than a single bad day, is what triggers a review.

Ask your provider for reporting that mirrors this exact structure rather than a generic performance summary, so that if the exchange raises a concern you already have the matching data in hand rather than needing to reconstruct it under time pressure during the review itself.