--- Day changed Sat Feb 24 2018 00:07 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has joined #c-lightning 00:36 -!- almkglor [b4be239b@gateway/web/freenode/ip.180.190.35.155] has quit [Ping timeout: 260 seconds] 00:41 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:b84e:e48:2fa5:a689] has quit [Remote host closed the connection] 00:42 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:b84e:e48:2fa5:a689] has joined #c-lightning 00:47 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:b84e:e48:2fa5:a689] has quit [Ping timeout: 276 seconds] 01:37 -githubby:#c-lightning- [lightning] cdecker closed pull request #1084: Better handling bitcoin cli fail (master...better-handling-bitcoin-cli-fail) https://git.io/vAV2c 01:40 -githubby:#c-lightning- [lightning] cdecker pushed 4 new commits to master: https://git.io/vAVXT 01:40 -githubby:#c-lightning- lightning/master ac21ac3 Christian Decker: contrib: Add flake8 to builder container images... 01:40 -githubby:#c-lightning- lightning/master 68a9951 Christian Decker: contrib: Add pytest-reruns into the builder image... 01:40 -githubby:#c-lightning- lightning/master da062df Christian Decker: make: If running on travis allow 3 reruns of failed tests... 02:18 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1087: Add "make check-python" (flake8 check) (master...check-python) https://git.io/vAVMt 02:44 -githubby:#c-lightning- [lightning] cdecker closed pull request #1085: Avoid using undefined variable "name" in print_printwire_array(...). Fix PEP-8 violation. (master...undefined-variable-used-in-print_printwire_array) https://git.io/vAVo3 02:50 < provoostenator> State ONCHAIN, what's that? 02:51 < provoostenator> This comment could use more detail: https://github.com/ElementsProject/lightning/blob/master/lightningd/channel_state.h#L25 03:10 -!- BearShark [~BearShark@155.93.208.90] has joined #c-lightning 03:25 < BearShark> Can anyone help me with this? channel ALL: lightning_channeld: received ERROR channel 47aef2472bd5388428710167266dc95fc9801eb0f6afcdedcf56a7d3a9790b5f: update_fee 11000 outside range 15000-200000 03:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fjrznvzqvcuoxzwj] has quit [Quit: Connection closed for inactivity] 04:57 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:16 -githubby:#c-lightning- [lightning] arowser opened pull request #1090: Not pass '-static' to configurator on macOS (master...build_mac) https://git.io/vAV58 05:18 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 05:55 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 05:56 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 06:00 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:00 -!- shesek` [~shesek@bzq-84-110-53-17.cablep.bezeqint.net] has joined #c-lightning 06:01 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 248 seconds] 06:02 < rompert> dudes wtf is up with the fees? https://www.irccloud.com/pastebin/COovILD9/wtf 06:02 -!- dland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Remote host closed the connection] 06:03 -!- dland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:03 < rompert> i when i raise the maximum allowed percentage of fees, the fee increases... 06:06 -!- aj_ [aj@cerulean.erisian.com.au] has joined #c-lightning 06:09 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 264 seconds] 06:10 -!- aj [aj@cerulean.erisian.com.au] has quit [Ping timeout: 264 seconds] 06:10 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 06:11 < BearShark> rompert is the routing the same for each time you issue the command? 06:14 < rompert> no idea why it would change. can i see that on `pay` ? `getroute` shows the same path regardless of satoshis 06:15 < rompert> the payment goes thru just fine when i accept 10% fees :) 06:15 < rompert> still cheaper than onchain, so i'm not complaining 06:20 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 06:21 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 06:42 < BearShark> Was the node you sending to, routed "far away"? 06:44 < rompert> two nodes between. planning to connect directly and try again 06:44 < rompert> https://www.irccloud.com/pastebin/DsN3wjVy/ 06:45 < rompert> it doesn't seem to add much fees at all though 06:46 < rompert> and direct connection failed of course... 06:46 < rompert> $ cli/lightning-cli fundchannel 03457d3e97da4e6a01739f56c0cd168cb14962b91fb44dc3d647816c70e05e9b93 22000 06:46 < rompert> { "code" : -1, "message" : "received ERROR channel 953a8e35e6d5c0686a03036ba4fe66983d318565b7341237cd4d3d78ca446075: Unacceptable channel constraints: minimum HTLC value is too large: 0" } 06:54 < mlz> rompert, i got that error when trying to open a channel from a LND node to a c-lightning node 06:56 < rompert> mlz: hmm you mean the other way around, right? that error is from lnd i'm quite sure, because i lobotomized my lnd to get rid of it. but now i'm connecting from a clightning to a most probably lnd node (mainnet.yalls.org) 07:02 < mlz> rompert, i raised this issue with roasbeef yesterday, if you scroll up channel #lnd you will see the convo 07:07 < rompert> ok. hope he didn't just answer with ¯\_(ツ)_/¯ as usual :) 07:09 < rompert> hmmm you mean the `[lncli] rpc error: code = Code(202) desc = feerate_per_kw 6000 above maximum 1275` ? 07:10 < rompert> i think that is a different problem. i've raised that issue with roasbeef as well. 07:11 < rompert> the "HTLC value is too large: 0" is a different one... a very interesting one since 0 is seldom too *large* ... but i checked the code there, it gives that error in other cases as well, it is like last in an if-else-ladder or if-return whatever 07:12 < grubles> i think that error has something to do with lnd not recognizing sub-satoshi amounts? 07:14 < rompert> don't think it was, but i would lie if i'd say i figured it out. i just took those checks out and my node started to work again. 07:16 < rompert> ok then. one hop closer. let's try again 07:26 < rompert> ok almost the same. raised fees a few times. last time it didn't respond. tried again and it said payment was already in progress. then it crashed 07:26 < rompert> feels like monday today 07:28 < rompert> restarting and adding blocks from like last year or something... 07:29 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning 07:30 < rompert> oh happy days are back 07:34 < grubles> https://github.com/ElementsProject/lightning/issues/997#issuecomment-365569086 07:35 < grubles> i wasn't exactly right 07:36 < BearShark> Does anyone know a fix for the issue I'm currently having? I'm trying to connect two nodes together which already have open channels. 07:36 < BearShark> It returns with this: { "code" : -1, "message" : "channel ALL: lightning_channeld: received ERROR channel 47aef2472bd5388428710167266dc95fc9801eb0f6afcdedcf56a7d3a9790b5f: update_fee 11000 outside range 15000-200000" } 07:37 < grubles> not sure i've run into that error before 07:37 < BearShark> I've tried adjusting fees as it says, but it never works 07:55 -!- shesek` is now known as shesek 07:55 -!- shesek [~shesek@bzq-84-110-53-17.cablep.bezeqint.net] has quit [Changing host] 07:55 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 07:55 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Quit: Leaving] 08:17 < lxer> BearShark: you can set fee limits as commandline arguments 08:19 < lxer> ow. nm. 08:27 < BearShark> ixer i've tried that, still gives the same values 11k out of range of 15k-200k. when I set 200k... Something feels off here 08:39 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 08:40 -!- raichu [46c048d3@gateway/web/freenode/ip.70.192.72.211] has joined #c-lightning 08:40 < raichu> hey everyone 08:41 < mlz> rompert, that was just an example i could grab to tell roasbeef yesterday, but i already told him about other fee issues before and he said something about c-lightning has a strict policy on fees and it needs to relax the policy 08:41 < raichu> when i try to use lightning-cli help I get "Connecting to 'lightning-rpc': No such file or directory" 08:41 < BearShark> raichu restart lightningd 08:41 < raichu> but i've set the rpc file location using --rpc-file 08:42 < raichu> how? 08:42 < BearShark> Is the rpc file outside your lightning-dir folder? 08:42 < raichu> no i made sure it's in there 08:43 < BearShark> Ok then don't specify the rpc location, lightningd will do the defaults 08:43 < raichu> i think something is wrong with my lightningd... i've been using the github clightning guide 08:44 < raichu> and when I enter the command "lightningd/lightningd --network=testnet --log-level=debug" 08:44 < raichu> response is "lightningd/lightningd: No such file or directory" 08:44 < BearShark> are you sure you in the right directory? after compiling? 08:45 < raichu> ah 08:46 < raichu> well now i am, but error is: 08:46 < BearShark> If you are using lightningd/lightningd, make sure you are in the base level of the folder 08:46 < raichu> "Wallet blockchain hash does not match network blockchain hash: ####################################### != ################################################" 08:48 < BearShark> aa I can't help with that 08:49 < raichu> np 09:09 < rompert> mlz: okidoki. well at least the issue is known and they seem to work on it. 09:09 < mlz> oh cool.. where? 09:09 < mlz> there's a PR to fix it? 09:10 < rompert> mlz: i mean this one: https://github.com/cdecker/lightning-integration/issues/11 09:11 < rompert> s/work on/talk about/ :) 09:12 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:f8b8:8b18:c09e:f888] has joined #c-lightning 09:12 -!- raichu [46c048d3@gateway/web/freenode/ip.70.192.72.211] has quit [Ping timeout: 260 seconds] 09:13 < mlz> ah.. good to know at least it's there in the issues queue 09:17 < rompert> all will be well soon :) 09:18 < mlz> rompert, i don't quite understand this error, i've read the issue but don't understand it 09:19 < mlz> if we can get an answer from c-lightning code for this question then maybe someone can figure out how to fix it: 09:19 < rompert> the "minimum HTLC value is too large: 0" one ? issue 11 09:19 < rompert> ah. another :) 09:19 < mlz> "Hmm, yeh we do use an int64 for the min HTLC value. Are y'all setting the min HTLC to some maximum value? Is there any way to print out the accept_channel parameters y'all sent?" 09:21 < rompert> unfortunately my memory is bad, so i don't remember more than i said before. and no i don't understand it :) i think i debugged the value and it wasn't 0 09:28 < rompert> +if false && minHtlc > maxValueInFlight { 09:28 < rompert> + return fmt.Errorf("zminimum HTLC value is too large: %g %g", 09:28 < rompert> + r.ourContribution.MinHTLC.ToBTC(),maxValueInFlight.ToBTC()) 09:29 < rompert> this was my "fix" ... of course the "false &&" was added after i noticed... whatever i noticed... 09:31 < rompert> but you might be correct. maybe it was small values, and ToBTC didn't show it. or maxValueInFlight was negative, but i can't say i remember that it was. i probably would have remembered. sorry i'm a fix and forget type of guy. wasn't exactly going to make a PR out of it :) 10:25 -!- farmerwampum [~farmerwam@88.202.178.102] has joined #c-lightning 10:33 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:f8b8:8b18:c09e:f888] has quit [Remote host closed the connection] 10:34 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:f8b8:8b18:c09e:f888] has joined #c-lightning 10:38 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:f8b8:8b18:c09e:f888] has quit [Ping timeout: 240 seconds] 11:24 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Quit: Lost terminal] 11:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds] 12:32 -!- aj_ is now known as aj 13:01 -!- jb55 [~jb55@24.87.206.252] has joined #c-lightning 13:22 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 256 seconds] 13:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 14:15 < mlz> when we close a tx, does c-lightning give us a closing TXID? 14:33 < jojeyh> mlz, yes i remember closing a channel and eventually getting a closing txid 14:58 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 15:00 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 15:01 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 15:06 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 260 seconds] 15:15 -!- jb55 [~jb55@24.87.206.252] has quit [Ping timeout: 256 seconds] 15:21 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 15:26 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 252 seconds] 15:42 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 15:44 < mlz> rompert, aight found the source of that issue with c-lightning, should be pushed out inna bit 15:45 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 15:45 < mlz> jojeyh, i guess i have to wait for 144 blocks then i will find out 15:46 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 240 seconds] 15:53 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has quit [Ping timeout: 256 seconds] 16:03 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 16:07 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 252 seconds] 16:10 < jojeyh> mlz, lulz 16:23 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 16:28 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 256 seconds] 16:29 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qpvsrgutcoaiurte] has joined #c-lightning 16:31 -!- BearShark [~BearShark@155.93.208.90] has quit [Quit: Leaving] 16:44 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 16:48 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 245 seconds] 17:05 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 17:09 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 240 seconds] 17:19 -!- CubicEarths [~cubiceart@73.93.143.35] has joined #c-lightning 17:25 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has joined #c-lightning 17:30 -!- vogelito [~Adium@24-234-111-50.ptp.lvcm.net] has quit [Ping timeout: 256 seconds] 17:41 < mlz> what's the command to get info of another node key? 17:41 -!- bloxton [76d053ac@gateway/web/freenode/ip.118.208.83.172] has joined #c-lightning 17:44 < bloxton> Was that the real Laszlo that just posted on the lightning-dev mailing list? 17:57 -!- CubicEar_ [~cubiceart@2600:1010:b021:994b:5dda:8d14:3f1f:eec5] has joined #c-lightning 17:58 -!- CubicEarths [~cubiceart@73.93.143.35] has quit [Ping timeout: 248 seconds] 18:34 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #1094: wireaddr: Do hostname resolution in parse_wireaddr. (master...getaddrinfo-parse-wireaddr) https://git.io/vAwgo 18:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:48 -!- CubicEar_ [~cubiceart@2600:1010:b021:994b:5dda:8d14:3f1f:eec5] has quit [Remote host closed the connection] 18:49 -!- CubicEarths [~cubiceart@2600:1010:b021:994b:5dda:8d14:3f1f:eec5] has joined #c-lightning 18:49 -!- CubicEarths [~cubiceart@2600:1010:b021:994b:5dda:8d14:3f1f:eec5] has quit [Read error: Connection reset by peer] 18:50 < mlz> bloxton, i think so, he has pictures of himself and his kids too: https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-February/001044.html 19:04 -!- almkglor [b4be2338@gateway/web/freenode/ip.180.190.35.56] has joined #c-lightning 19:20 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 19:52 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 19:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 20:11 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:20 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:30 -!- almkglor [b4be2338@gateway/web/freenode/ip.180.190.35.56] has quit [Ping timeout: 260 seconds] 21:00 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 245 seconds] 21:19 -!- a___ [3a0936e7@gateway/web/freenode/ip.58.9.54.231] has joined #c-lightning 21:23 -!- a___ [3a0936e7@gateway/web/freenode/ip.58.9.54.231] has quit [Client Quit] 21:39 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qpvsrgutcoaiurte] has quit [Quit: Connection closed for inactivity] 23:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lmlxkcluafoswbuh] has joined #c-lightning 23:43 < rompert> mlz: excellent! 23:52 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has joined #c-lightning