Order Evaluation and Execution
Dexible operates a managed infrastructure that constantly monitors market conditions against a private database of orders. Each order is evaluated continuously to determine if user-specific criteria is met for each round of an order (or a single round if it's a single-round order). When market conditions are satisfied, Dexible submits a portion of a large order to a settlement smart contract for execution using a bank of "relays" that monitor and manage active transactions. These market conditions are evaluated on what would traditionally be considered the rules of an algo--or trading algorithm. But Dexible provides an algo trading experience that isn't necessarily fixed by a named trading algo--rather, it defines algos by a set of configured "policies".

Policy-Based Evaluation

Dexible relies on a configured set of "policies" to determine when a round should be executed. These policies include things like GasCost, LimitPrice, StopPrice, or BoundedDelay. Each of these tells Dexible whether certain conditions are met and allows Dexible to simply evaluate a set of policies before executing the details of an order.
From a trader's perspective using the UI, these policies are hidden as an internal implementation. When you tune a fixed gas price, you're actually modifying a GasCost policy. When you set a limit price, you are actually tuning the LimitPrice policy. All these policies are added to the order and evaluated once the order is submitted to Dexible.
In this way, Dexible can remain extremely flexible as an algo trading platform since adding new algos just means either adding more policy types or combining them in interesting ways. If you really want to tune a trading algo, we suggest using the SDK since it allows you to specify policy-level attributes for an order's algo.

Expanding Algo Definitions

Dexible will soon introduce more policy configurations to its UI platform. Namely, adding price ranges to TWAP would allow each round of a TWAP order to stay within a specific price range. Adding StopPrice policies with an upside activation price would allow take-profit algos that trigger on an upward-trending token price. Stay tuned as we add more algo types and eventually offer an algo editor where adding and tuning policies through the UI is possible for those that want to get way down in the weeds.
Last modified 3mo ago