One of the most underappreciated features of crypto markets is that they never close. No weekends, no holidays, no overnight gaps. LMEX runs 24/7/365 just like every other crypto exchange — but the implications for algo traders are more significant than most people realise.
This article walks through what 24/7 trading actually means in practice, how it changes algorithmic strategies, and the operational gotchas of running continuous systems.
In traditional markets, the trading day ends at 4pm. The market reopens the next morning. Anything that happens overnight gets priced in at the open via a gap. Algos rest. Humans sleep. Risk management is built around discrete trading sessions.
Crypto is different. There's no close. Price discovery happens continuously, including at 3am on a Sunday. This has several practical implications:
**No overnight gaps to worry about.** A position you hold tonight will not gap 5% against you tomorrow morning. Whatever happens overnight, you see continuously. Stops, take-profits, and other automated exits work without weird open-of-day surprises.
**Your bot has to handle continuous operation.** A "9 to 5" bot that runs only during business hours misses 67% of all trading. Continuous bots must handle reconnection, state recovery, scheduled maintenance windows, and exchange API hiccups gracefully.
**Liquidity varies dramatically by time of day.** Asian hours (00:00-09:00 UTC), European hours (07:00-16:00 UTC), and American hours (13:00-22:00 UTC) each have different liquidity profiles. Weekends are usually thinner than weekdays. A market that has 1mm of depth at the spread on Tuesday afternoon might have 200k on Saturday at 3am.
**Funding rate cadence runs all the time.** LMEX settles funding every 8 hours regardless of weekday or weekend. Strategies that key off funding need to account for weekend settlements like any other.
Several strategy adaptations are specific to the 24/7 environment:
**Time-of-day filters become important.** Liquidity varies enough that the same strategy can be profitable during US hours and unprofitable during weekend lulls. Add a time filter to your bot: only take signals when liquidity is above some threshold (measured by spread width or order book depth).
**Weekend volatility patterns differ.** Saturdays and Sundays tend to see lower volume but occasional sharp spikes — a single large player can move price more easily when fewer participants are active. Mean-reversion strategies sometimes work better; trend strategies sometimes whipsaw more. Backtest weekend behaviour separately.
**Continuous backtesting.** With no market close, there's no "end of day" to mark to market. Continuous PnL tracking is essential. Most retail backtest frameworks assume discrete trading sessions; adapt them or use frameworks built for crypto.
**Always-on monitoring.** Your bot can break at 3am on a Sunday. If you only check it during business hours, you might lose money for 36 hours before noticing. Set up alerts that ping you regardless of the day or hour when something goes wrong.
Running a 24/7 trading system is genuinely harder than running a discrete-session one. A few things that bite people:
**Server reboots happen.** OS updates, kernel patches, cloud provider maintenance. Plan for reboots and have your bot resume cleanly from saved state. Stateless bots are easier here; stateful bots need durable storage for open positions, pending orders, and recent fills.
**API key rotation while the bot is running.** API keys eventually need rotation. A bot designed for continuous operation needs a way to swap credentials without restarting. Most retail bots don't have this and require manual intervention during key rotation.
**Time synchronisation.** Many exchange APIs require timestamps within a few seconds of the exchange's clock. If your server's clock drifts, requests fail. Run NTP. Check it weekly.
**Logging discipline.** Continuous bots generate continuous logs. Without good logging hygiene (rotation, structured format, severity levels), you accumulate gigabytes of unsearchable noise. When something breaks, you need to find the relevant event among millions of log lines.
**Memory leaks.** A bot that runs for a week without issues might develop memory leaks that cause crashes after a month. Long-running processes need monitoring for memory consumption and periodic restarts (ideally graceful, where positions are preserved).
Algo traders sometimes treat 24/7 markets as an excuse to never sleep. This is a mistake.
A trader who can't disconnect from their bot for 12 hours has built a system that requires constant human supervision. That's not a properly designed system. It's a high-frequency manual operation pretending to be automated.
Well-designed bots run unattended for days at a time. The human reviews performance, adjusts parameters, and handles exceptional situations during normal waking hours. The bot operates within bounds the human has defined.
If you find yourself checking your bot at 2am because you can't sleep without knowing what's happening, the issue is either:
The first is a technical fix. The second is a sizing fix. The third is a psychological problem that bigger leverage will only make worse.
LMEX occasionally runs maintenance windows, typically scheduled and announced in advance. During maintenance:
Your bot needs to know about scheduled maintenance and adjust behaviour accordingly. Pause new entries before maintenance starts. Resume after the all-clear. Don't try to place orders during the window.
LMEX publishes maintenance schedules through their API and announcement channels. Subscribe and parse them programmatically.
Q: Should I trade differently on weekends?
Probably yes. Many strategies show different return profiles on weekends due to lower liquidity. Test your strategy separately on weekday and weekend data. If weekend performance is significantly worse, add a weekend filter that reduces position sizing or pauses entirely.
Q: How do I handle daylight saving time?
Use UTC for all timestamps in your bot. Convert to local time only for display. Crypto exchanges operate in UTC; matching their timezone removes a whole class of bugs. If you write a 9am-5pm filter, write it in your local time zone offset from UTC.
Q: What's the right way to handle continuous logging?
Use a logging library that supports rotation (logrotate, Python's RotatingFileHandler, etc.). Cap log size at something reasonable like 100MB per day. Use structured logging (JSON) so you can grep and parse later. Set up cloud logging (CloudWatch, Datadog) for centralised search across multiple bot instances.
Q: How often should I restart my bot proactively?
Weekly restarts are a reasonable cadence for most retail bots. This catches memory leaks, refreshes connections, and ensures recovery code actually works. Schedule restarts at known-low-volatility times. More frequent restarts add stability cost; less frequent makes recovery riskier when it eventually fails.