--- Log opened Wed Jan 02 00:00:10 2019 00:24 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 00:56 -!- rpickhardt [~rpickhard@i577BC2D7.versanet.de] has joined #c-lightning 01:04 <@cdecker> charltonh: we fuzz the amount that is being sent up to a maximum value of 0.5% (combined with the fees that are being paid). This allows us to better hide the source and destination of a payment 01:05 <@cdecker> By default `pay` will be willing to pay up to 100.5% of the desired amount, and those 0.5% are used for fees and amount fuzzing 01:06 <@cdecker> As for the inability to send back the same amount of satoshis, that might be due to the reserve value 01:07 <@cdecker> For more information about the reserve please refer to the spec here https://github.com/lightningnetwork/lightning-rfc/blob/a07dc3df3b4611989e3359f28f96c574f7822850/02-peer-protocol.md#rationale 01:07 <@cdecker> The TL;DR is that we don't allow a node to completely drain its side of the channel, because otherwise he would have no incentive not to attempt to cheat, since cheating would be free 01:08 <@cdecker> imho it's a bit of a mind-chess game that causes more trouble than it's really worth... 01:10 -!- nothingmuch [~user@213.152.162.149] has joined #c-lightning 01:40 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 02:04 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:09 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:31 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 02:45 < rpickhardt> @cdecker can you merge https://github.com/ElementsProject/lightning/pull/2139 today so that I can produce and release the video about the plugin system? 02:46 < blockstream_bot> [Christian Decker, Blockstream] Why is merging it into master a requirement for your video? 02:48 < rpickhardt> The plugin has to be accessible for people. In the video I would show them where it is located. 02:48 < rpickhardt> Of course I could always refer to a different plugin repository 02:49 < rpickhardt> But I thought the plugins should ship with c-lightning? 02:49 < rpickhardt> In the sense that users install c-lightning and have a selection of plugins they can choose from. 03:00 <@cdecker> Well, we need to curate the list of plugins that we ship with c-lightning by default anyway, so we'd need to have a nursery where the plugins can live until they get bundled anyway 03:03 <@cdecker> This is particularly important for plugins that expose some functionality to others (rpc passthrough) and has therefore to adhere to the naming convention and stability guarantee that we try to maintain 03:10 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds] 03:22 < rpickhardt> So this means I should publish the plugins in my own git repo since the process for shipping them with c-lightning is not clear yet? 03:23 < rpickhardt> Wasn't the idea that the plugin folder was for plugins that are automatically activated? So shipping third party plugins (even if they change the API) should not be such a big deal since users have to deliberately activate them? 03:24 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 03:24 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 03:25 < rpickhardt> In particular for the list funds plugin I would suggest to add it as a more advanced "hello world" or demo plugin as it demonstrates how to use the rpc interface in combination. But obviously it is up to you to decide that 03:29 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 03:29 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 04:49 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 04:49 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 04:54 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 05:08 <@cdecker> Especially for the python based plugins we may have the option of distributing them using pypi instead :-) 05:19 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 05:24 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 05:24 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 05:34 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 05:34 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 05:39 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 05:39 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 05:51 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 07:10 < jb55> rpickhardt cdecker: I think a wiki-like repo on github with a catalog of links to plugins would be neat. awesome-clightning-plugins or something. I agree there's not really a need to have them in the clightning repo itself... 07:20 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning 07:24 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 07:24 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 07:29 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 07:29 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 07:44 < rpickhardt> I will create a plugin repo then and try to maintain it (: 07:44 < rpickhardt> Will probably publish tomorrow 07:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 08:04 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 08:04 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 08:09 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 08:09 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 08:11 -!- deusexbeer [~deusexbee@095-129-175-192-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 272 seconds] 08:25 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving] 08:59 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 08:59 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 09:04 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 09:04 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 09:16 < charltonh> @cdecker: If you check the attached paste.ee you will see the amounts I'm using are well within those parameters. 11m sats available in channel and I'm trying to send 4m. 09:17 < charltonh> But one of the problems I have with CL are the fact that the error msgs still leave the users clueless on something like this. If amount fuzzing is causing transactions to not go through, a message should explain why or what happened. 09:30 -!- deusexbeer [~deusexbee@093-092-178-220-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 10:35 < ctrlbreak> Hey gents... what should my values for cltv-delta and cltv-final be on mainnet? 10:49 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 10:49 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 10:59 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 10:59 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 11:11 -!- rpickhardt [~rpickhard@i577BC2D7.versanet.de] has quit [Ping timeout: 240 seconds] 11:41 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 11:54 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 11:59 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 12:01 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 246 seconds] 12:03 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 12:09 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Quit: farmerwampum] 12:09 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 12:14 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Client Quit] 12:14 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 12:14 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 12:48 <@cdecker> ctrlbreak: current_height+delta so in the 556740+9 to 556740+1440 range 12:48 <@cdecker> ctrlbreak: cltv_final_delta should be 9 12:51 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning 12:52 < ctrlbreak> Thanks. It looks like current defaults for deltas are 14 & 10 (I've been trying to learn more in the interim) 13:12 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Read error: Connection reset by peer] 13:14 -!- farmerwampum [~farmerwam@184.75.209.90] has joined #c-lightning 13:55 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 14:11 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning 14:12 < t0mix> hello, is it possible to switch from tor to public state with c-lightning without closing existing channels? I guess, it's not.. but maybe? 14:13 < ctrlbreak> FWIW, my CL node has crashed 3 times today with : BROKEN: new_htlc_out:Input cltv_expiry 0 less than 557204? 14:13 < ctrlbreak> +2879.742334017 lightningd(14004):BROKEN: FATAL SIGNAL 6 (version v0.6.2-51-gd5aaa11) 14:13 < ctrlbreak> I notice its an open issue on github at https://github.com/ElementsProject/lightning/issues/2077 14:13 < ctrlbreak> any mitigations for the time being or anything I could provide that would help? 14:17 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:27 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 14:29 <@cdecker> We probably are just too aggressive in verifying the cltv_delta. Will see if we can disarm that and just fail the HTLC 14:39 <@cdecker> I'm guessing you didn't set a negative cltv_delta? 15:00 -!- ungenannter [~ungenannt@colin.chaoshosting.de] has quit [Quit: WeeChat 1.0.1] 15:02 -!- ungenannter [~ungenannt@colin.chaoshosting.de] has joined #c-lightning 15:04 < ungenannter> hello guys, is there any sensitive information which I should remove before posting logs ? 15:17 < ctrlbreak> cdecker: nope. My cltv configs are the current defaults. 15:18 < ctrlbreak> wtf... my CL node has crashed for a 4th time today. 15:27 < molz> cdecker, do you have the commit when c-lightning started this: charltonh: we fuzz the amount that is being sent up to a maximum value of 0.5% (combined with the fees that are being paid). This allows us to better hide the source and destination of a payment ? 15:28 < ctrlbreak> ... luckily I've had debugging turned on for most of these crashes... and they've ALL initiated from this peer: 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b 15:28 < molz> i tried to look for when this was changed in the commits and change logs but couldn't find it 15:29 < ctrlbreak> Ahhhh... it's Rompert.com? 15:29 < molz> but i noticed i paid more than the invoice issued by bitrefill a couple months ago, i thought bitrefill made me pay the fee 15:30 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 15:49 -!- farmerwampum_ [~farmerwam@cpe-107-9-138-59.neo.res.rr.com] has joined #c-lightning 15:52 -!- farmerwampum__ [~farmerwam@184.75.210.234] has joined #c-lightning 15:52 -!- farmerwampum [~farmerwam@184.75.209.90] has quit [Ping timeout: 272 seconds] 15:52 -!- farmerwampum__ is now known as farmerwampum 15:54 -!- farmerwampum_ [~farmerwam@cpe-107-9-138-59.neo.res.rr.com] has quit [Ping timeout: 272 seconds] 16:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 16:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 16:05 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 16:37 < ungenannter> molz, ctrlbreak: thats why i'm here. Had some crashes lately. Looks like its the same peer over here. 16:37 < molz> eh? 16:38 < molz> no i didn't have any crash 16:38 < ctrlbreak> I had to close my channel with them until the daemon crash is handled... 16:38 < ctrlbreak> whatever 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b is constructing could potentially be weaponized into a DoS??? :-( 16:40 < ctrlbreak> anyway... been at this for 11 hours now. Time to take a break for a while. Cheers. 16:40 < ungenannter> molz: sorry, my mistake :) 16:40 < molz> oh ok :P 16:42 < molz> ctrlbreak, lol that is rompert's node, what's it doing? 16:44 < ctrlbreak> I don't know... but every single crashdump I have (all the way back to NOV) indicates that it is communication from that node that is hitting this issue: https://github.com/ElementsProject/lightning/issues/2077 16:44 < molz> oh really? lol tell rompert :D 16:45 < molz> let me ping him, he's probably sleeping now but he'll let us know when he wakes up 16:45 < ctrlbreak> I don't know how and wanted to get some more information from here/devs first? :-S 16:45 < molz> maybe rompert wants to bring down the world of clightning.. haha jk 16:49 < ctrlbreak> ok... done for the day, for real. Cheers guys. 17:10 -!- deusexbeer [~deusexbee@093-092-178-220-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 17:16 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 17:39 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 17:59 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 18:41 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 19:08 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds] 21:26 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-muhzynlsjblcoded] has left #c-lightning [] 21:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-muhzynlsjblcoded] has joined #c-lightning --- Log closed Thu Jan 03 00:00:10 2019