Configuration
where every setting lives.

01Where settings live

02How config.json works

• You only write the keys you change. Nested objects are merged with the defaults, so {"limits": {"maxOpen": 3}} keeps every other limit.
• Lists replace the default list entirely (for example news.feeds).
• A value of the wrong type is rejected at start with one clear line, for example config: …config.json: bankrollSol: expected number, got string ("10"). Invalid JSON is reported with the file name.
• mode must be paper, alert or live. Anything else stops the desk at start, and live refuses to start until its checks pass (Live trading).
• node src/cli.mjs doctor prints warnings for contradictions: zero or negative limits, placeholder wallets, a stop at or above the entry, exposure caps that make the last slots unreachable, and more.

The example file:

{
  "mode": "paper",
  "bankrollSol": 10,
  "modules": { "perps": false, "polymarket": false, "jev": false },
  "whales": { "wallets": ["PASTE_A_SOLANA_WALLET_YOU_FOLLOW"] },
  "news": {
    "feeds": [
      "https://cointelegraph.com/rss",
      "https://www.coindesk.com/arc/outboundfeeds/rss/",
      "https://decrypt.co/feed"
    ]
  }
}

03The keys you will change most

Every other key (lane thresholds, exit ladders, allocator, books) is documented by the comment next to it in src/defaults.mjs, and the important ones on the page of the feature they belong to.

04Console fields and the config keys they set

config.json is the base. With the console on (npm start, npm run dash), a console field overrides its config key only when its value differs from the console default in the table below, that is, once you really changed it. Exception: Desk → Mode and every Live trading field always come from the console while it is running (defaults included): a mode: "live" or live.* in config.json is used only when the console is off (DASH=0 or DESK_ADMIN=0). See Live trading. The check runs at start and after every save. If you set a field back to its console default, the config.json value (or the built-in default) applies again.

05Solana RPC and the pump.fun WebSocket

The public Solana endpoint drops heavy logsSubscribe streams. For a stable pump.fun stream, create a free endpoint at Helius, QuickNode or Chainstack and set it in one of two places:

• Console (owner): Integrations → Solana RPC / WebSocket URL. Enter the https:// URL. The desk uses it as solanaRpc and derives the WebSocket (pump.wsUrl) by replacing http with ws, at start and right after each save. The console's Solana RPC health check tests the same URL. When filled in, it wins over config.json.
• config.json, if your provider's WebSocket URL is not simply the HTTP URL with ws:

{
  "solanaRpc": "https://<your-rpc-host>/?api-key=<key>",
  "pump": { "wsUrl": "wss://<your-rpc-host>/?api-key=<key>" }
}

06Environment variables

The desk loads .env next to package.json on start (cp .env.example .env); a variable already set in your shell or process manager wins. You can also export them in your shell, or set them in your process manager (Deployment).

export TELEGRAM_BOT_TOKEN=<token>
export TELEGRAM_CHAT_ID=<chat id>
npm start

07Temporary overrides for research

replay and sweep accept --set key=value, repeatable, without touching config.json. Values are read as JSON when they parse (numbers, true/false, lists). A key that does not exist is refused, so a typo cannot silently change nothing.

node src/cli.mjs replay --set pump.lanes.moonshot.enabled=false --set ev.minEv=0.05