--- Log opened Sat Jan 14 00:00:14 2023
00:13 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
02:03 -!- kexkey [~kexkey@static-198-54-132-142.cust.tzulo.com] has quit [Ping timeout: 260 seconds]
02:04 -!- kexkey [~kexkey@static-198-54-132-142.cust.tzulo.com] has joined #c-lightning
02:47 < xin3qu> I paused about a year experimenting with lightning; I remember problems when using dynamic IP-Addresses. Is it now possible to bind a node to an FQDN, so that channel partners find each other again even when both changed their IP? Pointer to documentation relating to this welcome.
02:53 < xin3qu> greves: had those problems when using dynamic DNS and an IP which changed every 24h. If you, with your changed IP, do not reconnect the peer won't find you anymore
03:21 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
03:23 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 255 seconds]
06:33 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
06:35 -!- jon_atack [~jonatack@user/jonatack] has joined #c-lightning
07:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
07:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
07:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
08:09 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
08:12 -!- jon_atack [~jonatack@user/jonatack] has joined #c-lightning
08:14 -!- DeanWeen is now known as DeanGuss
08:14 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host]
08:14 -!- DeanGuss [~dean@user/deanguss] has joined #c-lightning
09:38 -!- greves [~Guest77@36-230-141-135.dynamic-ip.hinet.net] has quit [Ping timeout: 260 seconds]
09:47 < vincenzopalazzo> <instagibbs> "what's the incantation for..." <- `check-proto` or something like that
09:47 < vincenzopalazzo>  
09:50 < vincenzopalazzo> you could also clone lnprototest in the same level of core lightning and run the following command `make check PYTEST_ARGS='--runner=lnprototest.clightning.Runner'` where you can add inside `PYTEST_ARGS` the `-k <name file or test>` 
09:50 < vincenzopalazzo> BTW right now lnprototest is broken, I will try to finish the patch next week
12:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
12:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
12:14 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning
15:46 -!- md56 [~md@node-1w7jra2ajz8fq5uhedazdfxz2.ipv6.telus.net] has joined #c-lightning
15:47 < md56> How do I prune lightning-cli listchannels
16:45 -!- md56 [~md@node-1w7jra2ajz8fq5uhedazdfxz2.ipv6.telus.net] has quit [Quit: Client closed]
17:58 -!- jon_atack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
17:58 -!- jon_atack [~jonatack@user/jonatack] has joined #c-lightning
20:10 -!- jarthur_ [~jarthur@user/jarthur] has joined #c-lightning
20:12 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 260 seconds]
20:13 -!- jarthur_ is now known as jarthur
23:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
23:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
--- Log closed Sun Jan 15 00:00:15 2023