--- Log opened Tue Jan 01 00:00:08 2019
00:03 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
02:01 -!- 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
04:17 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
06:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds]
06:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
07:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
07:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
10:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
10:34 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
11:20 -!- charltonh [~charltonh@189.160.97.62] has joined #c-lightning
12:14 < ctrlbreak> Anyone help with an explanation to my earlier question regarding an invoice between 2 nodes under my control?  I'm trying to account for the overpayment (not upset or anything... just trying to understand the *why*):
12:14 < ctrlbreak> 2018-12-30T22:30:21.011Z lightningd(15920): pay(0x462d318): sendpay via route: us -> 556285:2185:0 (2995762193msat, 144blk) -> 02a5a95669adcb170dc85a70eef8bdd3e60b459d83bb47b6aac3e17c58faffc919
12:14 < ctrlbreak> <ctrlbreak> 2018-12-30T22:30:21.012Z lightningd(15920): Sending 2995762193 over 1 hops to deliver 2989091000
13:33 < charltonh> 6671193 msats is 6671 sats, which is the kind of fee I've seen before too and wondered Why.
13:34 < charltonh> a little high but not unreasonable if it took a long route, we don't have control over the fees some lightning nodes charge.
13:34 < charltonh> But as you mentioned only 1 hop...  so have you been able to account for it on that node?
13:49 < jb55> perhaps it's route randomization kicking in? not sure if that was fixed yet.
14:04 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:06 < ctrlbreak> Haven't been able to account for it.  It was a single payment over an existing channel between my 2 nodes.  Forgive my ignorance here, but if the payment wasn't 'routed' (hop=1?)... would fees be incurred at all?  If so, who's?  The sending node or the receiving?
14:09 < ctrlbreak> Oyy... my node crashed a couple hours ago :-S
14:09 < ctrlbreak> 2019-01-01T20:34:07.768Z lightningd(15920): new_htlc_out:Input cltv_expiry 0 less than 556898?
14:09 < ctrlbreak> 2019-01-01T20:34:07.791Z lightningd(15920): FATAL SIGNAL 6 (version v0.6.2-51-gd5aaa11)
14:09 < ctrlbreak> How do I submit a bug on Github?
14:19 < ctrlbreak> ... nevermind.  Found its an open issue.  Just wish there was some way I could help.
14:42 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
17:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:26 -!- deusexbeer [~deusexbee@095-129-175-192-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
17:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:32 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds]
18:55 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving]
19:05 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
20:31 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
20:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
21:02 -!- nothingmuch [~user@62.102.148.164] has quit [Ping timeout: 246 seconds]
21:20 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-muhzynlsjblcoded] has left #c-lightning []
21:20 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-muhzynlsjblcoded] has joined #c-lightning
23:03 < charltonh> I think what I am seeing is definitely a bug.  Added it to issue #2206  https://github.com/ElementsProject/lightning/issues/2206
--- Log closed Wed Jan 02 00:00:10 2019