DST phantom window creates a 21-day execution risk for epoch timestamp logic #10
Description
Hey — spotted something worth flagging while looking at the slug builder logic.
The bot constructs market slugs using epoch timestamps like btc-updown-5m-{epoch_ts}. That part is fine. But if any part of the execution pipeline uses local time or hardcoded UTC offsets to determine trading windows or market open/close boundaries, there's a 21-day vulnerability coming up.
US DST shifted March 8. UK/EU doesn't shift until March 29. For three weeks, any bot using fixed UTC offsets for exchange-correlated timing will be off by exactly 1 hour.
For pure prediction markets this matters less — but if the bot cross-references traditional exchange hours anywhere (for signal generation, reference prices from Coinbase/Binance, or risk windows), that offset is currently wrong.
Built a demo that shows the failure mode and the fix: https://github.com/LembaGang/dst-exploit-demo
Runs in under 5 seconds. Shows exactly where bots break during DST transitions.
Worth a look before March 29 when EU clocks change and the offset resets.