Skip to content

v0.1.0

Latest

Choose a tag to compare

@Erio-Harrison Erio-Harrison released this 15 Oct 12:07
· 16 commits to master since this release
b58d1ba

Initial tagged release. The core data collection + backtesting pipeline works end-to-end, and the desktop app covers the Dashboard and Backtest pages. This is an early 0.x release — expect rough edges, see "Known limitations" below.

What's included

  • Real-time tick data collection from Binance via WebSocket (trading-core live), with batched Postgres writes and a tiered (memory + Redis) cache
  • Backtesting engine with SMA and RSI strategies, tick-based and OHLC-based modes, and standard performance metrics (Sharpe ratio, max drawdown, win rate, profit factor, etc.)
  • Optional CLI paper trading (trading-core live --paper-trading), now correctly tracking positions per symbol
  • Tauri + Next.js desktop app: Dashboard (data overview, OHLC preview, quick strategy test) and Backtest (full configuration + results) pages
  • CI: Rust fmt/clippy/test and frontend lint/build on every push and PR

Known limitations

  • The desktop app's Trading (live) and Settings pages are not implemented yet — live trading and paper trading are currently CLI-only (trading-core)
  • No multi-instance coordination for trading-core — running more than one instance duplicates work rather than scaling or failing over (see #9)
  • BacktestMetrics and the SmaStrategy/RsiStrategy signal logic have no automated test coverage yet (see #8)
  • The live/paper-trading hot path still does a synchronous DB write and cache round-trips per tick — fine for personal/dev use, not tuned for high-frequency throughput

Notable fixes in this release

  • profit_factor no longer returns a Decimal::MAX sentinel that leaked into the UI as a meaningless huge number when a backtest had no losing trades
  • Fixed a test-isolation bug causing flaky cargo test failures
  • Fixed ESLint errors that were silently breaking npm run build
  • trading-core now handles SIGTERM in addition to SIGINT/Ctrl+C, so graceful shutdown actually runs in containerized deployments
  • Added a security notice about a phishing campaign distributing malware through a cloned copy of this repo — see the README