Liquidity
Seeding Order Books: The First Steps for New Token Pairs
Learn how seeding initial buy and sell orders helps establish functional order books for new token pairs and supports organic trading activity.
Read more →Liquidity
Learn how to design effective spot-only liquidity strategies for centralized exchanges, focusing on essential parameters, common pitfalls, and practical tips for token projects and trading teams.
Published
Effective liquidity on spot markets is a cornerstone for healthy token ecosystems and active trading venues. For token projects, exchanges, and trading teams, building a spot-only liquidity strategy requires careful consideration of order placement, risk management, and exchange-specific constraints. This article explores the essential parameters to configure, common pitfalls to avoid, and practical advice for designing a robust spot market making approach using tools like Atlas LP.
Spot market making involves posting limit orders on centralized exchanges, allowing any market participant to trade against them. Unlike futures or margin trading, spot-only strategies deal strictly with asset-for-asset exchanges (e.g., BTC/USDT) without leverage or derivatives. This means:
When configuring a spot-only liquidity bot such as Atlas LP, several parameters directly influence the quality and risk profile of your strategy. Here’s a breakdown of the most important ones:
The spread defines how far your buy and sell orders are placed from your chosen base price. In Atlas LP, spreads are set in basis points (bps), with a minimum width of 40 bps. Tighter spreads can attract more trades but increase the risk of adverse selection, while wider spreads may reduce fill rates but offer more protection against volatility.
Your base price is the anchor around which orders are placed. This could be a moving average, last traded price, or a manually chosen level. The choice impacts both the visibility of your orders and your exposure to price movements.
Atlas LP allows you to specify the number of bid and ask levels, with customizable spacing between each. More levels mean deeper liquidity provision, but also require more capital and careful sizing to avoid overexposure.
Order sizes can be randomized between a minimum and maximum, but must meet the exchange’s minimum quantity and notional requirements. Too-small orders may not be accepted by the exchange, while too-large orders increase inventory risk.
The tick interval determines how often the bot checks the market and updates orders. Atlas LP supports intervals from 0.5 seconds (default is 3 seconds). Faster intervals can help maintain tight spreads but may increase API usage and risk of rate limiting.
Nested bands allow you to vary spreads or liquidity depth by time of day or day of week, adapting to expected changes in market activity.
Each exchange has its own symbol rules, minimum order sizes, and notional requirements. Bots like Atlas LP validate these before starting, but manual configuration errors can still occur.
Market making exposes you to inventory swings as your orders are filled. Without careful monitoring, you may end up holding too much of one asset, especially in volatile markets.
Placing orders too close to the market (ultra-tight spreads) can lead to rapid inventory turnover and higher exposure to adverse price moves.
Bots must avoid acting on outdated or inconsistent order book data. Atlas LP skips ticks if data is stale or crossed, but network issues or exchange outages can still pose risks.
Incorrect API key permissions can prevent the bot from operating, while over-permissive keys (e.g., withdrawal enabled) increase security risks. Atlas LP requires only read and spot trading permissions, and never asks for withdrawal access.
Atlas LP supports spot market making on the following centralized exchanges:
| Exchange | Spot Only |
|---|---|
| Binance | Yes |
| DigiFinex | Yes |
| LBank | Yes |
| BingX | Yes |
| XT.com | Yes |
| Biconomy | Yes |
| Toobit | Yes |
| CoinW | Yes |
| P2B | Yes |
| Azbit | Yes |
| Dex-Trade | Yes |
Building an effective spot-only liquidity strategy requires a deep understanding of order book dynamics, careful parameter selection, and ongoing monitoring. By focusing on these key parameters and avoiding common pitfalls, token projects and trading teams can provide real, transparent liquidity that benefits both the project and its trading community.
Atlas LP does not guarantee returns, prices, trading volume, or exchange listings.
Crypto trading involves risk. Atlas LP is software for placing and managing limit orders; it does not guarantee returns, prices, volume or listings. Follow the rules of each exchange and applicable law.
Spot strategies involve posting limit orders for direct asset-for-asset trades (e.g., BTC/USDT) without leverage. Futures strategies involve contracts and may use leverage or margin, which are not supported by Atlas LP.
Monitor your balances and fills regularly, use moderate spreads, and adjust your order sizes and base price as needed to maintain a balanced inventory.
Atlas LP only needs to read account data and place/cancel spot limit orders. Withdrawal permission is never required, reducing security risks.
Atlas LP performs detailed API checks and stops the bot with an error status if credentials are invalid or rejected by the exchange.
No. Genuine market making means posting limit orders that any participant can trade against. Wash trading, self-trading, or volume manipulation are strictly prohibited.
Liquidity
Learn how seeding initial buy and sell orders helps establish functional order books for new token pairs and supports organic trading activity.
Read more →Liquidity
Learn what exchange liquidity provision means, why it matters for crypto markets, and how genuine market making works without volume manipulation.
Read more →Atlas LP
Explore the daily workflow of a spot liquidity bot, from real-time ticker reads to order placement and daily asset snapshots, and learn how Atlas LP manages genuine market making.
Read more →Connect an exchange API key, set your spread band and order levels, and monitor orders, fills and balances from one console.