Compare Market Maker SLAs for Tier-2 Exchange Listings

If you've ever sat across the table from a market maker's business development team, you know the feeling — a rush of promises delivered with just enough confidence to make you forget you're signing away a meaningful chunk of your token supply for six to twelve months. The pitch sounds polished, the numbers sound reasonable, and everyone in the room nods. Six months later, you're staring at a thin order book, wondering where the liquidity went and whether that monthly invoice you keep paying is actually buying you anything. The gap between what market makers promise and what they deliver isn't always malice — more often, it's a gap in the agreement itself, buried in language that sounds technical but leaves critical questions unanswered.

We work in an industry that treats liquidity as though it appears the moment a token lists on an exchange. It doesn't. And the document that's supposed to guarantee it — the Service Level Agreement, or SLA — is frequently the least scrutinized contract a crypto project signs. This isn't a glamorous topic, but getting it right is one of the few operational levers that actually affects whether your token survives its first year of trading. So let's walk through what a market maker SLA should contain, what the numbers actually mean, and how to compare proposals from different providers without getting lost in jargon.

Defining the Liquidity Baseline: Spread and Depth Requirements

Every market maker engagement starts with a fundamental question: what does "liquidity" look like for your token? It's a deceptively simple question, and the answer is encoded in two primary metrics — the bid-ask spread and the order book depth.

The spread is the gap between the best buy and sell orders on the order book. For Tier-2 exchange listings, market makers typically commit to maintaining a maximum spread within the range of 0.5% to 2.0%. That range is wider than what you'd see on Binance or Coinbase for blue-chip assets, and for good reason — Tier-2 venues carry less organic flow, meaning the market maker absorbs more directional risk on every fill. A 0.5% spread commitment sounds tight and impressive in a proposal, but it's only meaningful if you understand the conditions attached. Is that 0.5% on the first level of the book — meaning the top bid and top ask — or averaged across a certain depth? A spread of 0.5% at a depth of $500 is a very different promise than a 0.5% spread at $50,000 of depth.

The spread your market maker quotes is meaningless without a corresponding depth commitment — a tight spread on paper can mask an order book that evaporates the moment someone places a real trade.

Depth requirements define how much capital the market maker commits at various price levels. Some SLAs specify depth at a fixed percentage from the mid-price — for instance, maintaining at least $10,000 in combined bid and ask liquidity within 1% of the midpoint. Others use a tiered structure, requiring progressively less capital at wider distances. What you want to avoid is an agreement that talks about spread without binding the market maker to a specific depth profile, because that's where the friction begins — you'll have a beautiful-looking order book that provides almost no actual execution quality.

When comparing proposals, ask each provider to specify depth commitments at multiple price levels, denominated in USDT or USD equivalent, not in token quantities. Token-quantity commitments can be gamed by market makers who simply let the token's price decline, thereby reducing their capital exposure while technically meeting the letter of the agreement.

Analyzing Uptime Guarantees and Order Book Continuity

A market maker is only useful when it's actually active. This sounds obvious, but uptime guarantees in SLAs vary enormously — from 95% to 99.9% — and the difference matters more than most founders realize.

A 95% uptime commitment means the market maker is permitted to be offline for roughly 3.6 hours per month. For a token listed on a single Tier-2 exchange, that downtime can translate directly into moments of zero liquidity — the kind of moments where a single sell order from an early investor can move the price 15%, triggering cascading liquidations in any leveraged positions and sending a visible signal to every trader watching the chart. At 99.9% uptime, the permitted downtime drops to about 43 minutes per month — still not zero, but a meaningful improvement that reflects a more serious operational commitment.

The subtlety that gets missed is *when* uptime is measured. Some SLAs calculate uptime across the full 24-hour trading cycle; others exclude certain hours or apply different standards during high-volatility periods. You want a contract that measures uptime during exchange trading hours without carve-outs, because the moments when liquidity disappears are precisely the moments when you need it most — during market stress, during sudden news, during the volatility spikes that define crypto trading.

When evaluating proposals side by side, map each commitment to this kind of framework. A market maker offering a tight spread but weak uptime is selling you visibility without reliability — and on Tier-2 exchanges, where organic order flow is thinner, reliability is what separates a functioning market from a token that looks listed but effectively isn't.

Inventory Management: Balancing Token Supply and Market Maker Risk

Here's where the relationship between your project and the market maker gets genuinely complicated. To provide two-sided liquidity, a market maker needs an inventory of your tokens — typically in the range of 5% to 10% of the circulating supply. This is the mechanism that allows them to place asks on the order book when there's natural buying pressure, and to absorb sells when the market tips the other direction.

The tension is inherent: the market maker wants the maximum inventory with the least downside protection for you, because a larger inventory gives them more flexibility and more opportunities to profit from spread capture. You, on the other hand, want to provide enough inventory for the market maker to do their job, while retaining as much control as possible over how those tokens interact with the market.

There are two common structures for inventory provisioning:

1. Lending arrangement — you lend the market maker a defined quantity of tokens for the contract duration, and they return the same quantity at the end. This is cleaner from a tokenomics perspective, but the market maker may demand higher fees to compensate for the risk of holding a depreciating asset.

2. Direct allocation — you transfer tokens outright, with or without a buyback clause. This gives the market maker more skin in the game and can align incentives if the buyback price is structured correctly, but it also means those tokens are no longer under your control.

In either case, the SLA should specify what happens to the inventory if the contract is terminated early — whether due to breach, mutual agreement, or the exchange delisting the token. We've seen projects discover, six months in, that their market maker is sitting on a material percentage of circulating supply with no clear return timeline, creating a lingering trust deficit with the community.

The tokens you hand to a market maker aren't just operational tools — they represent a transfer of trust from your community to a third party, and the SLA needs to reflect that weight.

The inventory question also intersects with your broader tokenomics design. If your circulating supply is already constrained by vesting schedules, staking locks, or treasury policies, allocating 5–10% to a market maker can create a surprisingly large share of the *actually liquid* supply. Run the numbers against your real float, not your theoretical maximum — the alignment between your inventory commitment and your actual market dynamics is where most SLAs quietly fail.

Structuring Performance Incentives and Monthly Fee Models

Tier-2 exchange market making isn't charity. Providers typically charge a monthly fee — sometimes framed as a flat retainer, sometimes structured as a performance-based incentive tied to volume or spread maintenance. Understanding what you're paying for, and what you're not, is the difference between a productive partnership and a recurring invoice that drains your runway.

The most common fee structures break down as follows:

• Flat monthly fee — a fixed payment regardless of market conditions or trading volume. This is straightforward but creates a misalignment: the market maker gets paid whether or not they're providing meaningful liquidity.

• Retainer plus performance bonus — a base fee supplemented by bonuses for hitting volume targets or maintaining spread below a certain threshold for a defined percentage of time. This is more aligned with project interests but introduces complexity in measurement and verification.

• Volume-based fee — compensation tied directly to trading volume on the listed pair. This aligns incentives strongly but can incentivize wash trading — a practice where the market maker generates volume between their own accounts to meet targets without providing genuine liquidity.

The contract duration matters here too. Standard Tier-2 SLAs run six to twelve months, and most providers require at least a six-month commitment to justify their setup costs — deploying trading infrastructure, acquiring initial inventory, and calibrating algorithms to the specific token's volatility profile. Shorter contracts are possible but come at a premium, and the market maker's long-term commitment to maintaining your order book will reflect the short-term nature of the relationship.

When comparing proposals, calculate the total cost over the full contract period and benchmark it against the liquidity outcomes — not just the numbers on the page. A $15,000 monthly retainer that delivers consistent depth and tight spreads is a better investment than an $8,000 monthly fee that produces an order book nobody can actually trade against. Sustainability of the engagement matters more than the sticker price.

Navigating Contractual Obligations and SLA Breach Protocols

The final piece — and the one most frequently treated as boilerplate — is the breach protocol. What happens when the market maker fails to meet the agreed-upon metrics?

Most SLAs define breach in terms of sustained underperformance — for example, failing to meet the spread commitment for more than 4 consecutive hours or dropping below the uptime threshold for a defined measurement period. The remedies should be clearly articulated: cure periods (how long the market maker has to fix the issue after notification), penalty structures (fee reductions or credits for periods of non-compliance), and termination rights (your ability to exit the contract if breaches are repeated or severe).

What you want to avoid is an SLA that defines breach so narrowly that it's practically impossible to trigger. If the spread commitment is measured as an average over a full month rather than a rolling window, a market maker can let the spread blow out during volatile periods and compensate with artificially tight spreads during quiet hours — meeting the letter of the agreement while destroying the trading experience for your users.

1. Insist on rolling measurement windows — 4-hour or 24-hour rolling averages catch periods of poor performance that monthly averages smooth over.

2. Require transparent reporting — the SLA should mandate regular performance reports with auditable data, not self-reported metrics from the market maker's own systems.

3. Define escalation clearly — who contacts whom, through what channel, and with what response time when a breach is identified.

4. Build in a mutual review clause — a scheduled mid-contract review where both parties assess performance and adjust terms if needed.

5. Preserve your right to reclaim inventory — if the contract terminates, the SLA should specify a clear timeline for token return, ideally within 14 days.

The broader point is this: an SLA is a living document that governs a relationship, not a static checkbox. The market makers who deliver genuine value are the ones who welcome these provisions because they signal that you're serious about the engagement — and seriousness, in this corner of the industry, tends to attract the kind of alignment that makes both sides perform better.

---

Choosing a market maker for a Tier-2 exchange listing isn't a decision you make once and forget. It's an ongoing negotiation between your project's need for visibility and the market maker's need for profitability — and the SLA is the framework that holds that tension in balance. The best agreements don't eliminate friction; they make friction visible and manageable, so that when things drift — and they will drift — both parties have a shared language for course correction. The question worth sitting with isn't whether your next market maker will perform perfectly. It's whether the agreement you're signing gives you enough clarity to know when they're not — and enough leverage to do something about it before the sentiment in your community turns.