Configuration

Files

  • config/config.yaml — main runtime configuration.

  • config/keys.json — credentials & secrets (Alchemy, Telegram).

Example: config.yaml

chains:
  ethereum: true
  base: true

panel:
  enabled: true
  language: en
  # other UX feature flags…

features:
  copytrade: true
  sniper: true

Example: keys.json

{
  "alchemy": {
    "ethereum": {
      "http": "https://eth-mainnet.g.alchemy.com/v2/KEY",
      "ws":   "wss://eth-mainnet.g.alchemy.com/v2/KEY"
    },
    "base": {
      "http": "https://base-mainnet.g.alchemy.com/v2/KEY",
      "ws":   "wss://base-mainnet.g.alchemy.com/v2/KEY"
    }
  },
  "telegram": {
    "bot_token": "123456789:ABCDEF…"
  }
}

Environment Variables (suggested)

In CI/CD, inject secrets via environment variables and have your loader populate keys.json at runtime.

Security Notes

  • Rotate Alchemy keys on leakage suspicion.

  • Restrict bot admin commands to trusted users.

  • Protect the host with firewall + fail2ban; avoid exposing RPC to the internet.

PreviousArchitectureNextContributing