--- Log opened Mon May 06 00:00:04 2019
00:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
01:19 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
01:37 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
01:57 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has joined #c-lightning
02:15 < ulrichard> Usually when a peer goes offline for a couple of days, I close the channel. Normally after at most two weeks it is closed. But I have four channels that are in the CHANNELD_SHUTTING_DOWN state for 3 or 4 weeks. What are my options to investigate what happened to them?
03:15 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 250 seconds]
03:16 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
03:16 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 244 seconds]
03:33 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:48 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
05:05 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
05:05 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #c-lightning
05:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
06:07 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #c-lightning
06:19 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Ping timeout: 248 seconds]
06:21 -!- ironbutt [~LiberLive@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 246 seconds]
06:29 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 244 seconds]
06:37 < m-schmoock> to whom it may concern: thx for those invoiceless test donantions to my node
06:38 < m-schmoock> since a node operator can only guess what the payment was for we could rename the calls "senddonation" "listdonations" :D
06:41 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Remote host closed the connection]
06:58 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:01 <@cdecker> lol
07:01 <@cdecker> ulrichard: by default the node will always attempt to close collaboratively (since it is cheaper and doesn't have a time delay), but it requires the peer to reconnect and negotiate the close
07:02 <@cdecker> ulrichard: if that doesn't work you can try `lightning-cli -k close id=[peerid] force=true`
07:03 <@cdecker> The `-k` in that command line switches to keyword based mode and then you can specify `force` as well (you can do so without `-k` as well, but then you need to know the argument order)
07:07 < ulrichard> cdecker: ok thanks.  I get a txid wether I use the peerId or the channelId in this command. Is this intentional? Now I guess I have to wait for an onchain confirmation to see the result?
07:07 <@cdecker> Yep, now we wait for the TX to confirm
07:08 <@cdecker> Then we wait for the delay of the unilateral close to timeout, and then the wallet will grab the funds back
07:08 <@cdecker> Depending on the peer that may take a few days, but you'll get your funds back
07:09 < ulrichard> So With other channel closes the process was automatic. What could be different with these channels, that they stayed in the "closing" state for so long?
07:12 < m-schmoock> cdecker: we could need a decent faq sequence diagram incase of these questions
07:13 < m-schmoock> after the third time running into this, im confident that the daemon does what it is supposed to to, but for newbies it can be painfull :D
07:13 < m-schmoock> *processflow diagram
07:14 < ulrichard> m-schmoock: yes that sounds usefull
07:15 <@cdecker> Yea, I started one at some point, but never got to a usable point
07:15 < ulrichard> Another question: Is there an easy way to get an xpub for the on-chain wallet of lightningd?
07:16 <@cdecker> Currently not, but patches welcome :-)
07:17 < ulrichard> Don't know if I find the time. But that sounds like a good task to start with...
07:18 < m-schmoock> the "panic! where is my money?" flowchart diagram
07:18 < m-schmoock> the last arrows that cant be resolved are "go ask in IRC" :D
07:22 <@cdecker> That'd be good yeah
07:28 < ulrichard> Ok, the first one is confirmed closed. Thanks for the help.
07:46 < grubles> 7
08:18 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 248 seconds]
08:19 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has quit [Remote host closed the connection]
08:22 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
08:43 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
08:55 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #c-lightning
09:02 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:03 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
10:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
12:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:35 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
12:38 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
12:39 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 248 seconds]
12:39 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 248 seconds]
13:03 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
13:06 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Ping timeout: 252 seconds]
13:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:43 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
14:55 < fiatjaf> where does the 'pay' plugin stores the data that's later recovered by 'paystatus'?
15:37 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:06 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
18:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:40 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
18:59 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: leaving]
20:51 < rusty> jb55: That was surprisingly useful.  For 1M channels, we now have 284MB in channel/node data, but 165M in our ordered map of gossip msgs, and 29MB for the hash table for short-channel-ids -> channels.
21:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
21:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
21:28 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Ping timeout: 255 seconds]
22:00 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
22:05 < jb55> rusty: nice I haven't used that before, will check it out
22:23 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
22:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:38 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has joined #c-lightning
23:04 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
23:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:19 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 248 seconds]
23:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
--- Log closed Tue May 07 00:00:05 2019