MetaQuotes-Demo XAUUSD — applicable contract and cost settings for October 2-9, 2026

New comment
We are validating an existing private, offline XAUUSD research archive from MetaQuotes-Demo. We need source-backed historical economics for a USD-denominated hedging demo product, before any historical net result can be accepted.

The requested source-label period was 2026-10-02 00:00 inclusive through 2026-10-10 00:00 exclusive. Under our separately reviewed EET/DST interpretation, its bounded UTC envelope is 2026-10-01 21:00 inclusive through 2026-10-09 21:00 exclusive. Please state the time basis and exact effective interval of any economic settings you provide. Data dates do not by themselves define the contract's validity.

Our current observations were collected October 13-14 with terminal build 6230; the October 13 Python binding was 5.0.6090. The current product is USD hedging demo, leverage 1:200. Please identify the applicable public product/group or a non-secret group alias and whether its configuration applied during the historical window. We do not assume that the observed account itself existed then, nor that current settings applied then. Please do not request or publish account credentials. If further account context is essential, first identify the minimal non-secret fields needed and a supported private route.

Could the responsible service owner provide any archived symbol/account-group configuration, dated schedule, change log or written confirmation addressing:

1. **Contract and execution basis.** XAUUSD contract size, point/tick size, digits, base/profit/margin currencies; lot min/max/step/limit; stop/freeze distances; trade, order, filling and execution modes. List changes inside the interval, or confirm a specific unchanged effective interval with its source.
2. **Tick-value contradiction.** Current metadata and Specification both report tick value 0.1, contract 100 and tick size 0.01. Current OrderCalcProfit controls return +/-USD1 for one lot over +/-0.01 in all buy/sell directions. Please explain the intended economic/calculation basis, whether the metadata is erroneous or uses another unit, and which basis applied to the historical interval. Please preserve rather than overwrite the conflicting observations.
3. **Commission and separate fees.** The October 14 native SymbolInfoCommissions calls returned 0 with no API error for XAUUSD and four configured FX symbols; existing account history contains funding only. These observations do not establish historical zero cost. Please provide the date-applicable account-group tariff or an explicit statement of zero applicable charges, including commission, minimum/maximum charges, tiers, currency/conversion, direction/entry/exit rules, daily/monthly/account-level fees and posting timing. Distinguish no symbol commission rules from no charges of any relevant kind.
4. **Financing.** Current gold observations are points mode, long -12.6, short -4.6, Wednesday triple. Please provide date-applicable long/short rates, units and conversion/rounding basis, all seven weekday multipliers and holiday adjustments. State the exact server-time liability cutoff separately from booking time; treatment of entry/exit exactly at cutoff, positions partially closed across cutoff and late postings; and any DST policy affecting that cutoff. A quote-session close alone does not answer rollover liability.
5. **Margin.** Provide historical leverage and any volume/notional/equity tiers, symbol calculation mode, per-side initial and maintenance rates, hedged larger-leg or fixed hedged treatment, pending-order treatment and any scheduled changes. Please identify whether fixed leverage represents this product for the intended sizes or where it does not.
6. **Sessions and exceptions.** Provide the complete dated quote and trade session schedules, timezone, inclusivity rules and holiday/exception closures for the requested interval, including Friday/weekend boundaries. Current Mon-Fri 00:00-23:00 tables do not certify historical closures or explain all historical gaps.

For every supplied record, please include its issuer/owner, publication or configuration version, effective start/end timestamps, symbol and account-product/group scope, and any known corrections. An original record published before the period or an explicit responsible-owner retrospective confirmation would be useful. Retrieval timestamps are not substitutes for effective dates.

If records are unavailable or outside the service's supported scope, please distinguish which fields are unavailable, unknown, retained elsewhere or never historically versioned, and identify any supported next source. We are asking for technical configuration evidence, not financial advice, a trade, an account change, credentials, a new account or a paid-data purchase.

What is this about, in 1 sentence ?

Sorry, but I'm not going to read all this AI slop.

Alain Verleyen #:

What is this about, in 1 sentence ?

Sorry, but I'm not going to read all this AI slop.

Al these topics about "We have become an AI tool" instead of "We use AI as a tool" is getting out of hand. To me it comes accross as a way to waste human recoures.
Enrique Dangeroux #:
Al these topics about "We have become an AI tool" instead of "We use AI as a tool" is getting out of hand. To me it comes accross as a way to waste human recoures.

Yes I do agree. And it will become worst and worst I guess.

I take me a lot more time to analyze and check bug "reports" when generated by an AI, even when it's a actual bug. What a hell !

New comment