Understanding Crossed and Stale Order Books: Implications for Market Making Bots

What Are Crossed and Stale Order Books?

Order books are the heartbeat of every crypto exchange, reflecting real-time buy (bid) and sell (ask) interest for each trading pair. For market makers, understanding the nuances of order book states—especially when they become "crossed" or "stale"—is essential for providing reliable liquidity and avoiding undesirable trades.

Crossed Order Books: Definition and Causes

A crossed order book occurs when the highest bid price equals or exceeds the lowest ask price. In a healthy market, the best bid is always lower than the best ask, creating a spread. When this relationship breaks down, the order book is said to be "crossed."

Example:

Here, the best bid ($100.1) is higher than the best ask ($100.0)—a crossed book.

Common causes include:

• Latency: Delays in order book updates, especially during high volatility.
• API inconsistencies: Exchange APIs may momentarily report outdated or conflicting data.
• Manual errors: Rarely, manual order entry or exchange bugs can create crossed states.

Stale Order Books: Definition and Risks

A stale order book is one where the data is outdated compared to the current market. This can happen if the exchange's data feed lags, if there's a network issue, or if the API fails to deliver up-to-date information.

Risks of acting on stale data:

• Placing orders at non-competitive prices
• Missing sudden market moves
• Increased risk of adverse selection (being picked off by faster traders)

Why Do Crossed and Stale Order Books Matter for Market Making Bots?

Market making bots rely on accurate, real-time order book data to place limit orders that both provide liquidity and manage risk. If a bot acts on crossed or stale data, it may:

• Place orders at illogical or uncompetitive prices
• Create or reinforce unhealthy market conditions
• Expose itself to unnecessary risk

For token projects, exchanges, and trading teams, ensuring that liquidity provision is based on valid, up-to-date data is critical for market integrity.

How Atlas LP Handles Crossed and Stale Order Books

Atlas LP is multi-tenant software designed to run a spot liquidity (market making) bot on users' own centralized exchange accounts. It takes several steps to ensure order book health and avoid problematic states:

1. Real-Time Order Book Checks

Each tick (default every 3 seconds, configurable from 0.5 seconds), Atlas LP reads the latest ticker and order book data via WebSocket stream or REST API. If the data is stale or the order book is crossed, the bot skips that tick entirely—no new orders are placed or canceled until valid data is available.

2. Strict Data Validation

Before starting, Atlas LP validates API connectivity by checking ticker, order book, symbol rules, balances, open orders, and recent trades. This reduces the risk of acting on incomplete or outdated information.

3. Conservative Order Placement

Atlas LP only places resting limit orders—never market orders. If the market has no valid quotes, the bot seeds one buy and one sell order around the base price, but only after confirming the book is not crossed or stale.

4. Responsive Order Management

On each valid tick, the bot computes the desired order ladder and only places or cancels orders as needed. If an order book anomaly is detected (crossed or stale), the bot waits for the next valid update before acting, minimizing the risk of erroneous trades.

5. Transparency and Alerts

All open orders, recent fills (with fees), balances, and bot events are visible in the console. Users can set up Telegram alerts to notify them if a running bot has had no fills for a chosen period, which may indicate persistent order book issues.

Best Practices for Market Makers

Whether you use Atlas LP or another market making solution, it's important to:

• Monitor order book health: Regularly check for crossed or stale states.
• Use robust API connections: Prefer WebSocket streams for lower latency, but have REST as a fallback.
• Avoid acting on questionable data: Never place or cancel orders if the order book is clearly invalid.
• Stay compliant: Only provide genuine liquidity with resting limit orders. Wash trading, self-trading, and volume manipulation are strictly prohibited.

Summary Table: Crossed vs. Stale Order Books

Why This Matters for Token Projects and Exchanges

Healthy order books are essential for price discovery, low slippage, and trader confidence. Automated market making bots must be designed to recognize and avoid acting on crossed or stale data to support sustainable liquidity.

Atlas LP’s approach—skipping ticks when data is invalid, validating API connections, and only placing limit orders—helps maintain order book integrity without exposing users to unnecessary risk.

For more on how Atlas LP supports robust spot liquidity provision, visit [/liquidity-bot].

Atlas LP does not guarantee returns, prices, volume or listings.