Keeper Bots

Velocity has no central matching engine. The crossing, triggering and closing that a centralized exchange does in-process is done by offchain agents anyone can run, and the protocol pays per action.

Velocity has no central matching engine. The work that a centralized exchange does inside its own process, crossing two orders, noticing that a stop has been hit, closing an account that fell below maintenance margin, is instead done by offchain agents that watch the chain and send the transaction that performs the action. Anyone can run one, and the protocol pays for each action performed.

The four bots below have a tutorial each. All four ship from apps/keeper-bots-v2 in the velocity-v1 monorepo, which is not public yet. The wallet, RPC endpoint, config file, and run commands they share are in Trading Automation; each tutorial covers only what is specific to its bot.

Order matching bot

Fills crossed orders from the DLOB against a maker or the AMM. No capital needed, paid a filler reward per fill.

Order trigger bot

Marks stop and take-profit orders as triggered once their condition is met, so a matching bot can fill them. No capital needed, paid the flat filler fee.

Liquidation bot

Takes over positions from accounts below maintenance margin at a discount. Needs collateral, because it inherits the liability.

JIT maker bot

Competes to fill market orders during the JIT auction, before the AMM can. A strategy, not maintenance: it holds inventory and can lose money.

The first three are keeper duties: the protocol needs them done and pays a fixed reward for doing them. The JIT maker is a trading strategy that happens to ship in the same app. Keeper incentives covers how the rewards are funded, and Keepers and the decentralized orderbook covers how the DLOB that all of them read is built.