Historical Data

[oreoluwadavid]

Historical Data

Goal

Frequency and source of historical data for practice mode (need to download candles before running dry‑run or implement a mock data generator).

Background / Motivation

This item was captured in the Wayfinder map under “Not yet specified” to clarify a design decision needed for the pyquotex_reimagined trader.

Acceptance Criteria (Given/When/Then)

• Given the trader is about to start in live mode,
  When the credential source is determined,
  Then the application loads credentials from the agreed location without manual intervention.
• Given the OTP mechanism decision is made,
  When the login flow runs,
  Then the OTP is obtained via the chosen method (integrated or external) and the session is established.
• Given historical data is required for practice mode,
  When the runner starts,
  Then sufficient candle data is available (either downloaded or mocked) to allow the strategy to generate signals.
• Given strategy parameters and risk‑management settings need to be tuned for live deployment,
  When the trader is configured for live,
  Then the settings are loaded from a version‑controlled configuration file and can be overridden via environment variables.

Open Questions

• Should we encrypt credentials at rest?
• What is the retry policy for failed OTP requests?
• How far back should we download candles for practice (e.g., 7 days)?
• Which risk‑management parameters (max lot size, stop‑loss, take‑profit) are exposed externally?

References

• Wayfinder map: https://github.com/oreoluwadavid/pyquotex_reimagined/blob/main/map_body.txt

---

This issue was automatically created from the Wayfinder map.

[oreoluwadavid]

See the Wayfinder map for context: https://github.com/cleitonleonel/pyquotex/blob/main/map_body.txt

[oreoluwadavid]

PR #102 has been opened to implement this: #102