Authoritative Python tick timestamp semantics for the MetaQuotes demo service

[Burist Ch.]

Please clarify the current timestamp contract for XAUUSD on the MetaQuotes demonstration service when using the official MetaTrader5 Python package (5.0.6090).

The Python copy_ticks_from documentation describes received tick/bar times as UTC without an offset. The MQL5 Algo Book separately describes server time carried by ticks and shown in charts. The symbol_info_tick Python reference does not explicitly reconcile these two descriptions for its time and time_msc fields.

1. Are symbol_info_tick.time and time_msc true UTC Unix timestamps, or do they encode server-local wall-clock time relative to a nominal 1970 epoch? Please specify both fields.

2. If they encode server-local time, what is the current authoritative UTC offset and exact 2026 daylight-saving transition rule for this demo service's XAUUSD feed? Can the rule differ by instrument or by timestamp type?

3. What officially supported read-only source exposes this rule and its validity interval, without estimating the offset from tick age or assuming that each tick is fresh?

4. Do completed-bar timestamps, order/deal history query boundaries, and returned history timestamps use the same time basis? How should ambiguous/nonexistent DST times be handled?

The intended client is Demo-only and read-only. It rejects future/stale market data and must not subtract a guessed offset, widen freshness limits, or infer a valid tick from arrival time. An authoritative current reference or clarification from MetaQuotes staff would help establish a reviewed conversion contract. No trading access or account investigation is requested.

References:

https://www.mql5.com/en/docs/python_metatrader5/mt5symbolinfotick_py

https://www.mql5.com/en/docs/python_metatrader5/mt5copyticksfrom_py

https://www.mql5.com/en/book/common/timing/timing_local_server