lrvx
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
lrvx is a framework for building trading systems.
Strategies, backtests, paper trading, and live execution sit behind one toolkit. AI agents discover the surface and drive it end-to-end through an MCP control plane. One strategy class runs backtest, paper, and live. Bindings for Python, Node.js, Codon, embedded JavaScript, and a stable C API.
Documentation is available at docs.lrvx.dev
Language bindings
| Language | Install | Docs |
|----------|---------|------|
| Python | pip install lrvx | reference |
| Node.js | npm install @lrvx/lrvx | reference |
| Codon | build from source | reference |
| JavaScript (embedded) | bundled with C++ build | reference |
| C API | liblrvx_capi.so | reference |
All bindings expose the same strategy API, indicators, order books, backtesting, and data I/O. The C API is the integration point for adding support for any other language.
AI companion
lrvx-mcp is a Model Context Protocol server that gives AI coding agents (Cursor, Claude Code, Cline) grounded access to the lrvx surface — symbol lookups across bindings, scaffolders, indicator and backtest tools, full-text doc search.
See the package README for setup and the full tool list.
Connectors
Native exchange connectors (Bybit, Bitget, Hyperliquid, Polymarket) live under connectors/ and build with -DLRVX_BUILD_CONNECTORS=ON. The flag defaults to OFF so a backtest-only or research build doesn't pay the dependency cost. See the connectors README for adapter notes and the optional Polymarket Rust toolchain step.
Venue
Beyond trading on a market, lrvx can be one: the optional venue/ module adds a matching engine and the machinery around it, so many participants can trade against a single order book. See the venue docs.
Build options
The CMake options that gate every optional artefact (bindings, demo, tools, tests, benchmarks, connectors) are catalogued in docs/build/feature-flags.md. Defaults are OFF so a bare cmake -B build produces only the core C++ static library.
Commercial Services
For commercial support, enterprise connectors, and custom development, visit lrvx.dev/services.
Contributing
Contributions are welcome via pull requests.
Please follow the existing structure and naming conventions.
Tests, benchmarks, and documentation should be included where appropriate.