--- Log opened Mon Oct 19 00:00:51 2020 00:06 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 00:15 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 00:17 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 00:24 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds] 00:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:10 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:c8d8:3cff:298f:ce82] has joined #c-lightning 01:24 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 01:24 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 01:27 -!- jonatack [~jon@37.165.8.123] has joined #c-lightning 01:32 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 01:32 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 02:31 < m-schmoock> cdecker: what would be the best format to output a timestamp for a state change history via RPC? I find the way `getlog` commands formats timestamps a bit wired. Would rather have an ISO_8601 timestamp 02:31 < m-schmoock> same goes for `getlog` but I doubt we change that 02:33 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has joined #c-lightning 02:33 < m-schmoock> also we could improve on a channels 'status' array in listpeers, but again that can break RPC -.- 02:40 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has quit [Quit: will be back] 03:01 -!- jonatack [~jon@37.165.8.123] has quit [Read error: Connection reset by peer] 03:07 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:10 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:c8d8:3cff:298f:ce82] has quit [Quit: Leaving] 03:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:11 -!- vasild_ is now known as vasild 03:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 03:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 03:14 < m-schmoock> i'll add a `json_add_timeiso(stream, fieldname, ts)` helper for that 03:15 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 03:21 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 260 seconds] 03:48 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 04:51 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 05:08 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning 05:09 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds] 05:16 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 05:34 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 05:35 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 05:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 05:52 <@cdecker> Good idea, I like the ISO8601 format 👍 05:59 -!- asoltys [~root@s207-81-214-2.bc.hsia.telus.net] has quit [Quit: Lost terminal] 06:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 06:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 06:20 < m-schmoock> cdecker: what do you think of generating the tools/generate-wire.py with cython to C and checking those in. So then NO_PYTHON can always work unless we change the generators (not the definition)... https://cython.readthedocs.io/en/latest/src/userguide/source_files_and_compilation.html#compilation 06:21 < m-schmoock> just a funny idea I had ... 06:23 < m-schmoock> (because the generated files (i.e. wallet/db_sqlite3_sqlgen.c) change a lot more often than the generators 06:43 <@cdecker> True, but we 06:43 <@cdecker> 'd need to add python3-dev as a dependency anyway 06:45 <@cdecker> But honestly I don't think the `NO_PYTHON` mode is really all that useful (same goes for checked in generated files). It's a lot of work to work around a single dependency, while we leave others just sitting there. 06:45 <@cdecker> Hence my lack of enthusiasm regarding the NO_PYTHON configuration ;-) 07:11 -!- kexkey [~kexkey@89.36.78.182] has joined #c-lightning 07:52 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has joined #c-lightning 07:55 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 08:00 -!- jonatack [~jon@213.152.161.35] has joined #c-lightning 08:20 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has joined #c-lightning 08:20 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 08:25 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 08:26 < m-schmoock> yes, anyway I can at least now simply bisect all commits for missing generated files :D ... Since travis only tests the very last commit of a branch it can (and does) break in between 08:35 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 08:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:48 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Ping timeout: 256 seconds] 08:56 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds] 09:03 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 09:04 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 09:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 09:15 -!- mrostecki_ is now known as mrostecki 10:51 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #c-lightning 10:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds] 11:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 11:22 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.9] 11:36 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds] 12:01 < jasan> meeting in one hour 12:03 <@cdecker> Yep, since I missed last weeks spec meeting I'm watching my clock like a hawk :-) 12:13 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 272 seconds] 12:36 -!- jasan [~jasan@just.do.nothing.bublina.eu.org] has quit [Quit: jasan] 12:45 -!- jasan [~jasan@2001:470:6f:200:8825:7190:1ec9:90da] has joined #c-lightning 12:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 12:57 < rusty> https://meet.jit.si/CLightning-Open-Meeting in 3 minutes! 12:59 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 13:01 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 13:09 < jasan> cdecker: http://www.structuredprocrastination.com/ 13:16 < HelloShitty> Evening peeps 13:16 < m-schmoock> hey 13:16 < HelloShitty> How do I set dust limit in c-lightning? 13:16 < HelloShitty> I'm having some trouble with a firend to open channels with me 13:16 < HelloShitty> my friend gets an error saying the dust limits are not in line with each other or something like that 13:17 < HelloShitty> this happens when my friend tries to open a channel with me 13:17 < HelloShitty> https://i.ibb.co/cwPdGtD/photo-2020-10-19-13-31-34.jpg 13:18 < darosior> Well you need to open a bigger channel, fwiw channels that small are useless 13:20 < HelloShitty> darosior: no other way to be able to have open channels and not get those errors? 13:21 < HelloShitty> I'm experimenting things and didn't want big channels open so that if I screw up, I don't lose much 13:26 < HelloShitty> darosior: channel reserve and dust limit are 2 different things, no? 13:26 < darosior> Yeah, but related 13:27 < darosior> Re experimenting: Yeah i understand :) You may want to try with slightly bigger chans or testnet 13:28 < HelloShitty> I don't understand very well the description in the code 13:28 < HelloShitty> https://github.com/ElementsProject/lightning/blob/master/common/channel_config.h 13:28 < HelloShitty> lines 42 and 55 13:29 < HelloShitty> above those 2 lines are short descriptions 13:29 < HelloShitty> but I don't know if we can set those values via command line arguments or by placing them in the config file 13:29 < HelloShitty> or if they are calculated automatically 13:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 13:40 <@niftynei> hmm it looks like the dust limit in their node is a bit higher than what we consider dust 13:40 <@niftynei> the way that channel reserve is calculated is 1% of the channel balance, or the dust limit, which ever is greater 13:41 <@niftynei> it seems that we're (c-lightning) setting your channel reserve to the dust limit of 543, but then later fail to open the channel because we recognize that this would be below what they consider dust 13:42 <@niftynei> which is 573sats 13:42 < darosior> This is not the configuration, which main logic resides here https://github.com/ElementsProject/lightning/blob/master/lightningd/options.c . If you want to start reading the code i'd recommend starting here https://github.com/ElementsProject/lightning/blob/master/lightningd/lightningd.c :) 13:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 13:42 < darosior> Otherwise, see configuration help here https://lightning.readthedocs.io/lightningd-config.5.html (or `man lightningd-config`) 13:43 < HelloShitty> ok, I'll start with the help 13:43 <@niftynei> it seems like we could help head this off by setting the channel reserve to the larger of 1% of the channel balance, or the higher of the two channel dust-limits 13:43 < HelloShitty> then, I can look to the code and see if I can understand anything 13:43 -!- jasan [~jasan@2001:470:6f:200:8825:7190:1ec9:90da] has quit [Quit: jasan] 13:43 < HelloShitty> I would love to understand just 0.001% to be able to participate in one single line of code... heheh 13:44 < HelloShitty> But I'm dreaming to high, I guess 13:44 < HelloShitty> lol 13:44 <@niftynei> i mean, you could probably fix this issue lol 13:44 <@niftynei> here's where we set the reserve amount https://github.com/ElementsProject/lightning/blob/master/openingd/openingd.c#L211-L214 13:45 <@niftynei> note that we only compare against *our*, local, dust limit 13:48 < HelloShitty> oh, ok. But I'm not going to mess with anything. I just started with lightning network like a week ago. I have a lot to learn before I can delete a single char in this code. that's for sure 13:48 < HelloShitty> I can't even set a channel for inboun capacity. lol 13:48 <@niftynei> but then farther down, we check that our reserve is higher than their dust limit 13:48 <@niftynei> https://github.com/ElementsProject/lightning/blob/master/openingd/openingd.c#L896-L915 13:49 <@niftynei> which it isn't, so it fails 13:49 < HelloShitty> yes, I do understand that, My fear is that I have no idea what implications the slightest change would have in the entire code. 13:50 <@niftynei> well, this is definitely a bug 13:50 < HelloShitty> So, I'll first try to learn the basics and how to properly deal with my node and then maybe, and just maybe, I can thing of changing a line of codde 13:50 <@niftynei> and needs to be fixed 13:50 <@niftynei> i'll make an issue for it, thanks for the report! 13:50 < HelloShitty> You peeps find the bugs for me 13:50 < HelloShitty> lol 13:51 < HelloShitty> Not me 13:51 < HelloShitty> You actually noticed it. I thank you for doing that 13:53 < HelloShitty> niftynei: the style of code used in the repository must (as is it mandatory) that respect the format it has? 13:53 < HelloShitty> I hate to buildd functions and break the parameters into several lines 13:53 < HelloShitty> lol 13:53 < HelloShitty> as in line 211 13:53 < HelloShitty> here: https://github.com/ElementsProject/lightning/blob/master/openingd/openingd.c#L211-L214 13:54 <@niftynei> HelloShitty: what's your github alias? i'll tag you in this issue 13:54 < HelloShitty> @PsySc0rpi0n 13:54 < HelloShitty> I already have another issue there, started by darosior 13:55 <@niftynei> yeah, we break lines to fit within an 80char window size 13:55 < HelloShitty> looks like I'm kinda stumbling in every bug possible 13:55 < HelloShitty> lol 13:55 < HelloShitty> But in a certain way, I'm happy I'm stumbling againts them 13:55 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 13:56 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 13:56 <@niftynei> our style guide is here https://github.com/ElementsProject/lightning/blob/master/doc/STYLE.md 13:57 < HelloShitty> ok, thank you 13:57 < HelloShitty> So, is that bug as simple as it looks, to fix? 13:58 < HelloShitty> Is just to swap the parcels in line 213 ? 13:58 <@niftynei> ah. so. 13:58 <@niftynei> there are two cases that we call set_reserve 13:59 < HelloShitty> hum, ok 13:59 <@niftynei> one, we are the peer opening the channel. in that case, the code is perfectly correct 13:59 < HelloShitty> I need to read the other function aswell to see if I can understand 14:00 <@niftynei> in the other case, we are the peer who's having the channel opened to us. 14:00 < HelloShitty> I see. That's where the code needs the fix 14:00 <@niftynei> in that case, we need to use the dust_limit sent to us in their open_channel message 14:00 <@niftynei> https://github.com/ElementsProject/lightning/blob/master/doc/STYLE.md 14:00 < HelloShitty> and the dust-limit is always on the side of who's openening the channel, yes? 14:00 <@niftynei> oops, wrong link 14:00 <@niftynei> https://github.com/ElementsProject/lightning/blob/master/doc/STYLE.md 14:01 <@niftynei> https://github.com/ElementsProject/lightning/blob/master/openingd/openingd.c#L803 14:01 <@niftynei> ok that's the right one lol 14:01 < HelloShitty> :) 14:01 <@niftynei> in this case, yes 14:01 <@niftynei> you can tell based on this quote from the spec 14:01 <@niftynei> https://github.com/ElementsProject/lightning/blob/master/openingd/openingd.c#L898-L901 14:02 <@niftynei> anyway. to fix this, i'd probably change `set_reserve` to take an extra parameter -- the dust limit to use 14:02 <@niftynei> and then just pass in the correct dust-limit each place that it's called 14:03 * niftynei dusts hands 14:03 < HelloShitty> hum, ok. That looks easy for you to fix. Hope that is a uick fix 14:03 <@niftynei> haha 14:03 < HelloShitty> I'm too scared to mess with it. :) 14:04 <@niftynei> i was just about to ask you to ping me when you wanted a review :P 14:04 < HelloShitty> I'm not that confident 14:04 < HelloShitty> :) 14:04 < HelloShitty> I'm not sure this is the correct term 14:04 < HelloShitty> lol 14:05 < HelloShitty> confiddent is rather someone who listens to the other's secrets and problems, no? 14:05 <@niftynei> "I'm not that confident" is a correct usage of the word 'confident' 14:05 <@niftynei> confidant is someone who listens to other's secrets 14:06 < HelloShitty> ok, but I can read what you just suggested andd I can try to see if I could make the changes if it was a life or ddeath situation 14:06 <@niftynei> 🙃 14:06 < HelloShitty> :) 14:06 < HelloShitty> ahh ok. confidant... Slight difference, completely different meaning 14:08 < HelloShitty> I also need to take a look the the coding style. I always use a 'p' prepended to the parameter of a funciton, so that I know, anywhere in the code, that that vatriable is supposed to be a variable to be passed to a function 14:09 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:c8d8:3cff:298f:ce82] has joined #c-lightning 14:09 < HelloShitty> something like set_reserve(struct state* pstate) 14:10 < HelloShitty> Let me take a look to the code and see if I can folow your suggestion 14:16 <@niftynei> 👍 14:17 < HelloShitty> What data type has dust_limit? I spend more time searching for it than trying to do anything else. lol 14:17 < HelloShitty> It's a member of localconfig struct, if I'm not mistaken 14:18 < HelloShitty> localconf I mean. And localconf is a variable of type struct channel_config 14:19 < vincenzopalazzo> I think that dust_limit is a "struct amount_sat" https://github.com/ElementsProject/lightning/blob/57dd5be2fd9cca5df33acea4031b06d925d6275a/channeld/commit_tx.c#L17 14:20 < HelloShitty> hehe 14:20 < HelloShitty> I feel I'm going round and round 14:21 < HelloShitty> that line says that dust_limit is of type struct amount_sat 14:21 < HelloShitty> noow I would need to find how amount_sat is defined to check which data type woul be dust_limit 14:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 14:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 14:42 -!- kexkey [~kexkey@89.36.78.182] has quit [Ping timeout: 260 seconds] 15:03 -!- vincenzopalazzo [~vincent@2001:b07:6474:9d49:c8d8:3cff:298f:ce82] has quit [Quit: Leaving] 15:07 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:11 -!- vasild_ is now known as vasild 15:22 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 15:29 <@niftynei> right, it's a struct amount_sat data type 15:34 < HelloShitty> I have been searching the code for the correct data type for the dust_limit value 15:34 < HelloShitty> But I coulddn't find it yet 15:35 < HelloShitty> I'm such a noob and I really wanted to help and I would be really happy to be able to fix this, but I'm afraid I might not be up to the task, even if it's quite simple 15:35 < HelloShitty> It would be my very first time I would participate in such huge project 15:36 < HelloShitty> I think I understand what is required which is to let the set_reserve() function to know about the remote dust_limit, compare it to localconf->channel_reserve 15:38 < HelloShitty> and if localconf-channel_reserve is lower than remote ddust_limit, then set localconf-channel_reserve equal to remote dust limit 15:52 < HelloShitty> niftynei: still around? 15:55 < HelloShitty> If I understand, any lightning node has these 2 parameters, Channel_reserve and dust_limit. When one node opens a channel to another node, it must make sure that it's own channel reserve needs to be equal or greater than it's own ddust_limit 15:56 < HelloShitty> and I also, it needs to make sure that it's own channel_reserve is equal or greater than the other node dust_limit value 15:57 < HelloShitty> I changed a bit the set_reserve() function here in my laptop but I'm not sure if it makes any sense because I don't know if the above statement is true or even accurate 15:58 < HelloShitty> if it is, I just added another if statement checking if state->localconf.channel_reserve is less than the remote->localconf.dust_limit and if it is, then, set state->localconf.channel_reserve equal to remote->localconf.dust_limit 15:59 < HelloShitty> I just did this in my laptop. I changed nothing on github wahtsoever. But as I have no idea if this makes any sense, I don't even want to show what I did. lol. Maybe if it makes sense, I show it 16:00 < HelloShitty> Now it's time to got to bed. Thank you for helping 16:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:32 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Ping timeout: 240 seconds] 16:51 < rusty> HelloShitty: I can open a channel to you, what's your node? 17:07 <@niftynei> HelloShitty, if you don't mind could you check to see if this matches your logic? https://github.com/ElementsProject/lightning/pull/4141 17:37 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 17:42 < az0re> rusty: I've been recording the mempool feerate histogram and results of `estimatesmartfee` for various block targets every 3 minutes (with some interruptions) for almost two weeks now. I'm not sure how best to analyze it to find the best `normal` feerate. It's all JSON-formatted, though, and should be easy to process. Are you interested in the log? 17:43 < rusty> az0re: hmm, yes, but I'm swamped right now... 17:43 < az0re> OK no problem 17:44 < az0re> Just glad to know it's not pointless 17:44 < az0re> Also if you have anything else for me to record that might help analysis, let me know 18:05 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 18:06 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 18:08 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: No Ping reply in 210 seconds.] 18:10 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning 18:29 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 18:55 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving] 19:33 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 19:33 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 21:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 21:39 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 21:40 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 22:15 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 22:16 -!- sr_gi [~sr_gi@static-128-69-224-77.ipcom.comunitel.net] has joined #c-lightning 22:28 -!- jonatack [~jon@213.152.161.35] has quit [Ping timeout: 246 seconds] 22:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 22:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 22:59 -!- jonatack [~jon@213.152.162.10] has joined #c-lightning 23:00 < HelloShitty> niftynei: I'll check later when I get back home 23:00 < HelloShitty> heading to work now 23:00 < HelloShitty> thanks 23:32 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 23:57 -!- jasan [~jasan@2001:470:6f:200:ec29:2c49:5710:ccb6] has joined #c-lightning --- Log closed Tue Oct 20 00:00:52 2020