Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

The RL Engine: Continuous Learning Architecture

How It Works

The RL engine's role is order processing and intelligent routing. When a large order enters the system, the engine reads real-time market state (pool depth, volatility, cross-venue pricing, historical execution data) and outputs the optimal splitting and routing strategy.

The engine is not a static algorithm. It learns from every trade it processes through a closed-loop feedback system:

  • Dynamic Labeling. Every execution generates structured labels across five dimensions: intent (what the user wanted), route (what path the engine chose), fill (actual execution outcome), impact (market movement caused), and outcome (performance vs. benchmark). This closed-loop data is unavailable from any public market data provider. Binance has historical price data, but cannot see the intent-to-outcome execution loop. Deluthium earns these labels through execution itself.

  • Millisecond-Level Inference. The RL engine's inference runs at millisecond speed. Execution decisions do not create latency in the trading flow.

  • ZK-Verified Decisions. Every decision the RL engine makes is captured in the ZK-Merkle Tree, making the model's behavior auditable. This replaces the need for federated learning or distributed trust mechanisms with verifiable cryptographic proofs.


Data Flywheel

The RL engine creates a compounding advantage through what we call the execution quality flywheel:

More order flow enters the system β†’ The RL engine receives more high-quality closed-loop training data β†’ Execution strategies (routing, splitting, timing) improve β†’ Better execution quality attracts more order flow β†’ The flywheel accelerates.

This flywheel is Deluthium's core competitive moat. The execution data that trains the model is not purchasable on the open market (no vendor sells intent-to-outcome execution loops), it scales with volume (more trades = more data = better model), and it creates a structural barrier for competitors (copying the architecture does not copy the accumulated execution data).

Last updated