-
Notifications
You must be signed in to change notification settings - Fork 0
Safety
kgorlov edited this page May 13, 2026
·
1 revision
Safety is a core design requirement. The project must be useful for research and paper/demo validation without accidentally enabling live execution.
- Live trading is disabled by default.
- The public market-data collector cannot submit or cancel orders.
- The paper runner has no execution path.
- MetaScalp order and cancel CLIs are dry-run by default.
- Demo submissions require explicit confirmation strings.
- LLMs must not participate in live signal generation or execution routing.
The risk engine must stop opening new positions when any of these conditions apply:
- max daily loss reached;
- max open position count reached;
- max per-symbol notional reached;
- max total notional reached;
- max active symbols reached;
- duplicate symbol/direction exposure;
- Binance feed stale or missing;
- MEXC feed stale or missing;
- MetaScalp disconnected or connection inactive;
- observed feed latency above threshold;
- reconnect storm or order-book desync;
- repeated order placement/cancel errors;
- abnormal cancel ratio;
- repeated fill slippage above threshold;
- unexpected position or balance mismatch;
- manual kill switch active.
Do not commit:
-
.envfiles; - API keys or secrets;
- cookies;
- PEM or key files;
- MEXC UID values;
- local MetaScalp user settings;
- local account state.
The project stores secret references only as environment-variable names in memory/memory.json.
Real MetaScalp demo order submission requires:
--submit-demo --confirm-demo-submit METASCALP_DEMO_ORDER
Real MetaScalp demo cancel requires:
--submit-demo --confirm-demo-cancel METASCALP_DEMO_CANCEL
These paths must verify a connected DemoMode=true MEXC connection before POST calls.
A strategy must pass:
- shadow/paper validation;
- replay report;
- latency report;
- fee report;
- slippage report;
- fill-model comparison;
- MetaScalp demo reconciliation;
- operator review of audit logs.
Live mode remains out of scope until explicitly designed, configured, and confirmed.