--- Log opened Sat Nov 26 00:00:28 2022
00:10 -!- Rodicurus [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has quit [Quit: Client closed]
00:11 -!- Rodicurus [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has joined #c-lightning
00:16 -!- NorrinRadd [~me@64.64.116.142] has quit [Ping timeout: 260 seconds]
00:17 < vincenzopalazzo> Rodicurus: the stacktrace is really unreadble on my client but I guess the problem is the pyln-client version. Try to run `pip3 install -r requirements.txt`
00:18 < vincenzopalazzo> or submit an issue by tagging me and I will take a look :)
00:23 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
00:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
01:14 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
01:15 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
01:30 < Rodicurus> this is what I got
01:30 < Rodicurus> $ pip3 install -r requirements
01:30 < Rodicurus> Defaulting to user installation because normal site-packages is not writeable
01:30 < Rodicurus> ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements'
01:31 < vincenzopalazzo> you miss the .txt
01:31 < vincenzopalazzo> and you need to run it inside the summery dir
01:34 < Rodicurus> Im lost please elaborate
01:35 < vincenzopalazzo> Ok, sorry!
01:36 < vincenzopalazzo> you need to move into the summary directory with cd path/to/summery and run pip3 install -r requiments.txt
01:36 < vincenzopalazzo>  * you need to move into the summary directory with cd path/to/summery and run pip3 install -r requirements.txt
01:38 < vincenzopalazzo> or also avoid to copy and paste my typo and use https://github.com/lightningd/plugins/blob/master/README.md#python-plugins-specifics
01:47 < Rodicurus> thanks this is what I get:    $ pip3 install -r requirements.txt
01:47 < Rodicurus> Defaulting to user installation because normal site-packages is not writeable
01:47 < Rodicurus> Requirement already satisfied: pyln-client>=0.12 in /home/rick/.local/lib/python3.9/site-packages (from -r requirements.txt (line 1)) (0.12.1)
01:47 < Rodicurus> Requirement already satisfied: requests>=2.10.0 in /usr/lib/python3/dist-packages (from -r requirements.txt (line 2)) (2.25.1)
01:47 < Rodicurus> Requirement already satisfied: packaging>=14.1 in /home/rick/.local/lib/python3.9/site-packages (from -r requirements.txt (line 4)) (21.3)
01:47 < Rodicurus> Requirement already satisfied: pyln-bolt7>=1.0 in /home/rick/.local/lib/python3.9/site-packages (from pyln-client>=0.12->-r requirements.txt (line 1)) (1.0.246)
01:47 < Rodicurus> Requirement already satisfied: pyln-proto>=0.12 in /home/rick/.local/lib/python3.9/site-packages (from pyln-client>=0.12->-r requirements.txt (line 1)) (0.12.0)
01:47 < Rodicurus> Requirement already satisfied: PySocks!=1.5.7,>=1.5.6 in /home/rick/.local/lib/python3.9/site-packages (from requests>=2.10.0->-r requirements.txt (line 2)) (1.7.1)
01:47 < Rodicurus> Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in /home/rick/.local/lib/python3.9/site-packages (from packaging>=14.1->-r requirements.txt (line 4)) (3.0.9)
01:47 < Rodicurus> Requirement already satisfied: coincurve<18.0.0,>=17.0.0 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (17.0.0)
01:47 < Rodicurus> Requirement already satisfied: cryptography<37.0.0,>=36.0.1 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (36.0.2)
01:47 < Rodicurus> Requirement already satisfied: base58<3.0.0,>=2.1.1 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (2.1.1)
01:47 < Rodicurus> Requirement already satisfied: bitstring<4.0.0,>=3.1.9 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (3.1.9)
01:47 < Rodicurus> Requirement already satisfied: asn1crypto in /home/rick/.local/lib/python3.9/site-packages (from coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (1.5.1)
01:47 < Rodicurus> Requirement already satisfied: cffi>=1.3.0 in /home/rick/.local/lib/python3.9/site-packages (from coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (1.15.1)
01:47 < Rodicurus> Requirement already satisfied: pycparser in /home/rick/.local/lib/python3.9/site-packages (from cffi>=1.3.0->coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client>=0.12->-r requirements.txt (line 1)) (2.21)
01:48 < vincenzopalazzo> ah wait
01:48 < vincenzopalazzo> it is not merget jet https://github.com/lightningd/plugins/pull/402
01:49 < vincenzopalazzo> so there is bug, maybe cdecker can take a look to it before next tagged release
01:49 < vincenzopalazzo> for now the solution is pip3 install pyln-client
01:52 -!- laanwj [~laanwj@user/laanwj] has joined #c-lightning
01:57 < Rodicurus> and than I get          ......pip3 install pyln-client
01:57 < Rodicurus> Defaulting to user installation because normal site-packages is not writeable
01:57 < Rodicurus> Requirement already satisfied: pyln-client in /home/rick/.local/lib/python3.9/site-packages (0.12.1)
01:57 < Rodicurus> Requirement already satisfied: pyln-proto>=0.12 in /home/rick/.local/lib/python3.9/site-packages (from pyln-client) (0.12.0)
01:57 < Rodicurus> Requirement already satisfied: pyln-bolt7>=1.0 in /home/rick/.local/lib/python3.9/site-packages (from pyln-client) (1.0.246)
01:57 < Rodicurus> Requirement already satisfied: bitstring<4.0.0,>=3.1.9 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client) (3.1.9)
01:57 < Rodicurus> Requirement already satisfied: coincurve<18.0.0,>=17.0.0 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client) (17.0.0)
01:57 < Rodicurus> Requirement already satisfied: PySocks<2.0.0,>=1.7.1 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client) (1.7.1)
01:57 < Rodicurus> Requirement already satisfied: base58<3.0.0,>=2.1.1 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client) (2.1.1)
01:57 < Rodicurus> Requirement already satisfied: cryptography<37.0.0,>=36.0.1 in /home/rick/.local/lib/python3.9/site-packages (from pyln-proto>=0.12->pyln-client) (36.0.2)
01:57 < Rodicurus> Requirement already satisfied: asn1crypto in /home/rick/.local/lib/python3.9/site-packages (from coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client) (1.5.1)
01:57 < Rodicurus> Requirement already satisfied: cffi>=1.3.0 in /home/rick/.local/lib/python3.9/site-packages (from coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client) (1.15.1)
01:57 < Rodicurus> Requirement already satisfied: pycparser in /home/rick/.local/lib/python3.9/site-packages (from cffi>=1.3.0->coincurve<18.0.0,>=17.0.0->pyln-proto>=0.12->pyln-client) (2.21)
01:57 < Rodicurus> rick@Mildred:~/lightning/plugins/plugins/summary
01:58 < Rodicurus> and
01:58 < Rodicurus> 2022-11-26T09:54:17.715Z INFO    plugin-bcli: bitcoin-cli initialized and connected to bitcoind.
01:58 < Rodicurus> 2022-11-26T09:54:19.480Z INFO    lightningd: --------------------------------------------------
01:58 < Rodicurus> 2022-11-26T09:54:19.480Z INFO    lightningd: Server started with public key 03b58cf9d49d39902c50cfc53573609f272d9b3ef638269c26bb17166427d29550, alias SLEEPYGOPHER (color #03b58c) and lightningd v0.11.2
01:58 < Rodicurus> 2022-11-26T09:54:19.482Z INFO    plugin-summary.py: Plugin summary.py initialized
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py: Traceback (most recent call last):
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.local/lib/python3.9/site-packages/pyln/client/plugin.py\", line 639, in _dispatch_request
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     result = self._exec_func(method.func, request)
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.local/lib/python3.9/site-packages/pyln/client/plugin.py\", line 616, in _exec_func
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     ret = func(*ba.args, **ba.kwargs)
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.lightning/plugins/summary/summary.py\", line 103, in summary
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     peers = plugin.rpc.listpeers()
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.local/lib/python3.9/site-packages/pyln/client/lightning.py\", line 999, in listpeers
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     return self.call(\"listpeers\", payload)
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.local/lib/python3.9/site-packages/pyln/client/lightning.py\", line 384, in call
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     resp, buf = self._readobj(sock, buf)
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/home/rick/.local/lib/python3.9/site-packages/pyln/client/lightning.py\", line 312, in _readobj
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:     obj, _ = self.decoder.raw_decode(parts[0].decode(\"UTF-8\"))
01:58 < Rodicurus> 2022-11-26T09:55:45.459Z INFO    plugin-summary.py:   File \"/usr/lib/python3.9/json/decoder.py\", line 353, in raw_decode
01:59 < vincenzopalazzo> could you please stop to put stacktrace inside IRC I will ignore it because it is unreadeble, sorry! try to use https://codepaste.xyz
02:03 < Rodicurus> https://codepaste.xyz/posts/l8CifS0oY2D6NBJ1lqta
02:05 < vincenzopalazzo> ok the important line is TypeError: int() argument must be a string, a bytes-like object or a number, not 'dict' I think you should report the issue, and including your cln version
02:07 < laanwj> is it new behavior that "blockheight" in getinfo shows 0 blocks for a while, while syncing? or did i just not notice before
02:07 < vincenzopalazzo> orionwl: It is a bug :D
02:08 < vincenzopalazzo> or a feature
02:08 < laanwj> oh, thanks! 
02:08 < vincenzopalazzo> yeah sorry I noted it for a while but I did not put my self to debug it, we introduce it 2 version a go
02:10 < laanwj> it was initially slightly worring to me ("oh no it didn't start syncing from scratch did it") but looking at bitcoin-cli processes i soon noticed it was fetching recent blocks
02:11 -!- NorrinRadd [~me@85.237.194.149] has joined #c-lightning
02:13 < vincenzopalazzo> yeah this usually happen when you did not run the node for a while (or I just noted the bug when I rerun a old node) and I think it is also the reason to have this bug hide in the dark 
02:14 < laanwj> it's exactly that
02:14 < Rodicurus> report it to who?
02:15 < vincenzopalazzo> well I think i need just to debug it now that I had the reproducible, I think using rescan=1000 should ne enough
02:15 < vincenzopalazzo> Rodicurus: on Github
02:23 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
02:25 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
02:34 -!- busch_ [~busch@mail.datenschleuder.com] has quit [Quit: Bye]
02:35 -!- busch [~busch@tunnel544981-pt.tunnel.tserv18.dus1.ipv6.he.net] has joined #c-lightning
02:42 -!- NorrinRadd [~me@85.237.194.149] has quit [Ping timeout: 264 seconds]
02:44 < cdecker[m]> The blockheight only gets updated once we caught up with the Blockchain head since there are some actions in plugins that rely on it as timing information. It's a bit convoluted and an IBD or sync flag could also have worked I guess. The downside is for long syncs you don't have any progress indication on the RPC, only logs
02:48 < vincenzopalazzo> cdecker[m]: oh ok, so we change into this new behavior? it is not a regression. However, this isn't very clear because with tor this can take hours. Why we can not keep a ui_blk_height filed just for getinfo?
02:50 < vincenzopalazzo> there are use case where this information is useful, e.g with remote connection you are not able to see the log
02:56 < cdecker[m]> It's more that `gossipd` relies on the RPC to check gossip, and we have races where lightningd has processed a block, passes it on to gossipd but gossipd rejects gossip for that block in the meantime (thinking the block was processed in both, missing the utxos from that block and rejecting gossip accordingly). So we only update the display counter once we bounce through gossipd
02:58 < vincenzopalazzo> ah ok make sense
02:58 < vincenzopalazzo> I missed this fix
02:58 < vincenzopalazzo> so it was a feature not a bug :D
03:08 < laanwj> thanks, that makes sense, it's why i didnt make a github issue, wasn't sure it was actually unwanted behavior
03:10 < vincenzopalazzo> However at this point from UX point of view we can make the blockheight and use the warning as method to notify the user
03:28 < vincenzopalazzo> *can make the blockheight an optional field
05:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:31 < Rodicurus> and so summary.py is not usable? for the foreseeable?
06:53 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
06:54 -!- jespada [~jespada@nmal-24-b2-v4wan-166357-cust1764.vm24.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
07:36 -!- jonatack2 [~jonatack@user/jonatack] has joined #c-lightning
07:46 -!- NorrinRadd [~me@64.64.116.142] has joined #c-lightning
07:48 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
07:49 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
07:54 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds]
07:55 -!- jonatack2 [~jonatack@user/jonatack] has joined #c-lightning
08:55 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds]
08:56 -!- jarthur [~jarthur@user/jarthur] has quit [Read error: Connection reset by peer]
08:56 -!- jarthur_ [~jarthur@user/jarthur] has joined #c-lightning
09:37 -!- jonatack2 [~jonatack@user/jonatack] has joined #c-lightning
09:40 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
09:43 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
09:46 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
09:47 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
09:59 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 255 seconds]
09:59 -!- NorrinRadd [~me@64.64.116.142] has quit [Ping timeout: 264 seconds]
10:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
10:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
10:13 < grubmn> is there no way to run a postgresql and sqlite db concurrently with --wallet? 
10:13 < grubmn> and then specify the postgresql db as the "main" db while dropping the sqlite db?
11:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
11:34 -!- jarthur_ is now known as jarthur
11:39 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
11:41 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
11:49 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
11:50 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
12:04 < grubmn> would anything break if i enabled write-ahead logging for the lightningd.sqlite3 database? https://sqlite.org/wal.html
12:06 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
12:06 < grubmn> oh this actually instructs users to enable it for litestream replication: https://github.com/ElementsProject/lightning/blob/master/doc/BACKUP.md#sqlite-litestream-replication
12:06 < grubmn> hmmm
12:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
12:11 < grubmn> i'm asking for those running on HDDs. running bitcoind / elementsd / lightningd all on the same disks can really impact IO performance evidently. i'm looking for ways to squeeze out any additional IO performance. 
12:30 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
12:34 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
13:24 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
13:25 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
14:10 -!- Rodicurus [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has quit [Quit: Client closed]
14:12 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
14:18 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
15:09 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
15:12 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
15:25 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
15:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 255 seconds]
15:56 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
15:59 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
16:00 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
16:48 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
16:51 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
16:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
16:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:09 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
17:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
17:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
17:35 -!- Rodicurus [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has joined #c-lightning
17:57 -!- Rodicurus15 [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has joined #c-lightning
17:59 -!- Rodicurus15 [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has quit [Client Quit]
17:59 -!- Rodicurus [~Rodicurus@2406:3400:23e:6e00:e1e5:5d3a:832d:d880] has quit [Quit: Client closed]
18:36 < grubmn> hmmm fiatjaf wrote a sqlite3 -> postgresql migration tool https://github.com/fiatjaf/mcldsp
18:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
18:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
19:09 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
19:11 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
19:40 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
19:42 -!- jonatack2 [~jonatack@user/jonatack] has joined #c-lightning
19:51 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
19:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
20:03 -!- jonatack2 [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds]
20:05 -!- jonatack2 [~jonatack@user/jonatack] has joined #c-lightning
21:33 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Quit: Leaving]
21:35 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
22:06 -!- rusty [~rusty@115-166-20-247.tpgi.com.au] has joined #c-lightning
22:10 -!- rusty [~rusty@115-166-20-247.tpgi.com.au] has quit [Ping timeout: 264 seconds]
22:44 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
22:49 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning
23:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
23:18 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
23:19 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
--- Log closed Sun Nov 27 00:00:29 2022