Velocity Exchange Keeper Bots v2

The JIT (Just-In-Time) maker bot supplies liquidity by participating in JIT auctions for perp markets. It uses the jit-proxy client to update bids and asks to match the current top-level market in the DLOB.

Implementation Details

• Risk: Running a JIT maker involves taking on positional risk.
• Leverage: The sample implementation targets a specific leverage (e.g., TARGET_LEVERAGE_PER_ACCOUNT).
• Execution: It uses JitterSniper for order execution.
• Configuration: JIT makers require collateral. You can use forceDeposit in the config or deposit via the SDK/UI beforehand.
• Subaccount Alignment: Ensure all subaccounts used in botConfigs.subaccounts are also enumerated in global.subaccounts to avoid initialization errors.

global:
  subaccounts: [0, 1]

botConfigs:
  jitMaker:
    botId: "jitMaker"
    dryRun: false
    subaccounts: [0, 1, 1]
    perpMarketIndicies: [0, 1, 2]

The liquidator bot monitors spot and perp markets for bankrupt accounts and attempts to liquidate positions according to the protocol's liquidation process.

Key Configuration Concepts

• Derisking: By default, the bot derisks. Set disableAutoDerisking: true to disable the derisking loop if you want to manage risk manually.
• Market Restriction: To restrict which markets are liquidated, use perpMarketIndicies and spotMarketIndicies.
• Subaccount Mapping: Instead of global indices, you can use perpSubAccountConfig and spotSubAccountConfig to map specific subaccounts to specific market indices. These fields must be JSON strings.
• Subaccount Requirement: Any subaccount used in botConfigs must also be listed in the global.subaccounts array to ensure the driftClient initializes correctly.

botConfigs:
  ...
  liquidator:
    ...
    perpSubAccountConfig:
      "0": [0, 1, 2]
      "1": [3, 4, 5, 6, 7, 8, 9, 10, 11, 12]
    spotSubAccountConfig:
      "0": [0, 1, 2]

global:
  subaccounts: [0, 1]

You can configure the bot setup using a .yaml file. To run the bot with a specific configuration, use the --config-file flag.

Configuration Schema Reference

yarn run dev --config-file=example.config.yaml

The FloatingPerpMakerBot is a market-making bot designed to place limit orders on the DLOB (Dynamic Limit Order Book). It automatically shifts orders based on the oracle price using oraclePriceOffset.

Key behaviors:

• Two-sided Market: It attempts to maintain both long and short limit orders.
• Risk Management: It monitors account positions. As positions approach MAX_POSITION_EXPOSURE (default 10%), the bot skews orders to favor risk-reducing trades (placing them closer to the oracle price) and pushes risk-increasing trades further away.
• Automatic Updates: It uses a cooldown mechanism (MARKET_UPDATE_COOLDOWN_SLOTS) to prevent excessive updates to the same market.
• Order Management: If the bot is not quoting exactly two sides of the market (or if the market index is 0), it cancels existing orders and restarts the quoting process.

// The bot is initialized with a DriftClient, SlotSubscriber, RuntimeSpec, and BaseBotConfig
const bot = new FloatingPerpMakerBot(clearingHouse, slotSubscriber, runtimeSpec, config);

The bot implements several mechanisms to handle errors and prevent spamming failed transactions:

1. Simulation Errors: Before sending a transaction, the bot uses buildVersionedTransactionWithSimulatedCus. If simError is present, the error is logged and potentially sent via webhook.
2. Error Suppression: Certain error codes can be passed to errorCodesToSuppress to prevent noisy logs and webhooks for expected/transient errors.
3. User Throttling: If a liquidation attempt fails due to a simulation error (and the error is not suppressed), the user's public key is added to throttledUsers with a timestamp. Subsequent attempts for that user are skipped until LIQUIDATE_THROTTLE_BACKOFF has passed.
4. Bankruptcy Handling: If a user is identified as bankrupt via isUserBankrupt(user), the bot attempts to resolve the bankruptcy via tryResolveBankruptUser before proceeding with liquidations.

The LiquidatorBot is a specialized bot designed for the Drift V2 Protocol. It functions by taking over a portion of an endangered account's position. Because this process involves taking over positions, the bot requires collateral to operate.

Key Mechanics:

• Position Takeover Limit: The bot is constrained by maxPositionTakeoverPctOfCollateral, which defines the maximum percentage of its own free collateral it is willing to spend on any single endangered account.
• State Management: The bot operates in three states: IDLE, LIQUIDATING, and DERISKING.
• Derisking: Before attempting liquidations, the bot can perform a derisk operation to close out open positions on its own accounts to ensure safety.
• Market Support: It supports both Perp (Perpetual) and Spot markets, using specific subaccount configurations to determine which markets to watch and which subaccounts to use for liquidation.

/**
 * LiquidatorBot implements a simple liquidation bot for the Drift V2 Protocol. 
 * Liquidations work by taking over a portion of the endangered account's position, 
 * so collateral is required in order to run this bot.
 */