bolt.observer
Search
K

Agent configuration: auto swaps

In this guide, we will explore how to configure the open-source agent to perform auto-swaps.
Triggers and actions are the main components of a workflow. Once a trigger is activated, the workflow executes swaps until your channel or node liquidity reaches the desired level. Refer to the flowchart below for a visual representation:
Auto swap flowchart
In addition to defining "target" and "threshold" levels in the GUI, as shown in Create a workflow with auto swaps, you can also set options in CLI when running the agent:

Max and min swap amounts

  • maxswapsats allows you to set the maximum swap amount in satoshis.
  • minswapsats enables you to define the minimum swap amount in satoshis.

Maximum number of attempts

To manage the number of swaps executed by your workflows, use the maxswapattempts parameter. This parameter sets the maximum number of swaps authorized to reach your target liquidity levels. For example, if maxswapattempts = 10, up to 10 consecutive swaps will be allowed.

Fee limits

In a context of a congesetd mempool, it is quite useful to limit the cost or your operations. You can set the upper limit for the cost of a swap, including Boltz fees, off-chain fees, and on-chain fees by using maxfeepercentage option.
For instance, setting maxfeepercentage to 1% ensures the total cost of an 8M sats swap never exceeds 80k sats.
This options is helpful when the mempool is congested and on-chain fees skyrocket.
Here is an example of agent settings that enable auto swaps:
Could not load image
Agent configuration CLI: auto swap
For more details about auto swaps, please refer to the following link:
agent/README.md at main · bolt-observer/agent
GitHub
Agent configuration for Boltz plugin
For general information on the open-source agent, you can find all the details in our GitHub repository.