Managing Multiple Exchange Accounts: Best Practices for Crypto Market Makers

Introduction

For crypto market makers, operating across several exchange accounts is often essential for providing liquidity, managing risk, and supporting multiple trading pairs. However, juggling bots, API keys, and order management on different platforms introduces operational and security challenges. This guide outlines practical best practices for efficiently and securely managing multiple exchange accounts as a market maker, with a focus on spot trading using tools like Atlas LP.

Why Manage Multiple Exchange Accounts?

Market makers may need to operate on several exchanges and accounts for reasons such as:

• Supporting multiple token listings across different venues.
• Segmenting risk by using separate accounts for different strategies or clients.
• Complying with exchange-specific requirements or regional restrictions.
• Optimizing liquidity provision by targeting varied market conditions and user bases.

Managing these accounts efficiently is crucial to maintain reliable liquidity and minimize operational risks.

Setting Up: Account and API Key Management

1. Use Unique API Keys Per Account and Symbol

When using software like Atlas LP, each exchange account should have its own set of API keys. For each trading symbol (pair), create a dedicated bot instance. This approach:

• Simplifies tracking of open orders and fills per account and symbol.
• Limits the impact of a compromised key to a single account.
• Supports granular control over permissions and risk exposure.

2. Restrict API Permissions

Always generate API keys with the minimum permissions required. For spot market making on Atlas LP-supported exchanges, only enable:

• Read access (to fetch balances, open orders, trades, etc.)
• Spot trading permission (to place/cancel limit orders)

Never enable withdrawal permissions. Atlas LP never asks for withdrawal access and will not function if such permission is required.

3. Secure Storage and Encryption

API keys are sensitive credentials. Atlas LP encrypts API keys and secrets with AES-256-GCM before storage, and only decrypts them for the worker that communicates with the exchange. Even so, you should:

• Store backup copies of your API keys in a secure, offline location.
• Rotate API keys periodically, especially after personnel changes or suspected compromise.
• Never share API keys via insecure channels.

Operational Best Practices for Multi-Account Market Making

1. Validate Settings Before Launch

Each bot instance should have its settings validated before starting. Atlas LP performs checks on:

• Ticker and order book data
• Symbol rules (min/max order size, notional requirements)
• Balances, open orders, and recent trades

This prevents misconfigured bots from placing invalid or rejected orders.

2. Monitor Open Orders and Fills

Managing multiple accounts means more open orders to track. Use the bot console to:

• View open orders, recent fills (with fees), and balances for each account and symbol.
• Cancel individual or all open orders when needed.
• Stop a bot to halt new order placement while keeping existing orders visible for management.

3. Use Alerts for Inactivity

Atlas LP can send Telegram alerts if a bot has no fills for a user-defined period. This helps you quickly identify issues such as:

• Market inactivity
• API connection problems
• Symbol delistings or trading halts

Prompt response to alerts ensures continuous liquidity provision.

4. Regularly Review Daily Snapshots

Atlas LP records a daily snapshot of account asset value. Reviewing these snapshots helps you:

• Track performance and inventory changes per account
• Detect anomalies or unexpected asset movements
• Maintain accurate records for compliance and reporting

Security Considerations

1. Principle of Least Privilege

Never grant more permissions than necessary. API keys should be limited to the exact functions required for spot market making. This reduces the risk of unauthorized actions.

2. Isolate Accounts by Strategy or Team

If possible, use separate exchange accounts for different strategies, teams, or clients. This compartmentalizes risk and simplifies auditing.

3. Monitor for Credential Errors

Atlas LP will stop a bot and report an error if exchange credentials are rejected. Investigate such errors immediately to rule out issues like key expiration, permission changes, or potential compromise.

4. Stay Updated on Exchange Rules

Exchange symbol rules (such as minimum order size or notional value) can change. Regularly review these rules for each account and symbol to ensure bot settings remain compliant.

Practical Example: Managing Bots Across Three Exchanges

Suppose your team needs to provide liquidity for the same token on Binance, LBank, and CoinW. Here’s a streamlined workflow:

1. Create an account on each exchange and generate API keys with read and spot trading permissions only.
2. Register each exchange account in Atlas LP. For each account, add a bot for the desired trading symbol.
3. Configure bot settings (spread, order size, tick interval, etc.) per symbol, ensuring they meet each exchange’s requirements.
4. Validate settings using Atlas LP’s built-in checks.
5. Monitor all bots via the console, using Telegram alerts for inactivity and reviewing daily snapshots for each account.
6. Cancel or adjust open orders as needed, and rotate API keys periodically for security.

This approach allows your team to maintain a consistent liquidity presence while minimizing operational risk.

Avoiding Common Pitfalls

• Do not reuse API keys across accounts or symbols. This can lead to confusion and security issues.
• Do not enable withdrawal permissions. Atlas LP does not require them and will not use them.
• Do not ignore exchange updates. Symbol rules and API endpoints may change, so stay informed.
• Do not attempt to manipulate volume or prices. Genuine market making means placing resting limit orders that any participant can trade against. Wash trading, self-trading, or volume manipulation is strictly prohibited.

Conclusion

Managing multiple exchange accounts as a crypto market maker requires careful attention to operational detail and security. By following best practices—such as using unique API keys, restricting permissions, validating settings, and monitoring activity—you can efficiently provide liquidity across venues while minimizing risk.

Atlas LP supports multi-account management for spot market making on several leading exchanges, with robust security and operational controls. Remember, Atlas LP does not guarantee returns, prices, volume, or listings.