--- Log opened Tue Feb 05 00:00:41 2019
00:13 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
00:14 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
00:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:13 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:25 < t0mix> I opened direct channel with LND node, paid 4mil invoice. in log I see +6300satoshi was paid and route taken was not direct. in addition, receiver received 4006300 satoshi in total. how that's possible?
01:40 < t0mix> .. I did another payment, direct route, 1 million. paid 1002213.724 sat. wth =|
01:41 < t0mix> I'm sure even the first payment was direct "2019-02-04T23:06:55.754Z lightningd(11356): Sending 4006630681 over 1 hops to deliver 4000000000"
01:41 < t0mix> but why it collects payments when it is final destination?
02:02 < t0mix> does c-lightning just add random amounts?
02:33 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:45 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:05 -!- wxss [~user@mail.deeplinkmedia.com] has quit [Ping timeout: 245 seconds]
03:06 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
03:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
05:39 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
05:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:02 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
06:24 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:15 <@cdecker> t0mix: it will add a random amount up to 0.5% - routing fee
07:15 <@cdecker> For anything above that it'll need to told that it's ok
07:16 <@cdecker> On direct paths however we will soon stop fuzzing the amount since there is no previous hop that we have to hide our intended destination from 
07:19 < t0mix> aha, so the receiver receive a random bonus at the moment. and this will be gone with some planned release?
07:21 < t0mix> why lnd doesn't behave in same way? is it better or worse?
07:32 -!- kexkey [~kexkey@68.168.114.35] has joined #c-lightning
07:47 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
08:48 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
08:48 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
08:48 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
09:11 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:44 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
09:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
10:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
11:19 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:22 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
11:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
11:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
11:57 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
11:58 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
12:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
12:33 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
12:37 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
12:39 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:41 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
13:01 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 268 seconds]
13:06 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
13:13 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
13:32 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
13:44 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
14:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:24 -!- kexkey [~kexkey@68.168.114.35] has quit [Quit: Scaling pentatonically]
14:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:30 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
14:32 <@niftynei> t0mix don't quote me on this, but i believe that it'll be updated as of the next release
14:33 <@niftynei> i'd assume that lnd doesn't do it because they're a bit smarter about direct routes than c-lightning's current implementation
14:37 -!- Kostenko [~Kostenko@185.183.106.228] has quit [Ping timeout: 246 seconds]
14:42 -!- Kostenko [~Kostenko@185.183.106.228] has joined #c-lightning
14:47 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
15:16 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
16:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:25 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:54 < roasbeef> niftynei: yeh one of our peeps made a PR to the spec for that, we added stricter checks that made sense, and turns out their incompatible with what CL and eclair do atm 
16:55 < roasbeef> which sort of carries over to the max HTLC in the channel udapte, as that can't be higher than the channel capacity, so consistent to also ensure that max in flight on the link level isn't higher 
17:05 <@niftynei> afaict we should be setting the lower of the channel capacity or the remote's max inflight for the max msat htlc value in channel_updates
17:10 <@niftynei> well capacity minus cumulative reserves (essentially the 'effective' channel capacity)
17:12 <@niftynei> what's the PR# for the spec change? i wanna tag this patch to bound our max inflight num with it 
17:20 < molz> roasbeef, i guess this is the PR? -> https://github.com/lightningnetwork/lightning-rfc/pull/561
17:21 < molz> but it's closed
17:25 < roasbeef> yeh that's it
17:26 < roasbeef> so the max htlc on the channel udpate we set is in the opposite direction, which means it needs to observe the max htlc in flight set, ofc if that's infinity then you can use any value there, but then there's an issue where that's higher than the capacity there 
17:27 < roasbeef> we started to validate to ensure tha max in flight sent wasn't above the capacity taking into account resreve, but since y'all advertise max uint64, that caused us to reject all channels 
17:27 < roasbeef> we've reverted that check since then to not impact our next release, but just wanted to bring it to yalls attention 
17:27 < roasbeef> eclair sets the same static value of 5 mil sat or so, which can be above the chan size if it execeeds 5 mil sat 
17:48 -!- mryandao [~mryandao@unaffiliated/mryandao] has joined #c-lightning
19:39 -!- kexkey [~kexkey@68.168.114.35] has joined #c-lightning
19:45 -!- kexkey [~kexkey@68.168.114.35] has quit [Ping timeout: 244 seconds]
19:46 -!- kexkey [~kexkey@68.168.122.228] has joined #c-lightning
20:09 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
20:10 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
20:51 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
22:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
22:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
23:04 -!- warren [~warren@fedora/wombat/warren] has quit [Ping timeout: 240 seconds]
23:05 -!- warren [~warren@fedora/wombat/warren] has joined #c-lightning
--- Log closed Wed Feb 06 00:00:42 2019