--- Log opened Thu Jul 04 00:00:00 2019
00:14 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
00:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
01:05 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:13 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
01:19 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:29 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
01:30 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:07 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
03:14 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
03:20 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has quit [Ping timeout: 268 seconds]
03:21 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
03:22 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has joined #c-lightning
03:30 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
03:33 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Client Quit]
03:40 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds]
03:45 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:58 -!- k3tan172 [~k3tan@unaffiliated/k3tan] has quit [Remote host closed the connection]
04:34 -!- k3tan [~k3tan@unaffiliated/k3tan] has joined #c-lightning
04:54 < m-schmoock> cdecker: I noticed that `listchannels <scid>` for newly created channels will keep showing `"base_fee_millisatoshi" : 0` and `"fee_per_millionth" : 0` until I restart the daemon...
04:55 < m-schmoock> In this case LNBIG (who else) created a channel too me. When it gor CHANNELD_NORMAL I tried to use it and it failed with incorrect fees
04:55 < m-schmoock> then I did lightning-cli listchannels 583773x838x0  which shows me 0 fees
04:55 <@cdecker> Hm, sounds like a regression from when we introduced dynamic fees
04:55 < m-schmoock> can someone do a `lightning-cli listchannels 583773x838x0` and tell me the fees you see on gossip?
04:56 < m-schmoock> not sure, nobody changed the fees (Yet)
04:56 < m-schmoock> maybe your right
04:57 < m-schmoock> dunno
04:57 < m-schmoock> please pastebin `lightning-cli listchannels 583773x838x0` output
04:57 <@cdecker> Syncing now
04:57 < m-schmoock> :D
05:02 < m-schmoock> my node is the one reporting 400/4 fees
05:02 < m-schmoock> I charge very little to attract traffic and find moar bugs
05:07 < m-schmoock> My guess: it is a race condition between LND and CLN about channel announcement
05:11 < m-schmoock> Maybe when we see gossip with fees of yet non NORMAL channel right before the channel would be turning to NORMAL, the gossip is (maybe) dropped or something
05:11 < m-schmoock> at least this is the second or third time I noticed, so there is an issue
05:12 <@cdecker> So I see what appears to be your outgoing direction
05:13 <@cdecker> Fees 400/4 from 02a2 to 03fce
05:13 < m-schmoock> yes thats my node wating 400
05:13 < m-schmoock> but they are requesting 0/0   https://lightning.chaintools.io/channel/641865201536598016
05:13 < m-schmoock> and when I use it, it fails for INSUFFICIENT_FEES
05:14 < m-schmoock> LNBIG made this channel to me couple of hours ago, so all capacity is on there side
05:14 < m-schmoock> on way to use this channel (currently) is routing from them to me
05:15 < m-schmoock>  {'payment_hash': 'a6437f6569df5e97dfedfbda88379ebb4e90307e5a8c2a457de28c739dd75997', 'timeout': 600}, error: {'code': 204, 'message': 'failed: WIRE_FEE_INSUFFICIENT (reply from remote)', 'data': {'erring_index': 2, 'failcode': 4108, 'failcodename': 'WIRE_FEE_INSUFFICIENT', 'erring_node': '03fce165537aea120bffe8505876b44d5119354f825b3eac329b761fc5636bf334', 'erring_channel': '583773x838x0', 
05:15 < m-schmoock> 'erring_direction': 1}}
05:15 < m-schmoock> maybe its just a LND bug
05:15 < m-schmoock> but I noticed this several times. 
05:17 < m-schmoock> cdecker: do you also see "0/0" from them to me ?
05:17 <@cdecker> lnbig seems to send out an announcement (channel gets announced), and a channel_update (cltv delta is set)
05:17 <@cdecker> I can't see their direction in my cln yet
05:18 < m-schmoock> ah ok
05:18 <@cdecker> 1ml says they are announcing 0/0: https://1ml.com/channel/641865201536598016
05:18 < m-schmoock> shall I restart and see if that triggers something in their LND ?
05:18 <@cdecker> Notice that CLTV delta, which is also in the update is actually set to a valid value
05:19 < m-schmoock> you mean their 30 ?
05:19 <@cdecker> No idea why we're not seeing thei channel update
05:19 <@cdecker> Yep
05:19 < m-schmoock> I bet it will happen once I restart
05:19 < m-schmoock> lets see ....
05:19 <@cdecker> Hm, 1ml might also just be guessing 30 to be default, and not have received a channel update at ll
05:20 < m-schmoock> https://lightning.chaintools.io/channel/641865201536598016 also shows 30
05:20 < m-schmoock> hmmmm still 30/0/0  
05:20 < m-schmoock> my node sees 30
05:21 < m-schmoock> hm, the guys park 27 in their hotwallet, maybe they dont need the money :D
05:21 < m-schmoock> *27 BTC
05:21 < m-schmoock> restart didnt change it. re-trying to use this channel ...
05:21 <@cdecker> So you have an update for their side?
05:22 < m-schmoock> now it worked
05:22 <@cdecker> So you have an update for their side?This is what I see btw: https://gist.github.com/cdecker/e809f14cbd562cf2df2120ae9e1213cf
05:22 < m-schmoock> dunno, after restart, my node still sees 30/0/0 
05:22 < m-schmoock> but a payment worked correctly without INSUFFICIENT_FEE this time
05:22 <@cdecker> Wut? Sounds dodgy
05:23 < m-schmoock> is fee 0 disallowed ?
05:23 <@cdecker> No, that's perfectly alright
05:23 < m-schmoock> https://gist.github.com/m-schmoock/7e976435946ff02cf2c505c0429dce90
05:24 < m-schmoock> also https://gist.github.com/m-schmoock/1a5a80e4bd742909abd0d6ac175c837c
05:24 < m-schmoock> payment worked after restart
05:24 < m-schmoock> since they raise the INSUFFICIENT_FEE exception at their side, its likely a LND bug when using a channel after it just turned to CHANNELD_NORMAL
05:32 <@cdecker> Hm, strange, we do test this kind of thing quite often in the integration tests
05:32 <@cdecker> I'd rather expect there to be an issue with 0fees
05:39 < m-schmoock> can you ad a LND integration test that opens a channel fom´rom LND with 0 fees. try to use it after turning NORMAL
05:39 < m-schmoock> ...
05:45 <@cdecker> Sure, will need to first instrument lnd in the tests to be able to configure that, but should work
05:46 < m-schmoock> where / how are the integration tests organized?
06:22 <@cdecker> They're here https://github.com/cdecker/lightning-integration
06:23 <@cdecker> Though I haven't run them for a while now, and I think eclair changed something lately that broke the tests
06:23 <@cdecker> A simple `make update clients test` should execute all tests, though ptarmigan has some dev dependency that doesn't work for ubuntu 18.04
06:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:36 < m-schmoock> cdecker: now https://lightning.chaintools.io/channel/641865201536598016  shows the correct fees of them 60/500
06:37 < m-schmoock> I wonder why my payment worked after restart, as my gossip was still reporting 0/0
06:37 < m-schmoock> this is all fishy...
06:47 <@cdecker> Might be that the default policy on lnd is applied until it gets reconnected?
06:50 < m-schmoock> lets keep an eye on it
06:54 <@cdecker> Might be that the default policy on lnd is applied until it gets reconnected?
06:54 <@cdecker> Agreed
07:04 <@cdecker> fwiw now I actually also have the second update :-)
07:05 <@cdecker> With a much newer update, so I expect they just created a new one
07:17 < m-schmoock> those LND guys have too much money, when do they get hacked?
07:48 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds]
07:53 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
08:07 <@cdecker> PPA updated to 0.7.1, happy upgrading
08:32 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
08:40 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
08:40 -!- StopAndDecrypt_ [~StopAndDe@197.189.219.146] has quit [Ping timeout: 248 seconds]
08:59 <@cdecker> Docker images also updated, pull away :-)
09:21 < jb55> dang 900sats collected from two forwards, people are making some large purchases...
09:35 < jb55> last tx was 900k sats, collected 770 sats from that. brb lambo
09:56 < jb55> cdecker: noticing a bunch of these local_failed forwarding errors all of a sudden: https://jb55.com/s/af8f396ddb3b9da6.txt
09:56 < jb55> check at bottom
09:56 < jb55> not sure if something weird is going on or just regular network weirdness
09:57 <@cdecker> Network is weird alright :-)
09:57 <@cdecker> Did you update inbetween?
09:58 < jb55> cdecker: I think when it started getting timestamps was the latest release?
09:58 <@cdecker> Ok, seems you are enforcing a 10k minimum transfer
10:00 < jb55> I just have fee-per-satoshi=900
10:00 < jb55> that's my only fee option set
12:28 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
12:37 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
12:42 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
12:51 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
14:44 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
14:52 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds]
14:54 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Quit: jb55]
14:58 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
14:59 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
15:11 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
15:16 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
15:20 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
15:37 -!- MrHash [~mrhash@193.36.117.238] has joined #c-lightning
15:39 < MrHash> hey i'm running elements in regtest and lightning-elements on liquid-regtest chain. I pegged in some btc to elements and am sending to the lightning-elements wallet. the utxo appears in listfunds after 3 blocks but the amount is 0, the tx from elements side seems to be normal.
15:46 <@cdecker> MrHash: do you have a checkout from the lightning-elements branch? Might be that we have the wrong asset tag in there
15:51 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
16:06 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
16:08 < MrHash> cdecker: yes i checked out the lightning-elements branch and it's reporting as lightningd v0.7.1rc5-54-g83f09c2
16:09 < MrHash> i've set bitcoin related params to elements-cli, elements port etc. which i assumed was necessary in order to watch the elements chain
16:11 < MrHash> i pasted the listfunds and gettransaction output here https://pastebin.com/85Pj3KJf
16:19 < MrHash> elements regtest is reporting 5ac9f65c0efcc4775e0baec4ec03abdde22473cd3cf33c0419ca290e0751b225 as bitcoin asset
16:30 < MrHash> is "liquid-regtest" the correct network to run lightning-elements with?
16:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
17:25 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
17:26 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
17:40 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 272 seconds]
17:47 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
18:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:54 -!- MrHash [~mrhash@193.36.117.238] has quit [Ping timeout: 248 seconds]
18:59 -!- MrHash [~mrhash@host109-148-85-164.range109-148.btcentralplus.com] has joined #c-lightning
19:00 < MrHash> i guess this is setting the asset to liquidv1 bitcoin https://github.com/cdecker/lightning/commit/0ce13f463ce25f2fbb949a694b271c6442c93794
19:06 < MrHash> however the overwritten asset id doesn't match my regtest id either
19:19 < rusty> MrHash: hmm, unf. I haven't played with Elements & lightning at all, and cdecker is fast asleep...
19:20 < MrHash> yeh it's ok, it's not urgent, i'll wait until there's an update
19:20 < rusty> MrHash: I'm guessing this will be cleaned up before we finally get a PR for inclusion in the main branch...
19:20 < MrHash> yup np
19:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
19:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
19:27 -!- MrHash [~mrhash@host109-148-85-164.range109-148.btcentralplus.com] has quit []
20:26 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
20:45 -!- RonNa [~quassel@220-133-223-206.HINET-IP.hinet.net] has quit [Ping timeout: 246 seconds]
20:48 -!- RonNa [~quassel@220-133-223-206.HINET-IP.hinet.net] has joined #c-lightning
23:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Fri Jul 05 00:00:02 2019