Cj dZddlZejddZdZejddZejdd Zd Zejd d Z e ejd dZ ejddZ ejddZ ejddZdS)u, Configuration for the TD Slope params server. DELIBERATE DESIGN CHOICE: this service uses its OWN shared secret, separate from the license-validation secret already embedded in LicenseValidator.mqh. Reasons: 1. Blast radius — if this secret ever leaks (e.g. a sloppy log line, a compromised dev machine), it only exposes the params feed, not the license-validation channel that gates whether the EA runs at all. Keeping them separate means a leak here can't be used to forge VALID license responses, and vice versa. 2. This endpoint will eventually carry walk-forward parameters — arguably more commercially sensitive (the actual edge) than the license check itself. Worth not entangling its security with a channel that already exists and works. 3. If you'd rather reuse the existing license secret instead, that's possible too — the existing secret CAN be recovered by replaying LicenseValidator.mqh's exact XOR-decode routine against the _LV_OS/_LV_XK byte arrays already in that file. Just say so and I'll do that instead of minting a new one. Defaulting to a new, separate secret unless told otherwise. Set real values via environment variables in production — never commit real secrets to source control. The values below are placeholders. NTD_PARAMS_SHARED_SECRET5REPLACE_ME_WITH_A_REAL_RANDOM_SECRET_BEFORE_DEPLOYINGi,TD_PARAMS_DATA_DIRz ./data/paramsTD_PARAMS_SYMBOLS_PATHz./data/symbol_synonyms.jsonTD_PARAMS_DB_HOSTz 127.0.0.1TD_PARAMS_DB_PORT3306TD_PARAMS_DB_USER paramsreaderTD_PARAMS_DB_PASS CHANGE_METD_PARAMS_DB_NAMETradeSimulatorLicense)__doc__osenvirongetPARAMS_SHARED_SECRETMAX_TIMESTAMP_SKEW_SECONDSPARAMS_DATA_DIRSYMBOL_SYNONYMS_PATHMAX_PARAMS_AGE_DAYSLICENSE_DB_HOSTintLICENSE_DB_PORTLICENSE_DB_USERLICENSE_DB_PASSLICENSE_DB_NAME/wd/td-params-server/config.pyr#s6 z~~;! *..!5GGz~~;*..!4kBB#bjnn%8&AABB*..!4nEE*..!4kBB*..!46MNNr!