A 16-second clock drift falsely tripped my trading bot's kill switch. A postmortem.

DEV Community·6 points·wataru_suda_d295dab9cca4f·10 days ago·dev.to

My PC clock ran 16 seconds ahead of the exchange. Signature validation failed, a "helpful" fallback computed equity from a paper balance, and the bot declared a 58% drawdown. No orders were sent. Here is the chain of events and the two fixes.

Read the full article at dev.to →

#postmortem #clock #bots #drift #tripped #trading #falsely #kill

Related stories

Show HN: I wrote a book on trading psychology, Daoism, and quant riskbayrising.dev
Hacker News · 2 points · 5 days ago
Show HN: Jeeva – A modular trading engine for mid-frequency trading using Jevgithub.com
Hacker News · 1 points · 10 days ago
Show HN: StarSkirmish, an arena where LLMs create StarCraft Brood War botsstarskirmish.com
Hacker News · 3 points · 4 days ago
Show HN: A crypto trading demo using WebGPU and QuestDBscitrader.io
Hacker News · 3 points · about 18 hours ago
Show HN: Wallstreetclaws.com – Create AI Agents for Tradingwallstreetclaws.com
Hacker News · 2 points · 5 days ago
Show HN: Corral – Kill every command your agent startsgithub.com
Hacker News · 12 points · 2 days ago

Related topics

ddos6 outage13 clock6 crates5 io28 broken17 hey8