--- Log opened Tue Feb 19 00:00:54 2019
00:41 < t0mix> rusty, you scared me with your twitter status. I have lightning data stored on 16GB microSD.. now I'm in panic, trying to put some replication in place before it's too late.
00:42 < t0mix> I'm going to try paystatus.. lightningspin awaits me
00:50 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
00:53 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
01:06 < t0mix> paystatus doesn't show much. I see that 2 channels were excluded, then there is start time, end time.. duration 25 seconds (it's usually faster, only 12 seconds =D but I restarted lightningd recently and it's quite unusable for 15 minutes after start )
01:08 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:10 < bitonic-cjp> The sendpay RPC command has a "description" field. Is this field only used internally, or is it also sent to the recipient (through some protocol I'm not aware of)?
01:29 < rusty> t0mix: hmm, what machine is that?  I run under valgrind, and *I* get faster than that!
01:37 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 255 seconds]
01:39 < m-schmoock> rusty: he has a raspberry pi 'server'
01:40 < m-schmoock> bitcoin minimalist
01:43 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
02:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds]
02:36 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:09 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:44 < rusty> bitonic-cjp: internal only,it's saved to the db and returned in listinvoices et al.
03:51 < ctrlbreak> Can someone clear some confusion up for me?  I saw it mentioned in the LND slack (In response to a question) that if your node loses channel state and your node is effectively a write-off, even in the very far future where your channel peers force a unilateral close on you... at that all settles on chain, you would *still* be unable to access any balance on your side (presuming you had, say, an xpriv derived from the hsm_secret)?  Is this true?  
03:51 < ctrlbreak> I need to understand more.
04:32 < molz> ctrlbreak, i tried that on testnet, it is true, maybe wrong channel to discuss?
05:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
05:15 < t0mix> rusty, ARMv7 4core CPU, 1GB RAM, 100Mb/s internetz. OS is Raspbian 9. valgrind seems like debugging tool. I have zero experience with that. but I started on "youtube academy" yesterday with "howto use gdb" videos :)
05:29 < m-schmoock> nice+
05:29 < m-schmoock> we in germany have heavy internetZ :D
05:30 < m-schmoock> okay, your from slowakia
05:33 < t0mix> 100Mb/s is the low level here :) I have installed "valgrind" .. playing with it
05:33 < m-schmoock> in germany we trust our government to deliver the world best internetz
05:34 < m-schmoock> starts with 16MBits
05:34 < t0mix> B is for bytes meng :)
05:35 < m-schmoock> :]
06:15 -!- kexkey [~kexkey@87.101.92.74] has joined #c-lightning
06:51 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
07:03 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 272 seconds]
07:15 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
07:42 < bitonic-cjp> In the getroute output, elements have a delay value. Is this the CLTV value?
07:44 < bitonic-cjp> Or is this the CLTV *increment*?
07:45 -!- kexkey [~kexkey@87.101.92.74] has quit [Read error: Connection reset by peer]
07:49 < bitonic-cjp> It seems to be the value itself, with the first delay value being "the very worst case timeout for the payment failure, in blocks.", presumably for the payer.
07:49 < m-schmoock> juop
07:52 < bitonic-cjp> I get the feeling there's an off-by-one error in my thinking about the route. For N nodes in the route, there are N-1 hops between nodes.
07:53 < bitonic-cjp> It seems each array element in the route refers to a "hop", and whenever it includes "node" data, it's the node data of the payee-side of that hop.
07:58 < m-schmoock> your description seems correct to me
07:58 < bitonic-cjp> Yes, I think so too. Thanks for confirming.
08:06 < bitonic-cjp> Do I understand correctly that both the 'cltv' input and the 'delay' outputs are relative to the current block height?
08:08 < bitonic-cjp> I suppose that means that sendpay has to add the current block height to these values to create actual CLTV values (which are absolute).
08:19 -!- kexkey [~kexkey@192.230.35.147] has joined #c-lightning
08:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds]
08:57 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
09:15 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:21 -!- kexkey [~kexkey@192.230.35.147] has quit [Ping timeout: 255 seconds]
09:35 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: Textual IRC Client: www.textualapp.com]
10:07 < jb55> my listforwards settled count = 2, failed = 17. does this seem right?
11:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
12:34 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:58 < fiatjaf> jb55, I think it does
13:17 < t0mix> some progress.. I started "gdb lightning-cli", then set arg "getroute blahblah 1000 9 9", start, next, .. ,next..
13:17 < t0mix> program took a while @ cli/lightning-cli.c, line 337
13:18 < t0mix> it took ~12 seconds there
13:23 -!- booyah_ is now known as booyah
14:13 < m-schmoock> t0mix: aehm
14:13 < m-schmoock> the cli is just asking the daemin via IPC interface to calculate a route
14:13 < m-schmoock> its not the cli that is doing the calculation :D
14:14 < m-schmoock> and it takes the cli 12 seconds to wait for the daemon for a resonse on the IPC socket
14:15 < m-schmoock> but you learned how to use gdb, thats good!
14:21 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:30 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:36 < t0mix> ah, okay.. so still long road ahead. thanks m-schmoock :)
14:45 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:35 < m-schmoock> I could need a code review and feedback on https://github.com/ElementsProject/lightning/pull/2342
15:35 < m-schmoock> gn8
16:54 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning
16:58 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
17:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
17:20 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3]
21:33 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds]
22:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:52 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
23:26 < t0mix> 2019-02-20T07:18:20.221Z lightning_gossipd(3852): Trying to find a route from 0214ec84c84827dd4911de56d2ecb77d367c6f24c658b8acfe4826b01968e45594 to 0354fcd9f1554f3505238e1b3c29223868953730c30b6565ad482dc31e90bcfa93 for 1000 msatoshi
23:26 < t0mix> 2019-02-20T07:18:20.223Z lightning_gossipd(3852): 1 hop solution: 4611686018427387903 + 0
23:26 < t0mix> 2019-02-20T07:18:20.231Z lightning_gossipd(3852): 2 hop solution: 4611686018427387903 + 0
23:26 < t0mix> 2019-02-20T07:18:20.238Z lightning_gossipd(3852): 3 hop solution: 2920 + 3
23:26 < t0mix> .. wtf is wrong with 1 hop solution?
23:26 < t0mix> (ofc it took 12 seconds to find the routes)
--- Log closed Wed Feb 20 00:00:54 2019