raspiblitz/FAQ.cl.md

<!-- omit in toc -->
# Core Lightning on the RaspiBlitz FAQ

<!-- omit in toc -->
## Table of Contents
- [Common questions about the different Lightning Network implementations](#common-questions-about-the-different-lightning-network-implementations)
  - [Can LND and CLN nodes open channels to each other and route payments?](#can-lnd-and-cln-nodes-open-channels-to-each-other-and-route-payments)
  - [Can I run LND and CLN connected to the same node?](#can-i-run-lnd-and-cln-connected-to-the-same-node)
  - [Can I convert an LND node to CLN (or the opposite)?](#can-i-convert-an-lnd-node-to-cln-or-the-opposite)
  - [Is there a table to quickly compare LND and CLN?](#is-there-a-table-to-quickly-compare-lnd-and-cln)
- [CLN official documentation and support channels](#cln-official-documentation-and-support-channels)
- [Commands and aliases](#commands-and-aliases)
- [Directories](#directories)
- [Config file](#config-file)
  - [Default values](#default-values)
- [CLN cheatsheet](#cln-cheatsheet)
- [Plug-ins](#plug-ins)
  - [General info](#general-info)
  - [Directories](#directories-1)
  - [Implemented plugins](#implemented-plugins)
  - [Add a custom plugin](#add-a-custom-plugin)
  - [CLBOSS](#clboss)
  - [Feeadjuster](#feeadjuster)
  - [Dual funded channels](#dual-funded-channels)
    - [Reading](#reading)
    - [Setting up](#setting-up)
    - [Open a dual funded channel](#open-a-dual-funded-channel)
    - [Fundchannel syntax](#fundchannel-syntax)
    - [Multifundchannel syntax](#multifundchannel-syntax)
  - [Offers](#offers)
  - [Poncho - hosted channels](#poncho---hosted-channels)
- [Feature bits](#feature-bits)
- [Testnets](#testnets)
- [Backups](#backups)
  - [Backup strategy](#backup-strategy)
  - [Seed](#seed)
  - [How to display the hsm\_secret in a human-readable format?](#how-to-display-the-hsm_secret-in-a-human-readable-format)
  - [How to test the seedwords?](#how-to-test-the-seedwords)
  - [How to restore the hsm\_secret from text?](#how-to-restore-the-hsm_secret-from-text)
  - [Channel database](#channel-database)
- [Recovery](#recovery)
  - [Recover from a cl-rescue file](#recover-from-a-cl-rescue-file)
  - [Recover from a seed](#recover-from-a-seed)
  - [Emergency recovery in case of lost channel states](#emergency-recovery-in-case-of-lost-channel-states)
  - [Restore a CLN node from the database backup on the SDcard](#restore-a-cln-node-from-the-database-backup-on-the-sdcard)
  - [Rescan the chain after restoring a used CLN wallet](#rescan-the-chain-after-restoring-a-used-cln-wallet)
  - [Guesstoremote to recover funds from force-closed channels](#guesstoremote-to-recover-funds-from-force-closed-channels)
- [sqlite3 queries](#sqlite3-queries)
- [Extract the private and public key from the hsm\_secret file](#extract-the-private-and-public-key-from-the-hsm_secret-file)
- [Update](#update)
  - [Update to a new CLN release](#update-to-a-new-cln-release)
  - [Experimental update to the latest master](#experimental-update-to-the-latest-master)
- [sqlite3 queries](#sqlite3-queries-1)
- [Script file help list](#script-file-help-list)
- [All possible config options](#all-possible-config-options)

## Common questions about the different Lightning Network implementations

### Can LND and CLN nodes open channels to each other and route payments?
* Yes, all [BOLT specification](https://github.com/lightningnetwork/lightning-rfc) compliant implementations can open channels to each other and route payments.

### Can I run LND and CLN connected to the same node?
* Yes, both can run parallel on a RaspiBlitz and even have channels with each other.

### Can I convert an LND node to CLN (or the opposite)?
* No, currently there are no tools available to convert between the databases storing the channel states.
The channels would need to be closed to use the same funds in an other node.

### Is there a table to quickly compare LND and CLN?
* see [github.com/openoms/lightning-node-management/blob/master/node-types/comparison.md](https://github.com/openoms/lightning-node-management/blob/master/node-types/comparison.md)

---

## CLN official documentation and support channels
* https://lightning.readthedocs.io/
* https://github.com/ElementsProject/lightning
* Telegram: https://t.me/lightningd
* Discord: https://discord.gg/YGdpyj2aXj
* IRC: #c-lightning on libera.chat or https://matrix.to/#/#c-lightning:libera.chat
## Commands and aliases
* Check if the CLN daemon is running:
    ```
    sudo systemctl status lightningd
    ```
* Follow it's system output for debugging:
    ```
    sudo journalctl -fu lightningd
    ```
* The logs can be accessed in the menu `SYSTEM` - `CLLOG`
or with the alias: `cllog`
* The frequently used commands are shortened with alisases. Check them with the command `alias`:
    ```
    alias cl='sudo -u bitcoin /usr/local/bin/lightning-cli --conf=/home/bitcoin/.lightning/config'
    alias clconf='sudo nano /home/bitcoin/.lightning/config'
    alias cllog='sudo tail -n 30 -f /home/bitcoin/.lightning/bitcoin/cl.log'
    ```
## Directories
* All data is stored on the disk in:
`/mnt/hdd/app-data/.lightningd`
* and symlinked to:
`/home/bitcoin/.lightningd`

## Config file
* Edit in the menu `SYSTEM` - `CLNCONF` or use the alias `clconf`

### Default values
* on the RaspiBlitz for mainnet
  ```
  network=bitcoin
  log-file=cl.log
  log-level=info
  plugin-dir=/home/bitcoin/cln-plugins-enabled
  # Tor settings
  proxy=127.0.0.1:9050
  bind-addr=127.0.0.1:9736
  addr=statictor:127.0.0.1:9051/torport=9736
  always-use-proxy=true
  ```
* find [all the possible config options](#all-possible-config-options) below.

## CLN cheatsheet
<https://github.com/grubles/cln-cheatsheet>

## Plug-ins

### General info
* https://lightning.readthedocs.io/PLUGINS.html#a-day-in-the-life-of-a-plugin
* https://github.com/lightningd/plugins/

### Directories
* The plugins are installed to:
`/home/bitcoin/cl-plugins-available`
* and symlinked to:
`/home/bitcoin/cl-plugins-enabled`
* All plugins in the `/home/bitcoin/cl-plugins-enabled` directory are loaded automatically as set in the config file: `/home/bitcoin/.lightningd/config`

### Implemented plugins
* summary
* sparko
* [CLBOSS](#clboss)
* [feeadjuster](#feeadjuster)

### Add a custom plugin
* Place the plugin in the `/home/bitcoin/cl-plugins-enabled` directory
* Make sure it is owned by the `bitcoin` user and is executable:
    ```
    sudo chown bitcoin:bitcoin /home/bitcoin/cl-plugins-enabled/PLUGIN_NAME
    sudo chmod +x /home/bitcoin/cl-plugins-enabled/PLUGIN_NAME
    ```
* start with
    ```
    lightning-cli plugin start /home/bitcoin/cl-plugins-enabled/PLUGIN_NAME
    ```
* or to load it automatically on restart:
    ```
    sudo systemctl restart lightningd
    ```
    From the directory `/home/bitcoin/cl-plugins-enabled` it will load auomatically after restarts.
* To just load it run it once store in (and start from):
    `/home/bitcoin/cl-plugins-available/`

### CLBOSS
A plugin for automatic LN node management.
CLBOSS only requires to have funds deposited  to the onchain wallet of CLN.
The recommended amount to start is ~ 10 million satoshis (0.1 BTC).

It does automatically:

* generate outbound capacity - opens channels
* generate inbound capacity - submarine swaps through the boltz.exchange API
* aware of onchain fees and mempool through CLN and makes transactions when fees are low
* manages rebalancing - performs probing
* closes bad channels (inactive or low traffic) - this function needs to activated manually

Overall it is a tool which makes users able to send and receive lightning payments with minimal interaction, basically setting up a routing node by itself.

The transactions made by CLBOSS does cost money and running it requires a fair amount of trust in the (fully open-source - MIT) code.
Neither the CLBOSS nor the RaspiBlitz developers can take responsibility for lost sats, use at your own discretion!

* Activate it in the menu - `SETTINGS` - `-CL CLBOSS`
* Discussion: https://github.com/rootzoll/raspiblitz/issues/2490
* Advanced usage
https://github.com/ZmnSCPxj/clboss#clboss-status
* Stopping CLBOSS will leave the node in the last state. No channels will be closed or funds removed when CLBOSS is uninstalled.
* Check the running version:
    ```
    /home/bitcoin/cl-plugins-enabled/clboss --version
    ```

### Feeadjuster

* Install:
`config.scripts/cl-plugin.feeadjuster.sh on`

* to set the default fees add to the CLN config file (`clconf`)
  ```
  fee-base=BASEFEE_IN_MILLISATS
  fee-per-satoshi=PPM_FEE_IN_SATS
  ```

* example feeadjuster options
    ```
    fee-base=0
    fee-per-satoshi=200
    feeadjuster-imbalance=0.2
    feeadjuster-threshold=0.10
    feeadjuster-threshold-abs=0.01btc
    feeadjuster-enough-liquidity=1000000000msat
    feeadjuster-deactivate-fee-update
    feeadjuster-adjustment-method=hard
    ```
* effect displayed in the logs (`cllog`)
    ```
    plugin-feeadjuster.py:
    Plugin feeadjuster initialized (0 base / 200 ppm) with an imbalance of 20%/80%,
    update_threshold: 10%, update_threshold_abs: 1000000000msat,
    enough_liquidity: 1000000000msat, deactivate_fuzz: None,
    forward_event_subscription: False, adjustment_method: get_ratio_hard,
    fee_strategy: get_fees_global, listchannels_by_dst: True
    ```

* more options for the feeadjuster to be set in the CLN config can be seen in the [code](https://github.com/lightningd/plugins/blob/master/feeadjuster/feeadjuster.py#L323)

* start the feeadjuster
    ```
    cl plugin start /home/bitcoin/cl-plugins-available/plugins/feeadjuster/feeadjuster.py
    ```
* stop (best to run only periodically)
    ```
    cl plugin stop /home/bitcoin/cl-plugins-available/plugins/feeadjuster/feeadjuster.py
    ```
* Can use menu - `CL` - `SUEZ` to visualize the channel balances and fee settings
* check the list of base fees
    ```
    cl listpeers | grep fee_base_msat
    ```
* check the list of proportional fees
    ```
    cl listpeers | grep fee_proportional_millionths
    ```
* set the fees to the defaults
    ```
    cl setchannelfee all
    ```

### Dual funded channels
#### Reading
* https://medium.com/blockstream/c-lightning-opens-first-dual-funded-mainnet-lightning-channel-ada6b32a527c
* https://medium.com/blockstream/setting-up-liquidity-ads-in-c-lightning-54e4c59c091d
* https://twitter.com/niftynei/status/1389328732377255938
* lightning-rfc PR: https://github.com/lightningnetwork/lightning-rfc/pull/851/files
* represented by the feature bits 28/29

#### Setting up
* activate the feature on your node:
Type: `clconf` or use the menu `SYSTEM` - `CLCONF`.
Add the line:
    ```
    experimental-dual-fund
    ```
    Save and restart CLN.

* set up a liquidity ad:
    ```
    lightning-cli funderupdate -k policy=match policy_mod=100
    ```
    or set in the config for example - see the meaning of each line in https://medium.com/blockstream/setting-up-liquidity-ads-in-c-lightning-54e4c59c091d :

    ```
    experimental-dual-fund
    funder-policy=match
    funder-policy-mod=100
    lease-fee-base-msat=500sat
    lease-fee-basis=50
    channel-fee-max-base-msat=100sat
    channel-fee-max-proportional-thousandths=2
    ```
* check the settings used currently on your node:
    ```
    lightning-cli funderupdate
    ```
* check your advertised settings (needs some minutes to appear):
    ```
    lightning-cli listnodes $(lightning-cli getinfo | jq .id)
    ```

#### Open a dual funded channel
* check if a node has onchain liquidity on offer:
    ```
    lightning-cli listnodes nodeid
    ```

    Example:
    ```
    lightning-cli listnodes 02cca6c5c966fcf61d121e3a70e03a1cd9eeeea024b26ea666ce974d43b242e636
    ```
* list all nodes known in the graph with active offers:
    ```
    lightning-cli listnodes | grep option_will_fund -B20 -A7
    ```
* note the node `id` and `compact_lease`

* connect to the node
    ```
    lightning-cli connect nodeID@IP_or.onion
    ```
#### Fundchannel syntax
*  the amount is the own funds in the wallet contributed
use equal amounts to have a balanced channel from start
the amounts can be specified in `sat` or `btc`
    ```
    lightning-cli fundchannel -k id=NODE_ID amount=OWN_AMOUNTsat request_amt=PEER_CONTRIBUTION_AMOUNTsat compact_lease=COMPACT_LEASE
    ```
    It can fail if the offer changed or there are not enough funds available on either side.

* open a dual funded channel with a chosen utxo and miner feerate
list the utxo-s with `lightning-cli listfunds`, can list multiple
the feerate is in `perkb` by default, e.g. use 1000 for 1 sat/byte
    ```
    lightning-cli fundchannel feerate=PERKB_FEERATE utxos='["TRANSACTION_ID:INDEX_NUMBER"]' -k id=NODE_ID amount=OWN_AMOUNTsat request_amt=PEER_CONTRIBUTION_AMOUNTsat compact_lease=COMPACT_LEASE
    ```

#### Multifundchannel syntax
* discussed in https://github.com/ElementsProject/lightning/issues/4642#issuecomment-1149657371
* see a good format (json autoformatting tools help - like `CTRL`+`SHIFT`+`i` in VSCode):
    ```
    ₿ lightning-cli multifundchannel '[
        {
            "id": "nodeID1",
            "amount": "amount_in_sats"
        },
        {
            "id": "nodeID2",
            "amount": "amount_in_sats"
        },
        {
            "id": "nodeID3",
            "amount": "amount_in_sats"
        },
        {
            "id": "nodeID4",
            "amount": "amount_in_sats",
        }
    ]' 1000perkb
    ```

* The returned output:
    ```
    {
        "tx": "RAW............TX",
        "txid": "TX................ID",
        "channel_ids": [
            {
                "id": "nodeID1",
                "channel_id": "CHANNEL_ID2",
                "outnum": 3
            },
            {
                "id": "nodeID2",
                "channel_id": "CHANNEL_ID1",
                "outnum": 4
            },
            {
                "id": "nodeID3",
                "channel_id": "CHANNEL_ID4",
                "outnum": 1
            },
            {
                "id": "nodeID4",
                "channel_id": "CHANNEL_ID3",
                "outnum": 2
            }
        ],
        "failed": []
    }
    ```

### Offers
* Details at bolt12.org
* Create an offer to receive payments:
https://lightning.readthedocs.io/lightning-offer.7.html
    ```
    lightning-cli offer amount description [vendor] [label] [quantity_min] [quantity_max] [absolute_expiry] [recurrence] [recurrence_base] [recurrence_paywindow] [recurrence_limit] [single_use]
    ```
* Example:
Create a reusable offer which can be paid with any amount for LN tips using a fixed string.
    ```
    lightning-cli offer any tip
    ```

* Create an offer to send payments:
https://lightning.readthedocs.io/lightning-offerout.7.html
    ```
    lightning-cli offerout amount description [vendor] [label] [absolute_expiry] [refund_for]
    ```
* Fetch an invoice to pay an offer:
https://lightning.readthedocs.io/lightning-fetchinvoice.7.html
Will need at least one peer which supports onion the messages. For example:
    ```
    lightning-cli connect 024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605@128.199.202.168:9735
    ```
* Then use the command to fetch the BOLT12 invoice:
    ```
    lightning-cli fetchinvoice offer [msatoshi] [quantity] [recurrence_counter] [recurrence_start] [recurrence_label] [timeout] [payer_note]
    ```
* decode a BOLT12 invoice:
    ```
    lightning-cli decode bolt12_invoice
    ```
* pay a a BOLT12 invoice:
Will need to pay through a peer which supports the onion messages which means you need at least one channel with such a node.
    ```
    lightning-cli pay bolt12_invoice
    ```
* see if there is a new invoice is paid with:
    ```
    lightning-cli listinvoices
    ```
    The `pay_index` will increase as the offer gets reused.

### Poncho - hosted channels
* <https://github.com/fiatjaf/poncho/>
* <https://github.com/rootzoll/raspiblitz/issues/3269>

## Feature bits
* <https://bitcoin.stackexchange.com/questions/107484/how-can-i-decode-the-feature-string-of-a-lightning-node-with-bolt-9>
* Convert the hex number from `lightning-cli listpeers` to binary: <https://www.binaryhexconverter.com/hex-to-binary-converter> and count the position of the bits from the right.

## Testnets
* for testnet and signet there are prefixes `t` and `s` used for the aliases, daemons and their own plugin directory names.
* Testnet
    ```
    # alias:
    tcl | tclconf | tcllog

    # daemon service name:
    tlightningd

    # config file:
    /home/bitcoin/.lightningd/testnet/config

    # plugin directory:
    /home/bitcoin/tcl-plugins-enabled
    ```
* Signet
    ```
    # aliases:
    scl | sclconf | scllog

    # daemon service name:
    slightningd

    # config file:
    /home/bitcoin/.lightningd/signet/config

    # plugin directory:
    /home/bitcoin/scl-plugins-enabled
    ```

## Backups
* <https://lightning.readthedocs.io/FAQ.html#how-to-backup-my-wallet>>
* General details: <https://lightning.readthedocs.io/BACKUP.html>

### Backup strategy
* discussed in <https://github.com/rootzoll/raspiblitz/issues/2983>

* store your seed (or the `hsm_secret` HEX) as text.
* the channel database (`lightningd.sqlite3`) is replicated to the SDcard real-time.
* can make a cl-rescue file from time-to-time so you have a backup of the onchain wallet (`hsm_secret` - generated from the seed) and the channel database (`lightningd.sqlite3` - can be restored as a last resort - will trigger force closes with the peers).

* A future CLN version will have an SCB like functionality, but will be stored automatically with the peers (encrypted over LN), see the PR: [ElementsProject/lightning#5361](https://github.com/ElementsProject/lightning/pull/5361)

### Seed
* By default a BIP39 wordlist compatible, 24 words seed is used to generate the `hsm_secret`
* If the wallet was generated or restored from seed on a RaspiBlitz the seed is stored in the disk with the option to encrypt
* Display the seed from the menu - `CL` - `SEED`
* The file where the seed is stored (until encrypted) is on the disk: `/home/bitcoin/.lightning/bitcoin/seedwords.info`
* Show manually with:
`sudo cat /home/bitcoin/.lightning/bitcoin/seedwords.info`
* If there is no such file and you have not funded the CLN wallet yet can reset the wallet and the next wallet will be created with a seed.

### How to display the hsm_secret in a human-readable format?
* If there is no seed available it is best to save the hsm_secret as a file with `scp` or note down the alphanumeric characters in the two line displayed with:
    ```
    sudo xxd /home/bitcoin/.lightning/bitcoin/hsm_secret
    ```

### How to test the seedwords?
* The manual process:
    ```
    # display the hsm_secret in hex:
    sudo -u bitcoin xxd /home/bitcoin/.lightning/bitcoin/hsm_secret

    # input seed and generate an hsm_secret in a temporary location:
    lightning-hsmtool generatehsm /dev/shm/test_hsm_secret

    # compare
    xxd /dev/shm/test_hsm_secret

    # delete temp file
    srm /dev/shm/test_hsm_secret
    ```
### How to restore the hsm_secret from text?
* example from https://lightning.readthedocs.io/BACKUP.html#backing-up-your-c-lightning-node:
    ```
    cat > hsm_secret_hex.txt <<HEX
    00: 30cc f221 94e1 7f01 cd54 d68c a1ba f124
    10: e1f3 1d45 d904 823c 77b7 1e18 fd93 1676
    HEX
    xxd -r hsm_secret_hex.txt > hsm_secret

    # move in place (will overwrite! - remove the ##)
    ## sudo mv /home/bitcoin/.lightning/bitcoin/hsm_secret

    # fix the owner and tighten permissions
    sudo chown bitcoin:bitcoin  /home/bitcoin/.lightning/bitcoin/hsm_secret
    chmod 0400  /home/bitcoin/.lightning/bitcoin/hsm_secret
    ```

### Channel database
* Stored on the disk and synchronised to the SDcard with the help of the `backup` plugin.

## Recovery
* https://lightning.readthedocs.io/FAQ.html#database-corruption-channel-state-lost
* https://lightning.readthedocs.io/FAQ.html#loss
### Recover from a cl-rescue file
* use the `REPAIR-CL` - `FILERESTORE` option in the menu for instructions to upload

### Recover from a seed
* use the `REPAIR-CL` - `SEEDRESTORE` option in the menu for instructions to paste the seedwords to restore
* or use the manual commands
  ```
  # stop CLN
  sudo systemctl stop lightningd

  # change to the bitcoin user
  sudo su - bitcoin

  # generate the hsm_secret in temporary directory from your CLN seed words (follow the instructions)
   lightning-hsmtool generatehsm /dev/shm/hsm_secret

  # backup your old hsm_secret and channel database
  mkdir /home/bitcoin/.lightning/bitcoin/old_node
  mv /home/bitcoin/.lightning/bitcoin/** /home/bitcoin/.lightning/bitcoin/old_node/

  # move the new hsm_secret in place
  mv /dev/shm/hsm_secret /home/bitcoin/.lightning/bitcoin/

  # back to admin
  exit

  # start lightningd
  sudo systemctl start lightningd

  # show the logs
  cllog
  ```

### Emergency recovery in case of lost channel states

* blogpost: <https://blog.blockstream.com/core-lightning-v0-12-0/>
* demo video: https://youtu.be/zBmEieZuS8Q
* manpage: <https://lightning.readthedocs.io/lightning-emergencyrecover.7.html>
   ```
   lightning-cli help emergencyrecover
   ```

1. [Restore the hsm_secret (onchain wallet keys) from seed](#recover-from-a-seed) (or hex).
   * There is no need to wait for the (few hours) rescan to finish, but can follow it any time with:
    ```
    cllog
    ```
1. Upload and copy the emergency.recover file in place

    * upload the file with scp:
    ```
    scp hsm_secret emergency.recover admin@RASPIBLITZ_IP:~/
    ```
    * copy it from `/home/admin/`:
    ```
    sudo cp /home/admin/emergency.recover /home/bitcoin/.lightning/bitcoin/
    sudo chown bitcoin:bitcoin /home/bitcoin/.lightning/bitcoin/emergency.recover
    ```
1. Recover

    * run (as admin or bitcoin user):
    ```
    lightning-cli emergencyrecover
    ```
    * a list of channelID-s should be returned if it worked:
    ```
    {
       "stubs": [
          "................",
       ]
    }
    ```
1. See more data about the recovered funds and channels
   ```
   lightning-cli listfunds
   lightning-cli listpeers
   ```
   * List the funding txid-s:
   ```
   lightning-cli listfunds | jq -r '.channels[] | .funding_txid'
   ```
   Can check the txid-s in a mempool explorer. If one is spent that channel is already closed.

### Restore a CLN node from the database backup on the SDcard
* https://gist.github.com/openoms/3516cd8f393d69d52f858c3d47c9e469

### Rescan the chain after restoring a used CLN wallet
* automatically done when using `SEEDRESTORE`
* controlled by the entry in the cln config file
* can use the `menu` -> `REPAIR` -> `REPAIR-CL` -> `RESCAN` option
* or follow the manual process:
  <https://lightning.readthedocs.io/FAQ.html#rescanning-the-block-chain-for-lost-utxos>
    ```
    # stop `lightningd`:
    sudo systemctl stop lightningd

    # the ungraceful method:
    sudo killall ligthningd

    # Rescan from the block 700000
    sudo -u bitcoin lightningd --rescan -700000 --log-level debug

    # Rescan the last 1000 blocks:
    sudo -u bitcoin lightningd --rescan 1000 --log-level debug
    ```
* can monitor in a new window using the shortcut:
    ```
    cllog
    ```

### Guesstoremote to recover funds from force-closed channels
* <https://lightning.readthedocs.io/lightning-hsmtool.8.html>
    ```
    $ man lightning-hsmtool
    guesstoremote  p2wpkh node_id max_channel_dbid hsm_secret [password]
    Brute-force the private key to our funds from a remote unilateral close of a channel, in a case where we have lost all database data except for our hsm_secret.  The peer must be the one to close the channel (and the funds will remain unrecoverable until the channel is closed).  max_channel_dbid is your own guess on what the channel_dbid was, or at least the maximum possible value, and is usually no greater than the number of channels that the node has ever had.  Specify password if the hsm_secret is encrypted.
    ```
* Usage on the RaspiBlitz (example for mainnet):
    ```
    sudo -u bitcoin lightning-hsmtool guesstoremote p2wpkh-ADDRESS-bc1... PEER_NODE_ID 5000 /home/bitcoin/.lightning/bitcoin/hsm_secret
    ```
* The `p2wpkh-ADDRESS-bc1...` must a be a non-timelocked output. Shows with `OP_PUSHBYTES_20` in block explorers.
* The `max_channel_dbid` = 5000 is usually plenty, can set any higher number
* If the `hsm_secret` is encrypted give the password on the end

* Output if unsuccessful (the private key is not known):
    ```
    Could not find any basepoint matching the provided witness programme.
    Are you sure that the channel used `option_static_remotekey` ?
    *** stack smashing detected ***: terminated
    Aborted
    ```
* Output if successful:
    ```
    bech32      : bc1q......................................
    pubkey hash : 0123456789abcdef0123456789abcdef01234567
    pubkey      : 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01
    privkey     : 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
    ```
* To import the private key of the address in Electrum Wallet will need to convert to base58
    ```
    git clone https://github.com/matja/bitcoin-tool
    cd bitcoin-tool
    make test

    ./bitcoin-tool \
     --network bitcoin \
     --input-type private-key \
     --input-format hex \
     --input PASTE_THE_privkey_HERE \
     --output-type private-key-wif \
     --output-format base58check \
     --public-key-compression compressed
    ```
* Example output:
    ```
    KwFvTne98E1t3mTNAr8pKx67eUzFJWdSNPqPSfxMEtrueW7PcQzL
    ```
* To import to the Electrum Wallet use the `p2wpkh:` prefix:
  <https://bitcoinelectrum.com/importing-your-private-keys-into-electrum/>
  ```
  p2wpkh:KxacygL6usxP8T9cFSM2SRW5QsEg66bUQUEn997UWwCZANEe7NLT
  ```

## sqlite3 queries
* Query the reasons for force closes
    ```
    sudo -u bitcoin sqlite3 /home/bitcoin/.lightning/bitcoin/lightningd.sqlite3 'select short_channel_id, timestamp, cause, message from channel_state_changes inner join channels on channel_id = id where new_state = 7 order by timestamp'
    ```
* Query the reasons for cooperative channel closes
    ```
    sudo -u bitcoin sqlite3 /home/bitcoin/.lightning/bitcoin/lightningd.sqlite3 'select short_channel_id, timestamp, cause, message from channel_state_changes inner join channels on channel_id = id where new_state = 4 order by timestamp'
    ```

## Extract the private and public key from the hsm_secret file
<https://gist.github.com/openoms/0844cf2db807b85fbcffacf1a3fb53bd#file-readme-md>

## Update
### Update to a new CLN release
* See the tagged releases by the CLN team: [github.com/ElementsProject/lightning/releases](https://github.com/ElementsProject/lightning/releases)
* Will be able to update to new releases from the menu - `UPDATE` - `CL`
* Since downgrading the lightning database is not allowed the updated version will persist if the SDcard is reflashed.

### Experimental update to the latest master
* this won't persist in case the SDcard is reflashed so will need to manually update again.
* the command to use the built-in script to update to the last commit in the default branch is:
    ```
    config.scripts/cl.install.sh update
    ```
* if the database version is not compatible with the default version after a downgrade there will be an error message in `sudo journalctl -u lightningd` similar to:
    ```
    Refusing to migrate down from version 178 to 176
    ```
* in this case update to the next release from the menu or the latest master again with:
    ```
    config.scripts/cl.install.sh update
    ```

## sqlite3 queries
* Query the reasons for force closes
    ```
    sudo -u bitcoin sqlite3 /home/bitcoin/.lightning/bitcoin/lightningd.sqlite3 'select short_channel_id, timestamp, cause, message from channel_state_changes inner join channels on channel_id = id where new_state = 7 order by timestamp'
    ```

* Query the reasons for cooperative channel closes
    ```
    sudo -u bitcoin sqlite3 /home/bitcoin/.lightning/bitcoin/lightningd.sqlite3 'select short_channel_id, timestamp, cause, message from channel_state_changes inner join channels on channel_id = id where new_state = 4 order by timestamp'
    ```

## Script file help list
* generate a list of the help texts on a RaspiBlitz:
    ```
    cd /home/admin/config.scripts/
    ls cl*.sh > clScriptList.txt
    sed -i 's#^#./#g' clScriptList.txt
    sed -i 's#.sh#.sh -h#g' clScriptList.txt
    bash -x clScriptList.txt
    rm clScriptList.txt
    ```

    ```
    + ./cl.backup.sh -h

    ---------------------------------------------------
    CL RESCUE FILE (tar.gz of complete cl directory)
    ---------------------------------------------------
    cl.backup.sh cl-export
    cl.backup.sh cl-export-gui
    cl.backup.sh cl-import [file]
    cl.backup.sh cl-import-gui [setup|production] [?resultfile]
    ---------------------------------------------------
    SEED WORDS
    ---------------------------------------------------
    cl.backup.sh seed-export-gui [clseeddata]
    cl.backup.sh seed-import-gui [resultfile]
    ---------------------------------------------------
    RECOVERY
    ---------------------------------------------------
    cl.backup.sh [mainnet|signet|testnet] recoverymode [on|off|status] <-rescanbockheight|rescandepth>

    + ./cl.check.sh -h

    # script to check CL states
    # cl.check.sh basic-setup
    # cl.check.sh prestart [mainnet|testnet|signet]

    + ./cl.hsmtool.sh -h

    Create new wallet or import seed
    Unlock/lock, encrypt, decrypt, set autounlock or change password for the hsm_secret

    Usage:
    Create new wallet:
    cl.hsmtool.sh [new] [mainnet|testnet|signet] [?seedpassword]
    cl.hsmtool.sh [new-force] [mainnet|testnet|signet] [?seedpassword]
    There will be no seedpassword(passphrase) used by default
    new-force will backup the old wallet and will work without interaction

    cl.hsmtool.sh [seed] [mainnet|testnet|signet] ["space-separated-seed-words"] [?seedpassword]
    cl.hsmtool.sh [seed-force] [mainnet|testnet|signet] ["space-separated-seed-words"] [?seedpassword]
    The new hsm_secret will be not encrypted if no NewPassword is given
    seed-force will delete any old wallet and will work without dialog

    cl.hsmtool.sh [unlock] <mainnet|testnet|signet> <password>
        success: exit 0
        wrong password: exit 2
        fail to unlock after 1 minute + show logs: exit 3
    cl.hsmtool.sh [lock] <mainnet|testnet|signet>
    cl.hsmtool.sh [encrypt|decrypt] <mainnet|testnet|signet>
    cl.hsmtool.sh [autounlock-on|autounlock-off] <mainnet|testnet|signet>

    cl.hsmtool.sh [change-password] <mainnet|testnet|signet> <NewPassword>

    + ./cl.install-service.sh -h

    Script to set up or update the Core Lightning systemd service
    Usage:
    /home/admin/config.scripts/cl.install-service.sh <mainnet|testnet|signet>

    + ./cl.install.sh -h

    Core Lightning install script
    The default version is: v22.11.1
    mainnet / testnet / signet instances can run parallel

    Usage:
    cl.install.sh install - called by build_sdcard.sh
    cl.install.sh on <mainnet|testnet|signet>
    cl.install.sh off <mainnet|testnet|signet> <purge>
    cl.install.sh [update <version>|testPR <PRnumber>]
    cl.install.sh display-seed <mainnet|testnet|signet>

    + ./cl.monitor.sh -h
    monitor and troubleshot the c-lightning network
    cl.monitor.sh [mainnet|testnet|signet] status
    cl.monitor.sh [mainnet|testnet|signet] config
    cl.monitor.sh [mainnet|testnet|signet] info
    cl.monitor.sh [mainnet|testnet|signet] wallet
    + ./cl-plugin.backup.sh -h

    Install the backup plugin for Core Lightning
    Replicates the lightningd.sqlite3 database on the SDcard

    Usage:
    cl-plugin.backup.sh [on|off] [testnet|mainnet|signet]
    cl-plugin.backup.sh [restore] [testnet|mainnet|signet] [force]
    cl-plugin.backup.sh [backup-compact] [testnet|mainnet|signet]

    https://github.com/lightningd/plugins/tree/master/backup

    + ./cl-plugin.clboss.sh -h

    Install or remove the CLBOSS Core Lightning plugin
    version: v0.13A
    Usage:
    cl-plugin.clboss.sh [on|off] [testnet|mainnet|signet]
    cl-plugin.clboss.sh [info]

    + ./cl-plugin.cln-grpc.sh -h

    Install the cln-grpc plugin for CLN
    Usage:
    cl-plugin.cln-grpc.sh install - called by build_sdcard.sh
    cl-plugin.cln-grpc.sh on <testnet|mainnet|signet>
    cl-plugin.cln-grpc.sh off <testnet|mainnet|signet> <purge>
    cl-plugin.cln-grpc.sh status <testnet|mainnet|signet>
    cl-plugin.cln-grpc.sh update <source>

    + ./cl-plugin.feeadjuster.sh -h

    Install the feeadjuster plugin for Core Lightning
    Usage:
    cl-plugin.feeadjuster.sh [on|off] <testnet|mainnet|signet>

    + ./cl-plugin.http.sh -h

    Install, remove, connect the c-lightning-http-plugin
    version: 1dbb6537e0ec5fb9b8edde10db6b4cc613ccdb19
    Implemented for mainnet only.
    Usage:
    cl-plugin.http.sh [on|off|connect] <norestart>

    + ./cl-plugin.sparko.sh -h

    Install, remove, connect or get info about the Sparko plugin for Core Lightning
    version: v2.8
    Usage:
    cl-plugin.sparko.sh [on|off|menu|connect] [testnet|mainnet|signet] [norestart]

    + ./cl-plugin.standard-python.sh -h

    Install and show the output of the chosen plugin for Core Lightning
    Usage:
    cl-plugin.standard-python.sh on [plugin-name] <testnet|mainnet|signet> <persist|runonce>

    tested plugins:
    summary | helpme | feeadjuster | paytest

    find more at:
    https://github.com/lightningd/plugins

    + ./cl-plugin.summary.sh -h

    Install and show the output if the summary plugin forCore Lightning
    Usage:
    cl-plugin.summary.sh [testnet|mainnet|signet] [runonce]

    + ./cl-plugin.watchtower-client.sh -h

    Install the rust-teos watchtower-client plugin for CLN
    Usage:
    cl-plugin.watchtower-client.sh on <testnet|mainnet|signet>
    cl-plugin.watchtower-client.sh off <testnet|mainnet|signet> <purge>
    cl-plugin.watchtower-client.sh info

    + ./cl.rest.sh -h

    Core-Lightning-REST install script
    The default version is: v0.9.0
    mainnet | testnet | signet instances can run parallel

    Usage:
    cl.rest.sh [on|off|connect] <mainnet|testnet|signet> [?key-value]

    + ./cl.setname.sh -h

    Config script to set the alias of the Core Lightning node
    cl.setname.sh [mainnet|testnet|signet] [?newName]

    + ./cl.spark.sh -h

    Install, remove or get info about the Spark Wallet for Core Lightning
    version: v0.3.1
    Usage:
    cl.spark.sh [on|off|menu] <testnet|mainnet|signet>

    + ./cl.update.sh -h

    Interim optional Core Lightning updates between RaspiBlitz releases.
    cl.update.sh [info|verified|reckless]
    info -> get actual state and possible actions
    verified -> only do recommended updates by RaspiBlitz team
        binary will be checked by signature and checksum
    reckless -> if you just want to update to the latest release
        published on Core Lightning GitHub releases (RC or final) without any
        testing or security checks.
    ```

## All possible config options
  *  can be shown by running:
  `lightningd --help`
  * To persist the settings place the options in the config file without the `--` and restart lightningd
    ```
    Usage: lightningd
    A bitcoin lightning daemon (default values shown for network: bitcoin).
    --conf=<file>                                     Specify configuration file
    --lightning-dir=<dir>                             Set base directory: network-specific subdirectory is under here (default: "/home/admin/.lightning")
    --network <arg>                                   Select the network parameters (bitcoin, testnet, signet, regtest, litecoin or litecoin-testnet) (default: bitcoin)
    --mainnet                                         Alias for --network=bitcoin
    --testnet                                         Alias for --network=testnet
    --signet                                          Alias for --network=signet
    --allow-deprecated-apis <arg>                     Enable deprecated options, JSONRPC commands, fields, etc. (default: true)
    --rpc-file <arg>                                  Set JSON-RPC socket (or /dev/tty) (default: "lightning-rpc")
    --plugin <arg>                                    Add a plugin to be run (can be used multiple times)
    --plugin-dir <arg>                                Add a directory to load plugins from (can be used multiple times)
    --clear-plugins                                   Remove all plugins added before this option
    --disable-plugin <arg>                            Disable a particular plugin by filename/name
    --important-plugin <arg>                          Add an important plugin to be run (can be used multiple times). Die if the plugin dies.
    --always-use-proxy <arg>                          Use the proxy always (default: false)
    --daemon                                          Run in the background, suppress stdout/stderr
    --wallet <arg>                                    Location of the wallet database.
    --large-channels|--wumbo                          Allow channels larger than 0.16777215 BTC
    --experimental-dual-fund                          experimental: Advertise dual-funding and allow peers to establish channels via v2 channel open protocol.
    --experimental-onion-messages                     EXPERIMENTAL: enable send, receive and relay of onion messages and blinded payments
    --experimental-offers                             EXPERIMENTAL: enable send and receive of offers (also sets experimental-onion-messages)
    --experimental-shutdown-wrong-funding             EXPERIMENTAL: allow shutdown with alternate txids
    --announce-addr-dns <arg>                         Use DNS entries in --announce-addr and --addr (not widely supported!) (default: false)
    --help|-h                                         Print this message.
    --rgb <arg>                                       RRGGBB hex color for node
    --alias <arg>                                     Up to 32-byte alias for node
    --pid-file=<file>                                 Specify pid file (default: "/home/admin/.lightning/lightningd-bitcoin.pid")
    --ignore-fee-limits <arg>                         (DANGEROUS) allow peer to set any feerate (default: false)
    --watchtime-blocks <arg>                          Blocks before peer can unilaterally spend funds (default: 144)
    --max-locktime-blocks <arg>                       Maximum blocks funds may be locked for (default: 2016)
    --funding-confirms <arg>                          Confirmations required for funding transaction (default: 3)
    --cltv-delta <arg>                                Number of blocks for cltv_expiry_delta (default: 34)
    --cltv-final <arg>                                Number of blocks for final cltv_expiry (default: 18)
    --commit-time=<milliseconds>                       Time after changes before sending out COMMIT (default: 10)
    --fee-base <arg>                                  Millisatoshi minimum to charge for HTLC (default: 1000)
    --rescan <arg>                                    Number of blocks to rescan from the current head, or absolute blockheight if negative (default: 15)
    --fee-per-satoshi <arg>                           Microsatoshi fee for every satoshi in HTLC (default: 10)
    --htlc-minimum-msat <arg>                         The default minimal value an HTLC must carry in order to be forwardable for new channels
    --htlc-maximum-msat <arg>                         The default maximal value an HTLC must carry in order to be forwardable for new channel
    --max-concurrent-htlcs <arg>                      Number of HTLCs one channel can handle concurrently. Should be between 1 and 483 (default: 30)
    --max-dust-htlc-exposure-msat <arg>               Max HTLC amount that can be trimmed
    --min-capacity-sat <arg>                          Minimum capacity in satoshis for accepting channels (default: 10000)
    --addr <arg>                                      Set an IP address (v4 or v6) to listen on and announce to the network for incoming connections
    --bind-addr <arg>                                 Set an IP address (v4 or v6) to listen on, but not announce
    --announce-addr <arg>                             Set an IP address (v4 or v6) or .onion v3 to announce, but not listen on
    --disable-ip-discovery                            Turn off announcement of discovered public IPs
    --offline                                         Start in offline-mode (do not automatically reconnect and do not accept incoming connections)
    --autolisten <arg>                                If true, listen on default port and announce if it seems to be a public interface (default: true)
    --dev-allowdustreserve <arg>                      If true, we allow the `fundchannel` RPC command and the `openchannel` plugin hook to set a reserve that is below the dust limit.
                                                        (default: false)
    --proxy <arg>                                     Set a socks v5 proxy IP address and port
    --tor-service-password <arg>                      Set a Tor hidden service password
    --accept-htlc-tlv-types <arg>                     Comma separated list of extra HTLC TLV types to accept.
    --disable-dns                                     Disable DNS lookups of peers
    --encrypted-hsm                                   Set the password to encrypt hsm_secret with. If no password is passed through command line, you will be prompted to enter it.
    --rpc-file-mode <arg>                             Set the file mode (permissions) for the JSON-RPC socket (default: "0600")
    --force-feerates <arg>                            Set testnet/regtest feerates in sats perkw, opening/mutual_close/unlateral_close/delayed_to_us/htlc_resolution/penalty: if fewer
                                                        specified, last number applies to remainder
    --subdaemon <arg>                                 Arg specified as SUBDAEMON:PATH. Specifies an alternate subdaemon binary. If the supplied path is relative the subdaemon binary is
                                                        found in the working directory. This option may be specified multiple times. For example, --subdaemon=hsmd:remote_signer would use
                                                        a hypothetical remote signing subdaemon.
    --experimental-websocket-port <arg>               experimental: alternate port for peers to connect using WebSockets (RFC6455)
    --database-upgrade <arg>                          Set to true to allow database upgrades even on non-final releases (WARNING: you won't be able to downgrade!)
    --log-level <arg>                                 log level (io, debug, info, unusual, broken) [:prefix] (default: info)
    --log-timestamps <arg>                            prefix log messages with timestamp (default: true)
    --log-prefix <arg>                                log prefix (default: )
    --log-file=<file>                                 Also log to file (- for stdout)
    --version|-V                                      Print version and exit
    --fetchinvoice-noconnect                          Don't try to connect directly to fetch an invoice.
    --autocleaninvoice-cycle <arg>                    Perform cleanup of expired invoices every given seconds, or do not autoclean if 0
    --autocleaninvoice-expired-by <arg>               If expired invoice autoclean enabled, invoices that have expired for at least this given seconds are cleaned
    --autoclean-cycle <arg>                           Perform cleanup every given seconds
    --autoclean-succeededforwards-age <arg>           How old do successful forwards have to be before deletion (0 = never)
    --autoclean-failedforwards-age <arg>              How old do failed forwards have to be before deletion (0 = never)
    --autoclean-succeededpays-age <arg>               How old do successful pays have to be before deletion (0 = never)
    --autoclean-failedpays-age <arg>                  How old do failed pays have to be before deletion (0 = never)
    --autoclean-paidinvoices-age <arg>                How old do paid invoices have to be before deletion (0 = never)
    --autoclean-expiredinvoices-age <arg>             How old do expired invoices have to be before deletion (0 = never)
    --bitcoin-datadir <arg>                           -datadir arg for bitcoin-cli
    --bitcoin-cli <arg>                               bitcoin-cli pathname
    --bitcoin-rpcuser <arg>                           bitcoind RPC username
    --bitcoin-rpcpassword <arg>                       bitcoind RPC password
    --bitcoin-rpcconnect <arg>                        bitcoind RPC host to connect to
    --bitcoin-rpcport <arg>                           bitcoind RPC host's port
    --bitcoin-retry-timeout <arg>                     how long to keep retrying to contact bitcoind before fatally exiting
    --commit-fee <arg>                                Percentage of fee to request for their commitment
    --disable-mpp                                     Disable multi-part payments.
    --funder-policy <arg>                             Policy to use for dual-funding requests. [match, available, fixed]
    --funder-policy-mod <arg>                         Percent to apply policy at (match/available); or amount to fund (fixed)
    --funder-min-their-funding <arg>                  Minimum funding peer must open with to activate our policy
    --funder-max-their-funding <arg>                  Maximum funding peer may open with to activate our policy
    --funder-per-channel-min <arg>                    Minimum funding we'll add to a channel. If we can't meet this, we don't fund
    --funder-per-channel-max <arg>                    Maximum funding we'll add to a channel. We cap all contributions to this
    --funder-reserve-tank <arg>                       Amount of funds we'll always leave available.
    --funder-fuzz-percent <arg>                       Percent to fuzz the policy contribution by. Defaults to 0%. Max is 100%
    --funder-fund-probability <arg>                   Percent of requests to consider. Defaults to 100%. Setting to 0% will disable dual-funding
    --funder-lease-requests-only <arg>                Only fund lease requests. Defaults to true if channel lease rates are being advertised
    --lease-fee-base-sat <arg>                        Channel lease rates, base fee for leased funds, in satoshi.
    --lease-fee-base-msat <arg>                       Channel lease rates, base fee for leased funds, in satoshi.
    --lease-fee-basis <arg>                           Channel lease rates, basis charged for leased funds (per 10,000 satoshi.)
    --lease-funding-weight <arg>                      Channel lease rates, weight we'll ask opening peer to pay for in funding transaction
    --channel-fee-max-base-msat <arg>                 Channel lease rates, maximum channel fee base we'll charge for funds routed through a leased channel.
    --channel-fee-max-proportional-thousandths <arg>  Channel lease rates, maximum proportional fee (in thousandths, or ppt) we'll charge for funds routed through a leased channel.
                                                        Note: 1ppt = 1,000ppm
    --bookkeeper-dir <arg>                            Location for bookkeeper records.
    --bookkeeper-db <arg>                             Location of the bookkeeper database
    ```