From 37583d8c9ccfefed73b1f124d6ba551410e408f8 Mon Sep 17 00:00:00 2001 From: Colin Date: Sat, 6 Jan 2024 18:08:51 +0000 Subject: [PATCH] clightning: tune fees, logging --- .../services/cryptocurrencies/clightning.nix | 16 +++++++++++++++- secrets/servo/lightning-config.bin | 6 +++--- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/hosts/by-name/servo/services/cryptocurrencies/clightning.nix b/hosts/by-name/servo/services/cryptocurrencies/clightning.nix index 36704a7d..78586749 100644 --- a/hosts/by-name/servo/services/cryptocurrencies/clightning.nix +++ b/hosts/by-name/servo/services/cryptocurrencies/clightning.nix @@ -8,6 +8,11 @@ # - guide: # - `sudo -u clightning -g clightning lightning-cli help` # +# debugging: +# - `lightning-cli getlog debug` +# - `lightning-cli listpays` -> show payments this node sent +# - `lightning-cli listinvoices` -> show payments this node received +# # first, acquire peers: # - `lightning-cli connect id@host` # where `id` is the node's pubkey, and `host` is perhaps an ip:port tuple, or a hash.onion:port tuple. @@ -29,6 +34,7 @@ # - # - # - tor nodes: +# - # - # - # - a few tor-capable nodes which allow channel creation: @@ -38,9 +44,11 @@ # - # - more resources: # - node routability: https://hashxp.org/lightning/node/ +# - especially, acquire inbound liquidity via lightningnetwork.plus's swap feature +# - most of the opportunities are gated behind a minimum connection or capacity requirement # # tune payment parameters -# - `lightning-cli setchannel id [feebase] [feeppm] [htlcmin] [htlcmax] [enforcedelay] [ignorefeelimits]` +# - `lightning-cli setchannel [feebase] [feeppm] [htlcmin] [htlcmax] [enforcedelay] [ignorefeelimits]` # - e.g. `lightning-cli setchannel all 0 10` # - it's suggested that feebase=0 simplifies routing. # @@ -52,6 +60,7 @@ # # to receive a payment (do as `clightning` user): # - `lightning-cli invoice