⚡
Lightning Node Management
🇺🇸 English
🇺🇸 English
  • Contents
  • Lightning basics
  • Create inbound liquidity
  • Create outbound liquidity
  • Comparison table of software implementations
  • Comparison table of lightning channel markets
  • Node Types
    • Merchant
    • Spending
    • Routing
  • Advanced Tools
    • lnd.conf example
    • Advanced and automated fee settings
    • Set up an LND watchtower and connect a client
    • Methods to create a balanced channel with a trusted peer
    • Pool usage notes
    • Bos Score
  • Technicals
    • Connecting to a lightning node remotely
    • High onchain fee environment
    • Compact the LND database (channel.db)
    • Manage the LND onchain funds in Electrum Wallet
  • Recovery
    • Resources for LND
    • Resources for Core Lightning
  • Privacy
    • Resources on Lightning privacy
    • VPN tunnels
  • Hardware deployment
    • Hardware recommendations
    • RaspiBolt
    • RaspiBlitz
      • charge-lnd
      • Balance of Satoshis Telegram Bot
      • LND updates
      • Bitcoin Core updates
      • VPN and firewall setup
    • TrueNAS (FreeBSD) node
      • aliases
      • Balance of Satoshis
      • Lightning Terminal
      • Circuitbreaker
      • LNtop
      • LND notes
      • stream-lnd-htlcs
      • Suez
      • Tailscale
      • Connect Zeus
  • Donate
    • Donations
Powered by GitBook
On this page
  • clearing_price_rate
  • ratings
  • nextbatchinfo
  • auction snapshot
  • logs
  • Resources

Was this helpful?

Edit on GitHub
  1. Advanced Tools

Pool usage notes

PreviousMethods to create a balanced channel with a trusted peerNextBos Score

Last updated 1 year ago

Was this helpful?

Read through the and the .

The best place to search for commands and keywords:

Follow for an (unofficial) list of past batches and curated content.

The Pool install script for the RaspiBlitz is :

# download
wget https://raw.githubusercontent.com/openoms/raspiblitz/pool/home.admin/config.scripts/bonus.pool.sh
# inspect the script
cat bonus.pool.sh
# install
bash bonus.pool.sh on

clearing_price_rate

The uniform clearing price rate in parts per billion of the batch. It equals to the lowest included bid rate in the batch.

ratings

Returns the current Node Tier of a node, along with other information.

By default nodes listed in the are used to fill the bids, called TIER_1 in the ratings. They are shortlisted according to: up time, inbound capacity, history, channel updates, ability to actively route (via probing).

  • Check for a rating of a public node:

      pool auction ratings [NODE_PUBKEY]
  • The check the rating of the local node:

      $ pool auc r $(lncli getinfo|grep "identity"|cut -d'"' -f4)
      {
          "node_ratings": [
              {
                  "node_pubkey": "REDACTED_NODE_PUBKEY",
                  "node_tier": "TIER_1"
              }
          ]
      }
  • A channel buyer (Taker) can specify a bid to accept all tiers with --min_node_tier 0

     --min_node_tier value          the min node tier this bid should be matched with, tier 1 nodes are considered 'good', if set to tier 0, then all nodes will be considered regardless of 'quality' (default: 0)

nextbatchinfo

Returns information about the next batch the auctioneer will perform.

Shows:

  • fee_rate_sat_per_kw: what the target fee rate cut off will be

  • clear_timestamp: the blockheight of the next marker clearing attempt

$ pool auction nextbatchinfo

Example:

{
    "conf_target": 35,
    "fee_rate_sat_per_kw": "27714",
    "clear_timestamp": "1604406782"
}

For your order to be included in the next batch the fee_rate_sat_per_kw should be above the cut off value.

List the fee_rate_sat_per_kw of your orders with:

$ pool orders list | grep fee_rate_sat_per_kw

auction snapshot

Returns information about a prior batch such as the clearing price and the set of orders included in the batch. The prev_batch_id field can be used to explore prior batches in the sequence, similar to a block chain.

last batch info: $ pool auction snapshot

query the prior batches recursively:

# get the previous batch id
prev_batch_id=$(pool auc s |jq -r '.prev_batch_id')

# show the prior batch (just repeat the line to show the past batches)
prev_batch_id=$(pool auc s --batch_id $prev_batch_id|jq -r '.prev_batch_id') && pool auc s --batch_id $prev_batch_id

# show only the clearing price of the prior batch recursively:
prev_batch_id=$(pool auc s --batch_id $prev_batch_id|jq -r '.prev_batch_id') && pool auc s --batch_id $prev_batch_id|jq -r '.clearing_price_rate'

logs

Monitor the pool logs in: /home/pool/.pool/logs/mainnet/poold.log

Example:

tail -f -n 1000 /home/pool/.pool/logs/mainnet/poold.log

Resources

Search the txid of a batch on after it is confirmed (channels opened and published) to see the details of the channels and peers involved.

Documentation:

Source code:

API reference:

Unofficial curated info on Twitter:

Lightning Wiki page:

Pool release thread from @roasbeef :

LNmarkets newletter about Pool:

Technical Deep Dive blogpost:

Whitepaper:

documentation
resources below
https://lightning.engineering/poolapi
https://twitter.com/LightningPool
in this PR
Bos Score list
http://1ml.com
https://twitter.com/openoms/status/1326482404224229376
https://pool.lightning.engineering/
https://github.com/lightninglabs/pool
https://lightning.engineering/poolapi
https://twitter.com/LightningPool
https://lightningwiki.net/index.php/Lightning_Pool
https://twitter.com/roasbeef/status/1323299990916063232
https://lnmarkets.substack.com/p/15-november-9th-2020
https://lightning.engineering/posts/2020-11-02-pool-deep-dive/
https://lightning.engineering/lightning-pool-whitepaper.pdf