Marseille One Operations Manual
Everything required to deploy the engine on a clean Windows host and patch it into Bybit, Bitget, and Binance perpetuals within minutes.
API Configuration
On each connected exchange (Bybit, Bitget, Binance), generate a dedicated API key for Marseille One. Enable the following permissions:
- Read — account snapshot & position state.
- Write / Trade — order placement and cancellation.
- Contract / Derivatives — required for perpetual grid execution.
- Withdrawal — must remain DISABLED. The engine never requires it.
Bind the key to your static residential IP whenever possible. Paste the API Key & Secret into Config → API key configurationinside the client. Secrets are encrypted with your HWID and never leave the machine.
Environment Requirements
- OS: Windows 10 or Windows 11 (x64).
- CPU / RAM: 2 cores · 4 GB RAM minimum.
- Network: stable wired connection, < 80 ms RTT to the target exchange.
- Recommended hosting: low-latency VPS in Singapore, Tokyo, or Paris (France) — colocated near matching engines for sub-15s patrol budgets.
- Time sync: Windows Time service must be enabled to avoid signature drift.
Core Parameters
15s Patrol Cycle — the engine re-scans the order book every 15 seconds, repricing all unfilled grid levels. Lowering this value increases CPU load and exchange request weight; raising it allows micro-spreads to collapse before capture. The default of 15s is balanced for sub-1% per-day target ROI.
Fluctuation interception threshold — When the actual intercepted value exceeds the configured threshold (default % > 5.0), all grids are paused, and the patrol resumes only after volatility decays for two consecutive cycles. This parameter can be manually adjusted according to risk preference.
Tune both values from Config → Trading Parameters. Conservative profile: 30s cycle, %=2.0. Aggressive profile: 10s cycle, %=4.5.