Prop Price Comparisons: Align Timestamp Units Before the Spread
Two price records can look simultaneous while using different timestamp units or offsets. Establish what each time field means before calculating a spread. Correct arithmetic on mismatched observations still answers the wrong question.
Explore this site’s existing research resource
Keep the original time field
Record the documented unit, timezone or offset, precision and event meaning. An integer in milliseconds needs division by 1,000 before comparison with a seconds field. A local clock without its date and offset cannot identify a unique instant around every seasonal change.
For a Singapore journal, 23 October 2026 at 16:00:00+08:00 and 08:00:00Z refer to the same instant. Preserve both full representations. Do not join by the displayed hour or strip the offset before matching.
Check precision before a fictional spread
Suppose source A records price 100.00 at 08:00:00.100Z and source B records 100.03 at 16:00:00.350+08:00. Their observations differ by 250 milliseconds. The numerical price difference is 0.03, with that observation gap explicitly attached.
If source B reports only whole seconds, its fractional timing is unknown. Do not invent .000 precision or describe a zero-latency comparison. The products, side, currency and quantity basis also need to match before interpreting the price difference.
| Record | Full supplied instant | Price or conclusion |
|---|---|---|
| A | 2026-10-23T08:00:00.100Z | 100.00 |
| B | 2026-10-23T16:00:00.350+08:00 | 100.03 |
| Observation gap | B instant minus A instant | 250 milliseconds |
| Numerical difference | 100.03 − 100.00 | 0.03 with timing scope retained |
Do not substitute the quote for account evidence
This site’s existing timestamp resource remains the detailed companion. A matched quote comparison does not establish that an order filled, that the quoted size was available or that a provider used that price in its account valuation.
HashHedge’s current account and instrument conditions require their own review. The optional sponsored link is not an arbitrage invitation or a latency guarantee. The worksheet sends no requests to an exchange and measures no real execution or account result.
Sources and rule dates
- HashHedge: daily loss calculation
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established. - HashHedge: instruments and position limits
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established. - HashHedge: terms and conditions
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established.