--- Log opened Sat Jul 31 00:00:24 2021
00:15 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 272 seconds]
01:11 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
01:30 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 240 seconds]
01:39 -!- lxer [~lx@95.91.246.102] has joined #c-lightning
02:06 < michaelfolkson> c-lightning config question for pyln-client https://bitcoin.stackexchange.com/questions/107838/how-can-i-access-remote-lightningd-with-pyln-client
02:25 < cdecker[m]> Answered 🙂
02:42 < michaelfolkson> Thanks :)
02:43 -!- belcher_ is now known as belcher
02:45 < michaelfolkson> There are a couple more open (but please don't let me derail your day!)
02:45 < michaelfolkson> https://bitcoin.stackexchange.com/questions/107743/what-is-special-about-blocks-540574-and-564180
02:45 < michaelfolkson> https://bitcoin.stackexchange.com/questions/107636/how-to-replace-peer-id-with-alias-in-c-lightning
02:47 < vincenzopalazzo> The response to this question https://bitcoin.stackexchange.com/questions/107636/how-to-replace-peer-id-with-alias-in-c-lightning is somethings that I want propose with one PR after the version 0.10.1 is relased
02:48 < vincenzopalazzo> The only method that I know to get the information about the alias is made the join of the json payload provided by listpeers and listchannles
02:48 < vincenzopalazzo> Have more information of the node I think it is good to proposo as JSON format change
03:00 < cdecker[m]> Pretty much, they access different data stores (listforwards uses the DB, whereas listnodes uses the gossmap) so you'd likely have to merge them in a plugin (could implement that as an rpc_command hook to change the result of listforwards in-flight)
04:18 < vincenzopalazzo> Christian Decker: Ah this is my design fault. Ok this is better to make a plugin that make this join phase. I will push in the side project queue :) Thanks to point me out this differences
05:50 -!- Victorsueca [~Victorsue@90.165.120.190] has joined #c-lightning
06:22 < nathanael> cdecker[m]: thanks for answering the question about the two "special blocks" - is the btc-rpc-proxy you mention the rust implementation here: https://github.com/Kixunil/btc-rpc-proxy ?
06:42 < vincenzopalazzo> btc-rpc-proxy it is a really cool library, I need to understend it and maybe I can integrate in my java plugin to override the bitcoin backend
06:43 < vincenzopalazzo> however, nathanael if you want use a bitcoin backend plugin that enable the pruning mode you can run the btcli4j plugin https://github.com/clightning4j/btcli4j
06:44 < nathanael> vincenzopalazzo: hmm, thanks - i saw it, but i am not a big fan of java, but also not rust - will see what i will use
06:45 < nathanael> not decided yet
06:45 < nathanael> i hope at some point c-lightning will support pruned nodes on its own
06:45 < vincenzopalazzo> nathanael: I understend :) I will made a porting of this implementation in a language like rust, and/or golang. But not sure when yet :) 
06:46 < nathanael> vincenzopalazzo: cool - yeah time is limited ;)
06:46 < cdecker[m]> That's the one nathanael 👍
06:46 < nathanael> thanks - perfect
08:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
11:07 -!- jarthur [~jarthur@2603-8080-1540-002d-7505-cb9f-3992-4528.res6.spectrum.com] has joined #c-lightning
11:29 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning
13:43 < ufotofu> so on 0.10.1rc2, `decode` successfully decodes a bolt12, but errors with the following message when trying to pay the invoice
13:43 < ufotofu> "message": "Invalid bolt12: unexpected prefix lno"
15:32 -!- lxer [~lx@95.91.246.102] has quit [Ping timeout: 258 seconds]
15:46 -!- aechu [~major@gateway/tor-sasl/major] has quit [Remote host closed the connection]
15:46 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
17:13 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning
17:17 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 256 seconds]
18:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 244 seconds]
18:36 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
19:23 -!- jarthur_ [~jarthur@2603-8080-1540-002d-6954-6107-32c9-6eb8.res6.spectrum.com] has joined #c-lightning
19:25 -!- jarthur [~jarthur@2603-8080-1540-002d-7505-cb9f-3992-4528.res6.spectrum.com] has quit [Ping timeout: 272 seconds]
19:52 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 276 seconds]
19:53 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
20:15 -!- Jackielove4u [uid43977@user/jackielove4u] has joined #c-lightning
20:24 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 272 seconds]
20:26 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
20:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
21:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:03 -!- aechu [~major@gateway/tor-sasl/major] has quit [Remote host closed the connection]
21:03 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
21:56 -!- jarthur_ [~jarthur@2603-8080-1540-002d-6954-6107-32c9-6eb8.res6.spectrum.com] has quit [Quit: jarthur_]
23:07 -!- jarthur [~jarthur@2603-8080-1540-002d-5cd1-fa28-1e6f-abb1.res6.spectrum.com] has joined #c-lightning
23:21 -!- jarthur_ [~jarthur@2603-8080-1540-002d-1d4f-58cf-cdfb-06b1.res6.spectrum.com] has joined #c-lightning
23:24 -!- jarthur_ [~jarthur@2603-8080-1540-002d-1d4f-58cf-cdfb-06b1.res6.spectrum.com] has quit [Client Quit]
23:26 -!- jarthur [~jarthur@2603-8080-1540-002d-5cd1-fa28-1e6f-abb1.res6.spectrum.com] has quit [Ping timeout: 272 seconds]
--- Log closed Sun Aug 01 00:00:25 2021