Files
arbitrade/docs/architecture/current-implementation.md
T
zwitschi 38e1d64437
CI / lint-test-build (push) Successful in 2m31s
feat: add backtesting functionality with UI and API endpoints
- Introduced backtesting page and fragment in the dashboard for running backtests and viewing recent reports.
- Implemented backtest run logic with configuration options including event path, starting balances, trade capital, and fee profiles.
- Added recent backtest reports storage and retrieval.
- Created a new strategy module for statistical arbitrage experiments with validation on configuration parameters.
- Updated settings to include parameters for the statistical arbitrage strategy.
- Enhanced dashboard controls to support the new strategy mode.
- Added unit tests for backtesting functionality and strategy validation.
- Updated templates for backtesting UI integration.
2026-06-02 09:28:22 +02:00

2.2 KiB

Current Implementation Snapshot

This document summarizes the code that exists now, not the original plan.

Runtime

Market Data and Detection

Execution and Risk

  • Multi-leg execution sequencer exists for triangular cycles.
  • Pre-trade validation and trade-limit guards are wired into execution flow.
  • Kill switch and stop conditions are supported.

Dashboard

  • Server-rendered dashboard uses FastAPI + Jinja2 + HTMX.
  • Live metrics, overview, controls, charts, and audit fragments are exposed as separate endpoints.
  • Dedicated backtesting page exists at /dashboard/backtesting.

Backtesting

Deployment

  • Dockerfile installs runtime dependencies from requirements/latest-runtime.in.
  • CI publishes git.allucanget.biz/allucanget/arbitrade:latest.
  • Coolify deploys the prebuilt image and owns runtime env vars and persistent storage.

Current Gaps

  • Cross-exchange arbitrage remains deferred.
  • Stat-arb is experimental, not part of default live strategy.
  • Backtesting UI is functional but still a single-run/report workflow, not a full job queue.