/Documentation

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.

ℹ️
Settings are saved per-project. Changing settings on one project does not affect others, even if they share the same wallet.

Mode: Paper vs. Live

The Mode setting determines whether the project trades with simulated capital (Paper) or places real orders on Binance (Live).

PaperLive
DefaultYesNo
Real capital at riskNoYes
Order typeSimulated fill at mark priceBinance MARKET order
FeesNone (zero-fee simulation)Binance trading fees apply
SlippageNone (fills at trigger price)Real market slippage
Wallet requiredNoYes
Positions trackedYes (simulated)Yes (real)
⚠️
Live mode places real orders. MARKET orders execute immediately and cannot be cancelled. If your API credentials are invalid or connectivity fails, the runner falls back to paper mode for that tick and logs an error. Always verify your wallet is correctly configured before switching to live.

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

  1. Go to Settings → Wallets in the main navigation.
  2. Click Add Wallet and enter a label, your Binance API key, and your Binance API secret.
  3. Save. The credentials are encrypted immediately on save.
  4. Return to your project's Settings tab and select the wallet from the Wallet dropdown.
  5. Switch Mode to Live and save project settings.

Binance API key permissions

Your Binance API key must have the following permissions enabled:

PermissionRequiredPurpose
Read InfoYesAccount balance and position checks
Enable Spot & Margin TradingYesPlacing MARKET orders
Enable WithdrawalsNoNever required — do not grant this
⚠️
Never enable withdrawal permissions on an API key used with Norena. The platform only requires spot trading access.

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.

IntervalRuns per hourSuitable for
60s (1 min)60Scalping, 1m chart strategies
300s (5 min)125m–15m chart strategies (default)
900s (15 min)415m–1h chart strategies
3600s (1 hr)11h+ chart strategies
ℹ️
The run interval does not need to match the strategy's primary timeframe. Running a 1h chart strategy every 60 seconds is safe — it reads the same hourly close until a new hour completes.

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).

ExampleActive hours (UTC)
09:00 → 17:00Standard business hours
DisabledAlways active (24/7)
22:00 → 06:00Overnight 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
1Run a backtest over at least 3–6 months of data and review all 8 analytics modules.
2Run the strategy in paper mode for at least 1–2 weeks at the same run interval.
3Review the Regime Analysis to confirm the strategy does not only work in one market regime.
4Check the Max Drawdown figure in backtest. Can you tolerate this loss in a live account?
5Verify your Binance API key does not have withdrawal permissions enabled.
6Start live mode with a small position size and scale up gradually.
7Set Max Trades Per Day as a circuit breaker for your first live period.
8Monitor the Logs tab closely for the first 24–48 hours of live operation.
⚠️
Algorithmic trading involves significant financial risk. Past backtest performance is not indicative of future results. Never deploy capital you cannot afford to lose.