When US daylight saving time ended on November 1, 2026, the Eastern times on our results log, in results.csv and in the Eastern-time fields of /api/record started reading one hour late. Our code used a fixed summer offset instead of real New York time. No result, price, win, loss or count changed, only the clock label. It is fixed: every time on those pages is now New York time, standard or daylight as of that moment.
Every row in the log carries the time the alert fired and the time it settled, labeled ET. Our code made those labels by setting the clock a fixed four hours behind UTC, which matches Eastern time only while daylight saving is on. Since 2:00 AM on November 1, New York has been five hours behind UTC, so every new row showed a time one hour later than the real one.
An example from the log on November 5: the window KXBTC15M-26NOV050845-45 closed at 8:45 AM Eastern (Kalshi's ticker carries the close time: 26NOV05, 08:45). Our row said the alert fired at 9:42 AM ET and settled at 9:45 AM ET. The right times are 8:42 AM and 8:45 AM.
As of November 5, 2026 at 8:42 AM ET, 365 of the 18,633 rows in results.csv had the wrong time: 343 BTC, 19 NBA and 3 NFL. No MLB row was affected. Every row before November 1 was right, because the log starts after daylight saving began on March 8, 2026 (the first BTC row is from March 24, the first sports row from April 10).
The time is how you match a row in our log to the market on Kalshi, to the alert you received on Telegram, or to a Bitcoin chart. An hour off breaks that check, and checking us is the point of publishing the log. Nothing about how the record is counted changed: the live record is still 91.0% won across 13,470 graded alerts at a 91.6 cent average entry price, which is below breakeven before Kalshi's fee and further below after it.
date_et and settled_at columns of results.csv, and first_signal_et and data_through_et in /api/record now use America/New_York time, EST or EDT as of each moment. The rows since November 1 now show the right hour.signaled_at_utc and settled_at_utc are added at the end of every row, the same moments in UTC. They never shift with daylight saving and settle the hour that repeats every November. The existing columns keep their names and order.data_through_utc in /api/record was correct throughout: it was worked out with the same fixed offset that made the label, so the error cancelled out.If you downloaded results.csv after November 1, download it again, or subtract one hour from date_et and settled_at on rows dated November 1, 2026 or later. Spotted something else that looks wrong? Email [email protected].
No. Only the clock time printed beside each row was wrong. Every outcome, entry price, win, loss, exclusion and count is exactly as it was.
Rows timed after 2:00 AM Eastern on November 1, 2026, when daylight saving time ended. As of November 5, 2026 at 8:42 AM ET that was 365 rows of 18,633: 343 BTC, 19 NBA and 3 NFL. Every earlier row was right, because the whole log dates from after daylight saving began on March 8, 2026.
Download it again, or subtract one hour from date_et and settled_at on rows dated November 1, 2026 or later. The file now also has signaled_at_utc and settled_at_utc columns, which never change with daylight saving.
We read results.csv on November 5, 2026 at 8:42 AM ET and counted rows whose signal time fell after 2:00 AM Eastern on November 1, 2026, the moment daylight saving time ended. The old labels were always exactly four hours behind UTC, so each one converts back to its true moment without guesswork. DegenHedge is independent and is not affiliated with or endorsed by Kalshi.
Related: the results log · the read-only API · how to verify a signal service · our earlier correction
Free to read, free to check. Want to watch our calls get graded before paying anything? Follow the free @DegenHedgeProof Telegram channel; the paid feed is optional.
Every signal in our BTC 15-minute feed goes into a public results log and a downloadable CSV, graded against Kalshi's official result, losses included, with nothing pulled. The same record is available as JSON from our read-only API.
This is a free trial that becomes an automatically renewing subscription. Eligible new customers receive a 30-day trial with a payment card and $0 due today. Returning trial users see $4.99 due today before checkout. At the end of it your card is charged $4.99 and then $4.99 every month until you cancel. Cancel any time before the trial ends and you pay nothing: use your account page, send /manage in the bot, or email [email protected]. Cancelling later stops future renewals at the end of the current paid month and does not refund it. No refunds except as required by law. By starting a trial you authorize these recurring charges and agree to the Terms and Privacy Policy. Signals are informational and for entertainment only, are not financial or betting advice, and any single signal can lose 100% of your stake. Must be 18+ (some platforms require 21+). If gambling is a problem for you, call 1-800-GAMBLER.
These are 15-minute binary prediction-market contracts. Any single window can lose 100% of your stake. They settle on a 60-second index average, not on the exchange chart you may be watching. At high prices a loss costs many times what a win pays, and Kalshi's fee raises the win rate you need above the price. Nothing on this page is financial, investment, or betting advice.
Past performance does not guarantee future results. Trade only with money you can afford to lose. Must be 18+ or of legal age where you live. If gambling is a problem for you, call 1-800-GAMBLER.