--- Log opened Wed Mar 04 00:00:12 2020 00:58 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 01:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 01:09 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds] 01:11 -!- jonatack [~jon@37.171.110.92] has joined #c-lightning 01:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 258 seconds] 01:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 01:49 < darosior> vasild, zmn: hmm I should add a timeout here 01:49 < darosior> The io_loop would wait for the plugin's init forever ^^ 01:51 < darosior> Thanks niftynei and fiatjaf ! 01:53 < darosior> Oh that's interesting 02:00 -!- jonatack_ [~jon@37.167.199.192] has joined #c-lightning 02:03 -!- jonatack [~jon@37.171.110.92] has quit [Ping timeout: 258 seconds] 02:04 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 02:04 -!- kexkey [~kexkey@37.120.205.237] has quit [Ping timeout: 256 seconds] 02:10 < darosior> cdecker: when should we use #ifdef COMPAT_XXX over if (deprecated_apis) ? (context https://github.com/ElementsProject/lightning/pull/3560#pullrequestreview-368648801) 02:16 <@cdecker> Hm, good question, the COMPAT flags are mainly for developers so we recognize what to remove, deprecated_apis is for external to test against 02:16 <@cdecker> I presume you ask because of the `rpc_command` PR? 02:16 <@cdecker> That'd likely require both the compile flag and the option 02:16 <@cdecker> I'll amend accordingly 02:26 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Quit: Leaving] 02:34 < darosior> Yep I asked because of this 02:34 < darosior> Thanks 03:03 -!- jonatack_ [~jon@37.167.199.192] has quit [Ping timeout: 265 seconds] 03:03 -!- jonatack_ [~jon@213.152.161.25] has joined #c-lightning 03:08 -!- Maitor [~goban@gateway/tor-sasl/maitor] has quit [Ping timeout: 240 seconds] 03:08 -!- Maitor [~goban@gateway/tor-sasl/maitor] has joined #c-lightning 03:51 < fiatjaf> rusty: I don't understand it. I'm not asking for directions, just reading my internal channel graph. 03:54 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 04:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 04:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 04:20 -!- jonatack_ [~jon@213.152.161.25] has quit [Ping timeout: 256 seconds] 04:22 -!- jonatack_ [~jon@37.167.220.16] has joined #c-lightning 04:39 < vasild> fiatjaf: using DFS for lightning routes should work, but it won't find the shortest path. I can imagine it would end up with some crazy long routes. Why would you prefer DFS over Dijkstra? 04:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:18 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 05:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 05:24 < fiatjaf> vasild: because routes would be more random and more anonymous 05:26 < vasild> fiatjaf: then, I guess, it would make sense to couple DFS with some "must be sane, not too long or too expensive" restriction on the result. 05:27 < fiatjaf> haha yes 05:28 < vasild> if not then retry the DFS. I wonder if it would keep retrying for a long time before getting a sensible result, maybe worth experimenting with 05:29 < fiatjaf> with my total inexperience with graph algorithms I imagined that having fee + nhops limits would actually fit well with DFS, as these limits would naturally limit paths being explored and prevent total madness 07:22 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 07:43 < darosior> cdecker: Did you write the feerate smoothing or was it Rusty ? 07:45 < darosior> nevermind I self-answered my question ^^ 07:51 -!- jonatack_ [~jon@37.167.220.16] has quit [Quit: jonatack_] 07:51 -!- jonatack [~jon@37.167.220.16] has joined #c-lightning 08:10 -!- Maitor [~goban@gateway/tor-sasl/maitor] has quit [Remote host closed the connection] 08:11 -!- Maitor [~goban@gateway/tor-sasl/maitor] has joined #c-lightning 08:36 -!- vincenzopalazzo [~vincent@2607:fb90:4e35:422e:71d9:a300:270d:9a99] has joined #c-lightning 08:54 -!- vincenzopalazzo [~vincent@2607:fb90:4e35:422e:71d9:a300:270d:9a99] has quit [Ping timeout: 240 seconds] 09:32 -!- michaelfolkson [~textual@2a00:23c5:be01:b201:55fc:f43c:fed0:4fc6] has joined #c-lightning 09:37 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Remote host closed the connection] 09:39 -!- rafalcpp_ [~racalcppp@ip-178-211.ists.pl] has quit [Ping timeout: 255 seconds] 09:41 -!- rafalcpp_ [~racalcppp@ip-178-211.ists.pl] has joined #c-lightning 11:23 -!- x7268 [~ralph@110.150.129.62] has quit [Ping timeout: 256 seconds] 11:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 11:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 11:58 -!- vasild_ is now known as vasild 12:01 <@niftynei> can someone remind me what the C99 mode error is on travis for libwally? i feel like i saw an explanation of it somewhere but can't remember now 12:02 <@niftynei> it's impacting the CI job for #3556 https://travis-ci.org/ElementsProject/lightning/jobs/656309446 12:06 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 256 seconds] 12:06 -!- jonatack [~jon@37.167.220.16] has quit [Read error: Connection reset by peer] 12:08 < vasild> niftynei: hmm 12:10 < vasild> I do not know when it started happening, but maybe https://github.com/ElementsProject/lightning/commit/42d1d3b6 is supposed to fix it? 12:12 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 12:15 < vasild> niftynei: rebased #3556, lets see... 12:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 12:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 13:39 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 13:50 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 14:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:23 -!- michaelfolkson [~textual@2a00:23c5:be01:b201:55fc:f43c:fed0:4fc6] has quit [Quit: Sleep mode] 16:17 < k3tan> i wanted to move my c-lightning node to another machine 16:17 < k3tan> what do i need to back up in order to do this? 17:19 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:21 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 17:23 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:24 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 18:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 18:22 < fiatjaf> k3tan: ~/.lightning/bitcoin/lightningd.sqlite3 and ~/.lightning/bitcoin/hsm_secret 18:23 < fiatjaf> k3tan: but it is also a good idea to backup ~/.lightning/config and/or ~/.lightning/bitcoin/config 18:23 < fiatjaf> and .lightning/bitcoin/gossip_store 18:37 < zmnscpxj> do note that restoring and old lightningd.sqlite3 file is dangerous and you should really do something like replicate it in real-time 18:40 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 19:28 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 19:36 < k3tan> it's ok, i've closed all my channels, taken all my funds off, i'll just fire up a new node 19:37 < k3tan> thanks fiatjaf zmnscpxj 20:18 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 20:19 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 20:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 20:39 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 21:44 -!- k3tan [~ketan@unaffiliated/k3tan] has quit [Ping timeout: 246 seconds] 22:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 22:40 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 23:22 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 23:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] --- Log closed Thu Mar 05 00:00:12 2020