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
  • Requirements
  • Description
  1. bolt.observer
  2. LiquidOps
  3. Integrations
  4. Triggers

Channel balance

PreviousOnchain balanceNextNode balance

Last updated 2 years ago

Requirements

To use this feature, you need to have LiquidOps enabled with version 0.2.0 or higher or enrolled with macaroons.

Description

Channel balance checks perform constant monitoring of your channels´ liquidity and report when the liquidity falls below a certain level. The liquidity is the available balance that can be sent across the channel in one direction as reminded here below (source )

Liquidity(NodeA) = balance(NodeA) - channel_reserve(NodeA) - pending_HTLCs(NodeA)

The channel inbound liquidity is the amount of bitcoin that a node can receive through that channel.

The channel outbound liquidity is the amount of bitcoin that a node can send through that channel.

Note: We make a difference between the inbound/outbound liquidity at a channel level and at a node level. The inbound/outbound liquidity of a node will be the sum of inbound/outbound liquidity of all its channels and can be monitored with Node balance trigger.

The channel balance trigger can be configured by selecting 2 parameters :

Liquidity type: Inbound or Outbound

Threshold: expressed in %

agent
lnbook