bolt.observer
  • bolt.observer
    • LiquidOps
      • Getting started
      • Setup LiquidOps
        • Api based - pull
        • Agent based - push
      • Node and liquidity automation
      • Integrations
        • Triggers
          • TCP connectivity
          • Tor connectivity
          • Lightning Connectivity
          • Sync to chain
          • Sync to graph
          • Onchain balance
          • Channel balance
          • Node balance
          • Channel open
          • Channel close
          • Inactivity
        • Actions
          • Send a notification
          • Perform Auto Swaps
            • Use case: auto swap-out for a 2M sats channel
            • Use case: auto swap-out for a 50M sats channel
            • Use case: auto swap-in
    • Explorer
    • Integration configuration
      • Discord
      • Email
      • Nostr
      • Opsgenie
      • PagerDuty
      • Slack
      • Telegram
    • Reachability
    • Guides
      • Explorer: advanced search
      • Create a workflow with auto swaps
      • Agent configuration: auto swaps
      • Setup LiquidOps on Voltage nodes (API based - pull)
      • Setup LiquidOps on Voltage nodes (agent based - push)
Powered by GitBook
On this page
  • Recommended setup
  • Voltage setup
  • Agent installation
  • Agent options
  • Verification
  1. bolt.observer
  2. Guides

Setup LiquidOps on Voltage nodes (agent based - push)

This page describes the configuration process of LiquidOps with macaroons for nodes hosted on Voltage.

PreviousSetup LiquidOps on Voltage nodes (API based - pull)

Last updated 1 year ago

In order to fully leverage the capabilities of LiquidOps with a Voltage node, it is essential to utilize our open source . Since Voltage does not support direct installation of bolt.observer, the recommended approach is to install the agent on a separate server, which can seamlessly operate alongside a Voltage node.

Recommended setup

In this tutorial, we will explain how to configure our open-source agent to work with a Voltage node. Refer to the chart below for a visual representation:

Machine 1: Voltage node

Machine 2: a secondary server where the agent can be installed

Voltage setup

After logging into your Voltage account, navigate your "home" page. Scroll down the page and download the Admin macaroon and the TLS certificate onto the machine where you plan to install the agent. In this case, it would be Machine 2, as mentioned in the previous instructions#agent-setup.

Agent installation

Agent options

Ensure the following options are properly configured in the agent:

Apikey

Log into your account on bolt.observer, and from your node page and click on "Enroll in LiquidOps"

Generate an API key and copy its value.

Add the API key as an option in your command line:

--apikey a3fxxxxxxxxxxxxxxxxxxxxxxxxxx

Macaroon path

Specify the path to the admin macaroon file using the following option:

--macaroonpath /some/path/to/file.macaroon

TLS Certificate path

Specify the path to the TLS certificate file using the following option:

--tlscertpath /some/path/to/tls.cert

RPC server

Set the RPC server address using the following option:

--rpcserver demo.m.voltageapp.io:10009

The complete command line with all options is shown below:

bolt-agent --apikey a3fxxxxxxxxxxx --macaroonpath /some/path/to/file.macaroon --tlscertpath /some/path/to/tls.cert --rpcserver demo.m.voltageapp.io:10009

For additional options

Verification

Once the bolt-agent is running correctly, refresh your node page, and you should see "LiquidOps enabled" and the data source displayed in the top right corner of the page.

From this point, you can Create a workflow with auto swaps and starts enjoying the benefits of LiquidOps.

For the agent installation, you can find more information in Agent based - push and in the .

LiquidOps provides extensive automation capabilities for a wide array of operations, including connectivity, node status notifications, and liquidity management through . Liquidity management specifically requires on-chain and off-chain permissions, as well as access to addresses, invoices, and read/write permissions.

Install the agent by following the instructions under github .

repository
auto swaps
repository
agent
Agent and Lightning node running on separate machines
LiquidOps setup with agent
Command line agent configuration