--- Day changed Wed Feb 21 2018
00:07 -!- bryan_w [~is@2600:2108:9:8a90:f3b8:cb41:7595:463f] has quit [Ping timeout: 260 seconds]     
01:06 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection]     
01:06 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning     
01:08 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning     
01:11 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 240 seconds]     
01:30 < Mark____> about that "Capacity exceeded" failure, could someone explain what is meant by "AND have enough left to maintain your channel" ?
01:33 < p3tr> you need to have some funds to cover fees for TX's hitting the blockchain (closing the channel for example)
01:33 < Mark____> ok, thanks
01:37 < p3tr> is there a way how to make one invoice to be payable multiple times? what i mean is that i would create just one invoice (qr code) and reuse it
01:40 < Mark____> a followup question: the fee for the settlement tx has to come from the channel capacity? It can't be provided by the ln-node wallet?
01:46 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds]     
01:51 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
01:56 < p3tr> not sure, but my gut tells me it needs to be from the channel capacity, since it could be dangerous to cover all fees for all channels from the wallet - it could run out in case of massive channel closing
02:10 < bitonic-cjp> It has to come from channel capacity. If it came from anything that's only accessible my one node (say node A), then the other node (say node B) wouldn't be able to close the channel without A's cooperation.
02:10 < p3tr> good point
02:12 < bitonic-cjp> I don't know how fee negotiation between peers currently works. I guess the peer with the largest balance has the greatest interest in being able to close the channel.
02:13 < Mark____> so the error comes from the channel counterparty, it won't route a payment that would deplete all of your capacity in the channel?
02:18 < bitonic-cjp> I don't know.
02:23 < bitonic-cjp> Maybe a stupid idea: why can't we set the fee for the commit tx to ZERO, and use child-pays-for-parent to get it included in the block chain?
02:24 < bitonic-cjp> Or, instead of zero, just above the relay threshold.
02:24 < mryandao> bitonic-cjp: if a counterparty support 0-fee or arbitrarily low fees, it may be vulnerable to DoS attacks.
02:25 < mryandao> there should be cost to create a bi-directional channel with a counterparty, it shows your literal commitment lol.
02:26 < bitonic-cjp> I'm not talking about creating the channel, I'm talking about the tx that closes the channel. Let me check the official terminology.
02:26 < mryandao> settlement?
02:27 < bitonic-cjp> https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction.md
02:27 < bitonic-cjp> I think you were talking about the "Funding transaction".
02:28 < bitonic-cjp> I was questioning why we shouldn't make the "Commitment transaction" a very-low-fee tx.
02:31 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1056: Remove redundant casts to same type (master...redundant-casts) https://git.io/vAEcZ
02:35 < bitonic-cjp> https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md#updating-fees-update_fee
02:36 < bitonic-cjp> "...there is no general method for the broadcasting node to use child-pays-for-parent to increase its effective fee."
02:37 < bitonic-cjp> "the party which requested the channel creation always pays the fees for the commitment transaction"
02:41 < bitonic-cjp> This is different from what I see in C-Lightning though: you'd expect this fee to be (invisibly?) subtracted from the creator's channel balance, but somehow a payment TO the creator's side can still be affected?
03:22 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 256 seconds]     
03:59 -githubby:#c-lightning- [lightning] cdecker pushed 2 new commits to master: https://git.io/vAE2k
03:59 -githubby:#c-lightning- lightning/master 9842e32 Rusty Russell: lightningd: expose internal error information....
03:59 -githubby:#c-lightning- lightning/master 369d3ab Rusty Russell: fixup! Close memory leak, make error exposure DEVELOPER=1 only.
04:07 -githubby:#c-lightning- [lightning] cdecker closed pull request #1056: Remove redundant casts to same type (master...redundant-casts) https://git.io/vAEcZ
04:32 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
04:34 < p3tr> Is it possible to create a channel where both parties commit some funds? So far all channels i made with c-lightning show funds only on my side
04:50 < bitonic-cjp> From my understanding, this should be possible in theory, but I don't even know if there is a protocol standard for supporting that feature.
04:58 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 256 seconds]     
04:59 < hkjn0> p3tr: current protocol has all the initial funds in a channel committed by the initiator of the channel, see funding_satoshis here: https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md#the-open_channel-message
05:03 < p3tr> hm, i noticed this: push_msat is an amount of initial funds that the sender is unconditionally giving to the receiver
05:03 < bitonic-cjp> I think, in the future, doing something like that might come down to creating two channels (one in each direction) and then merging them. It does however violate the current protocol assumption that each channel only has a single funding tx.
05:03 < p3tr> so theoretically i could create a channel where both sides have funds by "giving away" some of mine?
05:05 -!- shesek [~shesek@31.210.189.206] has joined #c-lightning     
05:05 -!- shesek [~shesek@31.210.189.206] has quit [Changing host]     
05:05 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
05:05 < p3tr> bitonic-cjp: well i thought about this too (creating another channel in the opposite direction) but c-lightning tells me there already is a channel with that peer and refuses to create another
05:05 < p3tr> { "code" : -1, "message" : "Peer already CHANNELD_NORMAL" }
05:06 < bitonic-cjp> It is a limitation of C-Lightning that will probably be fixed in the future: C-Lightning only allows a single channel per peer.
05:10 < p3tr> ok thats good to know, i was afraid its a limitation of the protocol
05:10 < p3tr> thanks for all the info, much appreciated
05:11 < p3tr> do you perhaps know if that push_msat works as i described? and if so, can i somehow force c-lightning to use it
05:11 < p3tr> i would love to have a channel with funds on both sides between my 2 nodes
05:12 < bitonic-cjp> You could also just create a channel, and then perform a Lightning tx from the channel creator to its peer. Should have the same end result, right?
05:14 < p3tr> true
05:14 < p3tr> sometimes i'm overthinking stuff :) though that push_msat thing stir intrigues me
05:15 < p3tr> i'm going to poke through the code a bit just to see whats it all about
05:19 < Mark____> you could use push_msat on testnet. I have a hard time seeing it being used on mainnet
05:26 < mlz> yup, most of channels on mainnet have only one sided funds
05:27 < mlz> unless you open a channel with sleepyark or bitrefill or another merchant and buy something, your channel has fund only on your side 
05:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ptkymzprmpoctyba] has quit [Quit: Connection closed for inactivity]     
05:36 < mlz> hm does c-lightning support 'push_amount' now? 
05:47 -!- fafaynk [556487f0@gateway/web/freenode/ip.85.100.135.240] has joined #c-lightning     
05:47 < fafaynk> hi all, i have a problem with my lightningd, log is here http://pasted.co/e6cfdd6e
05:47 < fafaynk> please help
05:48 < fafaynk> it kills itsel unexpectedly
05:57 -!- dougsland [douglas@nat/redhat/x-ppxltmsirxueymuo] has joined #c-lightning     
06:03 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning     
06:26 < mlz> fafaynk, can you restart it?
06:27 < fafaynk> yes i can restart it, but always the same
06:27 < fafaynk> it runs for a while
06:28 < fafaynk> then exit
06:30 < mlz> fafaynk, when was the last time you updated your node?
06:33 < fafaynk> "version" : "v0.5.2-2016-11-21-1676-gbab3b1a", "blockheight" : 510230,
06:34 < fafaynk> is that what you asked for ?
06:35 < mlz> i just pulled the latest commit an hour ago
06:36 < mlz>  "version" : "v0.5.2-2016-11-21-2040-g3dbace3"
06:36 < mlz> try to update and see if it can help
06:37 < fafaynk> it runs for 7 hours now from my last restart
06:38 < fafaynk> still running
06:38 < fafaynk> if error occurs again
06:38 < fafaynk> i'll update and try
06:38 < fafaynk> thanks
06:39 < fafaynk> another issue is cpu utilization
06:39 < fafaynk> its 100%
06:39 < fafaynk> is that normal?
06:40 < fafaynk> its a digitalocean droplet 4 GB 2 vCPUs
06:50 < mlz> no it's not normal, update :P
07:05 < dougsland> not normal here too
07:05 -!- fafaynk [556487f0@gateway/web/freenode/ip.85.100.135.240] has quit [Ping timeout: 260 seconds]     
07:05 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds]     
07:06 -!- vogelito [~Adium@187.151.195.87] has quit [Quit: Leaving.]     
07:17 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1057: Mark intentionally unused parameters as such (with "UNUSED") (master...unused) https://git.io/vAEAc
07:17 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1058: Remove unused function json_dev_broadcast(...) (master...json_dev_broadcast) https://git.io/vAEAR
07:25 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning     
07:32 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning     
07:40 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]     
07:52 -!- jb554 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning     
08:06 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1061: Remove unused function arguments (master...remove-unused-function-arguments) https://git.io/vAufz
08:17 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning     
08:21 -!- jb554 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds]     
08:23 -!- vogelito [~Adium@187.151.195.87] has joined #c-lightning     
08:38 < bitonic-cjp> Argh, listchannels gives empty output again. Why????
08:43 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 276 seconds]     
09:01 -!- vogelito [~Adium@187.151.195.87] has quit [Quit: Leaving.]     
09:05 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning     
09:10 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving]     
10:08 -!- vogelito [~Adium@187.162.189.159] has joined #c-lightning     
10:11 < mlz> hm i'm running bitcoind and lightningd on this WSL Ubuntu, and from "getinfo" it says ""blockheight" : 1449, "network" : "testnet""  I'm wondering now if this Windows Linux Subsystem is not suitable to run nodes 
10:17 -!- vogelito [~Adium@187.162.189.159] has quit [Quit: Leaving.]     
10:18 -!- vogelito [~Adium@187-162-189-159.static.axtel.net] has joined #c-lightning     
10:28 -!- douglas [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning     
10:29 -!- douglas is now known as dlandgraf     
10:31 -!- dlandgraf is now known as dland     
10:33 < dougsland> mlz, no new blockheight ? 
10:34 < mlz> that number is totally wrong, testnet has mover 1.2mil blocks
10:35 < mlz> there's a disconnection between bitcoind and lightningd for some reason, probably have to stop running the nodes on that unbuntu
10:35 < dland> mlz: I see, I have been running on Fedora, just works. 
10:37 < mlz> well this is WSL ubuntu, my nodes installed on a vps server are fine on ubuntu there
10:40 < dland> if you need windows, have you tried cygwin ?
10:47 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1062: Make Python code conform to the Python PEP 8 style guide (master...pep8) https://git.io/vAu4w
10:54 -!- vogelito [~Adium@187-162-189-159.static.axtel.net] has quit [Quit: Leaving.]     
10:56 -!- vogelito [~Adium@187.162.189.159] has joined #c-lightning     
10:59 -!- vogelito [~Adium@187.162.189.159] has quit [Client Quit]     
10:59 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds]     
10:59 -!- vogelito [~Adium@187-162-189-159.static.axtel.net] has joined #c-lightning     
11:05 -!- vogelito [~Adium@187-162-189-159.static.axtel.net] has quit [Quit: Leaving.]     
11:06 < mlz> dland, ? 
11:26 < dland> mlz: I understood you are running on a Linux layer on top of Windows
11:26 < dland> never used WLS Ubuntu
11:30 < mlz> yea i'm just trying it out to see if it can work in this environment, and i don't want a VM or docker or even a dual boot 
11:30 < mlz> wondering if i can make a lightning.exe for windows 
11:34 < dland> mlz: I was mentioning to run on top of: www.cygwin.com
11:35 < dland> not sure if will be different from what you have now
11:36 -!- vogelito [~Adium@187.162.108.173] has joined #c-lightning     
11:39 < mlz> cygwin is a compiler, correct? not a OS, correct?
11:41 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has joined #c-lightning     
11:41 < lxer> c-lightning crashed again  https://dpaste.de/vJJS
11:56 < dland> mlz: it's unix env like, you can build stuff inside it
11:56 < dland> with gcc 
12:08 < vogelito> are there any docs on closing a channel and getting funds back?
12:46 -!- vogelito [~Adium@187.162.108.173] has quit [Quit: Leaving.]     
12:56 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has joined #c-lightning     
13:01 -!- dougsland [douglas@nat/redhat/x-ppxltmsirxueymuo] has quit [Ping timeout: 240 seconds]     
13:17 -!- jb554 [~jb55@216-71-192-56.dyn.novuscom.net] has joined #c-lightning     
13:54 -!- vogelito [~Adium@187-162-108-173.static.axtel.net] has quit [Quit: Leaving.]     
14:16 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection]     
14:21 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning     
14:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
14:37 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit []     
15:00 -!- booyah [~bb@193.25.1.157] has quit [Remote host closed the connection]     
15:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
15:37 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has quit [Read error: No route to host]     
15:52 -!- lightninmax [495ad11f@gateway/web/freenode/ip.73.90.209.31] has quit [Ping timeout: 260 seconds]     
15:55 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning     
16:11 -!- booyah [~bb@193.25.1.157] has joined #c-lightning     
16:44 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 255 seconds]     
17:01 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning     
17:09 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vAzfQ
17:09 -githubby:#c-lightning- lightning/master 91a9c29 practicalswift: Mark intentionally unused parameters as such (with "UNUSED")
17:10 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1047: dev_ping: don't crash with silly values. (master...pr-985) https://git.io/vAByw
17:12 -!- jb554 [~jb55@216-71-192-56.dyn.novuscom.net] has quit [Ping timeout: 256 seconds]     
17:34 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1066: wallet: remove obsolete peers. (master...fix-old-db-peers-exist) https://git.io/vAzUa
17:57 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1067: status: don't log gossip messages in channeld. (master...dont-log-gossip) https://git.io/vAzTF
18:03 < rotarydialer> Any way to get funds out of channel in this state: "state" : "ONCHAIND_THEIR_UNILATERAL"
18:03 < rotarydialer> ?     
18:04 < grafcaps> that means that the other party closed the channel
18:04 < grafcaps> without you
18:04 < grafcaps> so no
18:05 < grafcaps> any funds that you had in that channel should be returned to your on-chain wallet balance
18:11 < rusty> rotarydialer: yeah, it will just take time...
18:11 < mlz> rotarydialer, how long has it been in that state?
18:11 < rotarydialer> Since yesterday when I tried to buy some stickers... it didn't work
18:13 < rotarydialer> I'm usually good at figuring things out with some docs or examples, but I can tell that this is still the early days!
18:13 < dland> cccccchucrkbhbldfukfeguhnjfbnjlklfchvevgcitd
18:13 < dland> sorry
18:13 < grafcaps> hello dland's cat
18:14 < dland> ;)     
18:14 < rotarydialer> dland, that's the same password I use
18:14 < rusty> rotarydialer: what's your node id?  I can try to figure out what happened...
--- Log closed Wed Feb 21 18:21:01 2018
--- Log opened Wed Feb 21 18:21:21 2018
18:21 -!- kanzure [~kanzure@unaffiliated/kanzure] has joined #c-lightning     
18:21 -!- Irssi: #c-lightning: Total of 56 nicks [1 ops, 0 halfops, 0 voices, 55 normal]     
18:24 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning     
18:29 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has joined #c-lightning     
18:33 -!- Irssi: Join to #c-lightning was synced in 758 secs
18:44 < rusty> rotarydialer: ah, you didn't connect to the store directly, no wonder I can't find you!
19:13 -!- raichu [44b46aee@gateway/web/freenode/ip.68.180.106.238] has joined #c-lightning     
19:29 -!- raichu [44b46aee@gateway/web/freenode/ip.68.180.106.238] has left #c-lightning []     
20:15 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1068: Expose version (master...expose-version) https://git.io/vAzOa
20:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds]     
20:21 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-bgrbfkijhictvjul] has joined #c-lightning     
20:46 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
20:48 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]     
20:48 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]     
20:48 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
21:10 < rotarydialer> rusty, I opened a channel with another node. I was basing this on the guide I was using.
21:36 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 260 seconds]     
22:01 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]     
22:40 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-bgrbfkijhictvjul] has quit [Quit: Connection closed for inactivity]     
23:28 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has quit [Ping timeout: 260 seconds]     
23:39 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning