← all strategiesMulti-Strategy Rust Trading Engine with Shared Risk Arbiter
Otherscore 6found Jun 26, 2026github.com/Degenapetrader/EVPOLY
Run multiple independent strategy loops on Polymarket within a single Rust engine governed by a shared risk arbiter that enforces cross-strategy position limits and ingests remote alpha signals.
How It Works
The EVPOLY engine is a Rust-based framework that hosts multiple strategy loops concurrently. Each loop implements its own alpha generation logic (which may include arbitrage, momentum, or market-making variants). A centralized shared risk arbiter monitors aggregate exposure across all running strategies and can throttle or halt individual loops to enforce portfolio-level risk limits. A remote alpha interface allows external signals (e.g., from ML models or news feeds) to be injected into strategy loops at runtime.
Entry / Exit Conditions
Entry and exit logic is strategy-specific within each loop. The risk arbiter provides a veto layer: even if a strategy loop generates an entry signal, the arbiter can block execution if aggregate exposure exceeds configured limits. A manual execution API provides human override capability.
Verified Results
The repository has 45 stars and 14 forks, suggesting genuine community interest. Source-available non-commercial licensing implies real code exists and has been reviewed by others. No specific backtested or live results are disclosed.
Implementation Notes
Rust is an appropriate choice for a low-latency trading engine due to its memory safety guarantees and predictable performance characteristics. The shared risk arbiter pattern is a production-grade architectural choice seen in institutional trading systems. The remote alpha interface enables the engine to consume signals from external Python ML models or news parsers without rewriting core execution logic.
Risks
The framework's quality depends entirely on the quality of the individual strategy loops plugged into it. The non-commercial license restricts monetization pathways. Rust's steeper learning curve may limit community contributions and bug fixes. Without disclosed backtest results, the actual edge of any bundled strategy is unknown.