ENGINEERING / FREQTRADE

Run the bot.
Understand the system.

A trading strategy is only one component. Deployment, exchange permissions, persistence, monitoring and execution determine what actually runs.

deployment.flow
STRATEGY
  ↓
PROCESS
  ↓
EXCHANGE API
  ↓
PAPER EXECUTION
  ↓
LOGS + METRICS
OPERATIONS PATH

From installation to forward evidence.

01DEPLOYRun Freqtrade on a VPS

Build a persistent trading host with predictable restarts and logs.

↗02CONTAINERSDocker setup

Keep configuration, user data and upgrades reproducible.

↗03EVIDENCEPAPER trading

Measure forward behavior before exposing real capital.

↗04EXCHANGEFreqtrade + OKX

Connect an exchange API with deliberately limited permissions.

↗05SECURITYSecure the VPS

Reduce credential exposure and operational attack surface.

↗
SYSTEM CHECK

A bot is more than strategy code.

01 / STATE

Persist what matters

Trade state, configuration, strategies and model artifacts must survive process and container restarts.

02 / ACCESS

Minimize permissions

Exchange keys should have only required permissions. Public dashboards should not become bot-control surfaces.

03 / EVIDENCE

Forward test the deployment

PAPER mode tests signal behavior and operations together before real execution adds another risk layer.

RELATED RESEARCH
V6 architecture →Forward PAPER testing →Security model →
RUNNING IN OUR LAB

Freqtrade is infrastructure.
V6 is the experiment.

Our V6 branch uses FreqAI on BTC, ETH and SOL in PAPER mode. The public result is automatically updated from sanitized trading metrics.

Open V6 experiment
MODEPAPERMARKETS3TIMEFRAME5m