Configuration
Settings & Risk
Last updated April 20, 2026
Configure every aspect of your project's execution, scheduling, and risk controls. Settings are saved per-project and take effect on the next scheduled tick.
Project Settings
Each project has its own independent settings, accessible via the Settings tab inside the project view. Settings changes take effect on the next run — the runner always reads the latest settings_json at the start of each tick.
Mode: Paper vs. Live
The Mode setting determines whether the project trades with simulated capital (Paper) or places real orders on Binance (Live).
| Paper | Live | |
|---|---|---|
| Default | Yes | No |
| Real capital at risk | No | Yes |
| Order type | Simulated fill at mark price | Binance MARKET order |
| Fees | None (zero-fee simulation) | Binance trading fees apply |
| Slippage | None (fills at trigger price) | Real market slippage |
| Wallet required | No | Yes |
| Positions tracked | Yes (simulated) | Yes (real) |
When live mode is selected but no wallet is configured, the runner logs an error and silently falls back to paper mode. No exception is thrown and no alert is sent — check the Logs tab if trades are not executing as expected.
Wallets
Wallets store the Binance API credentials used by live mode. Credentials are encrypted at rest — only the encrypted ciphertext is stored in the database, and they are decrypted at runtime only when needed and immediately zeroed from memory after use.
Setting up a wallet
- Go to Settings → Wallets in the main navigation.
- Click Add Wallet and enter a label, your Binance API key, and your Binance API secret.
- Save. The credentials are encrypted immediately on save.
- Return to your project's Settings tab and select the wallet from the Wallet dropdown.
- Switch Mode to Live and save project settings.
Binance API key permissions
Your Binance API key must have the following permissions enabled:
| Permission | Required | Purpose |
|---|---|---|
| Read Info | Yes | Account balance and position checks |
| Enable Spot & Margin Trading | Yes | Placing MARKET orders |
| Enable Withdrawals | No | Never required — do not grant this |
Symbols
The Symbols field defines which trading pairs the project runs on. Each symbol is evaluated independently on every tick — the strategy runs separately per symbol with its own position state, condition rows, and trade logs.
Symbols must be entered as Binance spot pairs (e.g. BTCUSDT, ETHUSDT). Enter them as comma-separated tags. Duplicates are automatically de-duplicated.
Run Interval
The Interval setting controls how often the strategy is executed, in seconds.
| Interval | Runs per hour | Suitable for |
|---|---|---|
| 60s (1 min) | 60 | Scalping, 1m chart strategies |
| 300s (5 min) | 12 | 5m–15m chart strategies (default) |
| 900s (15 min) | 4 | 15m–1h chart strategies |
| 3600s (1 hr) | 1 | 1h+ chart strategies |
Trade Hours
When enabled, restricts strategy execution to a defined UTC time window. Runs outside this window are skipped and logged as "outside trade hours." Overnight windows are supported (e.g. 22:00 → 06:00 spans midnight correctly).
| Example | Active hours (UTC) |
|---|---|
| 09:00 → 17:00 | Standard business hours |
| Disabled | Always active (24/7) |
| 22:00 → 06:00 | Overnight window, spans midnight |
Disable Weekends
Skips all runs on UTC Saturday and Sunday when checked. Useful for strategies developed on traditional market data that assume a 5-day trading week.
Max Trades Per Day
Limits the number of buy orders placed in a UTC calendar day, per symbol. Sell orders do not count toward the limit — existing positions can always be closed. The counter resets at midnight UTC. Setting to 0 disables the cap entirely.
Advanced Logging
When enabled, writes additional diagnostic entries not written by default:
- Binance connectivity OK confirmation on each live tick
- Take Profit / Stop Loss trigger messages with exact prices
- Max trades per day skip messages (normally silent)
Recommended during debugging and initial live deployment. Can be turned off once the strategy is running stably.
Risk Checklist
Before enabling live mode on any project, work through this checklist:
| # | Item |
|---|---|
| 1 | Run a backtest over at least 3–6 months of data and review all 8 analytics modules. |
| 2 | Run the strategy in paper mode for at least 1–2 weeks at the same run interval. |
| 3 | Review the Regime Analysis to confirm the strategy does not only work in one market regime. |
| 4 | Check the Max Drawdown figure in backtest. Can you tolerate this loss in a live account? |
| 5 | Verify your Binance API key does not have withdrawal permissions enabled. |
| 6 | Start live mode with a small position size and scale up gradually. |
| 7 | Set Max Trades Per Day as a circuit breaker for your first live period. |
| 8 | Monitor the Logs tab closely for the first 24–48 hours of live operation. |