[RFC] Roadmap to v2.0

# RFC: Roadmap to v2.0 ## Introduction The multi-year effort to port the NautilusTrader core from Cython to a Rust + PyO3 implementation is approaching its final stage. The Rust core now backs the majority of the engine and adapter surface. The remaining work is parity validation against the legacy v1 core and optimizations that do not block cutover. This RFC outlines what v2 unlocks, the current status, the proposed cutover process, and the branch and support policy for v1 going forward. Comments and corrections are welcome. ## What v2 unlocks - Pure-Rust trading systems (backtest, sandbox, live) as a first-class option for mission-critical workloads. - Python remains fully supported as the control plane for strategy logic, configuration, and system orchestration, and as the bridge to the Python ecosystem for research and strategy frameworks. - Throughput: early measurements show ~3x message throughput improvement over the v1 Cython core. - Windows high-precision wheels: the Rust core handles `i128`/`u128` natively, removing the MSVC `__int128` blocker that limits the current Cython/FFI path on Windows. ## Status table The current status table is in the June 12, 2026 update below. ## Timing **The cutover is now gate-based rather than tied to a calendar quarter. The next completed `1.x` release is intended to be the final release with support for the legacy Cython v1 core. If final validation finds a serious blocker, we will take another `1.x` release rather than for

Posted by cjdsellers on May 9, 2026, 1:03 AM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [Feature]: Add TurboQuant Support for KV Cache Quantization