A local clock label is not always a unique instant. NIST explains that U.S. daylight saving time ends on the first Sunday in November at 2 a.m. local time, when clocks move back to 1 a.m. In places observing that transition, the repeated hour makes a bare label such as 01:30 incomplete for a precise expiry record. NIST: Local time FAQs and U.S. daylight saving transitions
Follow the evidence
Trace how the event could reach markets, then inspect a competing explanation.
Compare explanations
Switch lenses to see what each account explains—and what remains uncertain.
WFN analysis: imagine a hypothetical contract whose outcome depends on a price at 01:30 New York time on that transition date. If the specification omits an offset or a rule resolving the repeated hour, the label alone leaves two possible instants in this example. The correct interpretation must come from the documented contract and venue conventions. A screenshot taken at the first occurrence of 01:30 is not evidence about the price an hour later. A dispute record should preserve the timestamp, timezone, offset, source and stated expiry rule. The same discipline applies to stored data: two rows with identical local labels can refer to different observations when their offsets differ. The opposite seasonal change presents a different issue: some local times are skipped when clocks advance. A system that stores only local wall-clock text can therefore lose information at both types of transition. A precise record retains an unambiguous instant alongside the human-readable local display and the convention used to produce it.
WFN analysis: imagine a hypothetical contract whose outcome depends on a price at 01:30 New York time on that transition date. If the specification omits an offset or a rule resolving the repeated hour, the label alone leaves two possible instants in this example. The correct interpretation must come from the documented contract and venue conventions. A screenshot taken at the first occurrence of 01:30 is not evidence about the price an hour later. A dispute record should preserve the timestamp, timezone, offset, source and stated expiry rule. The same discipline applies to stored data: two rows with identical local labels can refer to different observations when their offsets differ. The opposite seasonal change presents a different issue: some local times are skipped when clocks advance. A system that stores only local wall-clock text can therefore lose information at both types of transition. A precise record retains an unambiguous instant alongside the human-readable local display and the convention used to produce it.
For a contract review, identify the designated timezone, the authoritative price source and the treatment of the exact expiry boundary. Equality with a threshold, a late observation or an unavailable quote should be handled by the actual specification. The daylight-saving conversion does not invent those clauses or decide an unnamed product’s outcome. For the audit trail, retain a UTC timestamp, the displayed local timestamp and its numerical offset. If a platform shows a countdown, compare its referenced expiry instant with the written terms before drawing a conclusion from the display. This article explains a timing ambiguity and provides no live expiry, price observation or allegation that a particular platform manipulated its clock.
The rule and the 2026 calendar example
Under the NIST-described rule, the 2026 autumn transition falls on 1 November. For the America/New_York timezone, an illustrative 01:30 timestamp before the clock change carries UTC−04:00; the repeated 01:30 afterward carries UTC−05:00. Those labels correspond to 05:30 UTC and 06:30 UTC respectively. The conversions are calendar arithmetic, not a reported contract schedule.
NIST’s guidance concerns the U.S. rule and notes that daylight saving practice has exceptions. Other jurisdictions can use different transition dates or rules. The time convention named in the actual contract therefore matters; the U.S. calendar example should not be imposed on an unspecified venue or foreign settlement source. NIST: Local time FAQs and U.S. daylight saving transitions
One hour can change the proposition being tested
WFN analysis: imagine a hypothetical contract whose outcome depends on a price at 01:30 New York time on that transition date. If the specification omits an offset or a rule resolving the repeated hour, the label alone leaves two possible instants in this example. The correct interpretation must come from the documented contract and venue conventions.
A screenshot taken at the first occurrence of 01:30 is not evidence about the price an hour later. A dispute record should preserve the timestamp, timezone, offset, source and stated expiry rule. The same discipline applies to stored data: two rows with identical local labels can refer to different observations when their offsets differ.
The opposite seasonal change presents a different issue: some local times are skipped when clocks advance. A system that stores only local wall-clock text can therefore lose information at both types of transition. A precise record retains an unambiguous instant alongside the human-readable local display and the convention used to produce it.
Resolve the time and the settlement boundary separately
For a contract review, identify the designated timezone, the authoritative price source and the treatment of the exact expiry boundary. Equality with a threshold, a late observation or an unavailable quote should be handled by the actual specification. The daylight-saving conversion does not invent those clauses or decide an unnamed product’s outcome.
For the audit trail, retain a UTC timestamp, the displayed local timestamp and its numerical offset. If a platform shows a countdown, compare its referenced expiry instant with the written terms before drawing a conclusion from the display. This article explains a timing ambiguity and provides no live expiry, price observation or allegation that a particular platform manipulated its clock.