--- Day changed Thu May 23 2019 00:37 -!- pioklo [~Pioklo@static-91-225-135-27.devs.futuro.pl] has joined #lnd 00:59 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 01:04 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 248 seconds] 01:04 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 01:22 -!- MaxSan [~four@185.9.19.107] has joined #lnd 01:45 -!- MaxSan [~four@185.9.19.107] has quit [Quit: Leaving.] 01:58 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 02:16 -!- MaxSan [~four@185.9.19.107] has joined #lnd 02:18 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 248 seconds] 02:20 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 02:31 -!- MaxSan [~four@185.9.19.107] has quit [Ping timeout: 246 seconds] 02:49 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 02:50 -!- MaxSan [~four@194.187.251.115] has joined #lnd 03:24 -!- pioklo [~Pioklo@static-91-225-135-27.devs.futuro.pl] has quit [Ping timeout: 248 seconds] 03:27 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Remote host closed the connection] 03:31 -!- scoop [~scoop@205.178.77.52] has joined #lnd 03:37 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 272 seconds] 03:45 -!- MaxSan [~four@194.187.251.115] has quit [Ping timeout: 248 seconds] 03:48 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #lnd 03:48 -!- MaxSan [~four@82.102.28.107] has joined #lnd 03:50 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-midqjhdtdxxxpojh] has joined #lnd 04:03 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 04:06 -!- x000_ [~x000@unaffiliated/x000] has joined #lnd 04:08 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Ping timeout: 248 seconds] 04:09 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 246 seconds] 04:47 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 04:53 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Remote host closed the connection] 04:55 < queip> how long the initial sync of lnd should take? it's been like 15 minutes at least. bitcoind is synced 04:56 < queip> oh I see in debug... cought up to 150K blocks. Is there a way to speed it up, if this is a fresh new LND and LND wallet, so certainly no transfers to me exist in blockchain yet? 05:03 < molz> it depends on your hardware and internet 05:07 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 05:45 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 06:07 < queip> why it seems to scan entire chain if it just created a new wallet, so he can be sure no keys are there in old blocks? 06:10 < molz> i guess so.. what if it's not a new wallet? wallet.db can be replaced 06:38 < queip> molz: lnd just created the new wallet, first time I run it. 06:39 < molz> queip, cool story bro 06:40 < molz> if it keeps syncing and won't come to an end for half a day, you can submit an issue 06:45 -!- x000_ [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 06:46 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 06:49 -!- votesmith [~votesmith@237.ip-217-182-75.eu] has quit [Quit: bye] 06:50 -!- x000 [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 06:54 -!- votesmith [~votesmith@237.ip-217-182-75.eu] has joined #lnd 06:54 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Quit: ZNC - http://znc.in] 07:03 -!- scoop [~scoop@205.178.77.52] has joined #lnd 07:03 < queip> with localhost bitcoind, it takes much less, like maybe 15 minutes 07:04 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #lnd 07:18 -!- michaelfolkson [~textual@62.60.61.161] has joined #lnd 07:24 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Remote host closed the connection] 07:31 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 07:36 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 272 seconds] 07:42 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 07:43 -!- x000 [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 07:43 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 08:26 < x000> yo 08:26 < x000> is LND planning an architectural upgrade like the sharding of ethereum ? 08:32 < molz> wtf is that? my best guess is NO NO NO .. this is bitcoin, not eth 08:38 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 08:56 -!- michaelfolkson [~textual@62.60.61.161] has quit [Quit: Sleep mode] 09:03 < Asara> hey all, trying to build lnd and I get: https://pastebin.com/Md0cVsK0 09:03 < Asara> any advice? 09:05 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 09:06 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lnd 09:12 < Talkless> Asara: are you building released tag or master? 09:17 -!- x000_ [~x000@unaffiliated/x000] has joined #lnd 09:17 < Asara> released tag: HEAD detached at v0.6.1-beta 09:18 < molz> Asara, how did you build it? 09:19 < Asara> running go get + go build in src/github.com/lightningnetwork/lnd/ 09:19 -!- sfhi [~sfhi@178.255.154.107] has joined #lnd 09:20 < molz> Asara, here's the guide, check to see if you did it correctly: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#installing-lnd 09:21 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 258 seconds] 09:21 < molz> make sure you have the current Go version also 09:24 < Asara> yeap running go 1.11 09:24 < Asara> will do make clean/make/make install. lets try it :) 09:25 < Asara> upgrading from 0.6-beta 09:27 < Asara> also Talkless thanks for the advice the other day about autopilot.maxchansize. totally solved my problem 09:27 < Talkless> Asara: cool :) 09:28 < Talkless> Asara: you can tip me 1 satoshi if you would insist :)) 09:30 < molz> Asara, look at the topic of this channel, you need go 12.4 09:31 < molz> correction: Go 1.12.5 actually 09:34 < Asara> hm its in sid. i'll upgrade my golang 09:34 < Asara> thanks for the heads up molz 09:36 -!- siom [~siom@165.84.231.19] has joined #lnd 09:43 -!- MaxSan [~four@82.102.28.107] has quit [Ping timeout: 272 seconds] 10:00 -!- x000_ [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 10:02 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 10:03 -!- x000_ [~x000@unaffiliated/x000] has joined #lnd 10:05 -!- sfhi [~sfhi@178.255.154.107] has quit [Quit: Leaving] 10:07 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 257 seconds] 10:07 -!- x000_ [~x000@unaffiliated/x000] has quit [Ping timeout: 245 seconds] 10:08 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 10:25 -!- spoke0_ [~spoke0@92.116.116.148] has joined #lnd 10:37 -!- MaxSan [~four@2001:ac8:28:4:5cf4:b40d:cd32:5bdf] has joined #lnd 10:38 -!- scoop [~scoop@205.178.77.52] has joined #lnd 10:43 -!- MaxSan [~four@2001:ac8:28:4:5cf4:b40d:cd32:5bdf] has quit [Quit: Leaving.] 10:56 -!- spoke0_ [~spoke0@92.116.116.148] has quit [Read error: Connection reset by peer] 11:03 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 11:06 -!- scoop [~scoop@205.178.77.52] has joined #lnd 11:07 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 11:07 -!- scoop [~scoop@205.178.77.52] has joined #lnd 11:11 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 11:12 -!- scoop [~scoop@205.178.77.52] has joined #lnd 11:39 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:05 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 12:14 -!- sfhi [~sfhi@178.255.154.107] has joined #lnd 12:16 -!- michaelfolkson [~textual@82-132-246-32.dab.02.net] has joined #lnd 12:17 -!- michaelfolkson [~textual@82-132-246-32.dab.02.net] has quit [Client Quit] 12:43 -!- sfhi2 [~sfhi@91-152-137-204.elisa-laajakaista.fi] has joined #lnd 12:46 -!- sfhi [~sfhi@178.255.154.107] has quit [Ping timeout: 258 seconds] 13:14 -!- michaelfolkson [~textual@148.252.239.114] has joined #lnd 13:21 -!- michaelfolkson [~textual@148.252.239.114] has quit [Quit: Sleep mode] 13:48 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 13:53 -!- x000 [~x000@unaffiliated/x000] has quit [Ping timeout: 258 seconds] 14:41 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 14:46 -!- sfhi2 [~sfhi@91-152-137-204.elisa-laajakaista.fi] has quit [Quit: Leaving] 14:49 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 15:22 -!- pioklo [~Pioklo@static-91-225-135-27.devs.futuro.pl] has joined #lnd 15:37 -!- siom [~siom@165.84.231.19] has quit [Quit: Leaving] 16:04 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 16:11 -!- qxt [~bang@unaffiliated/qxt] has quit [Quit: Leaving] 16:12 -!- x000 [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 16:14 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 16:39 -!- MaxSan [~four@46.19.137.116] has joined #lnd 16:45 -!- spoke0 [~spoke0@2001:16b8:4806:8300:b4d9:b962:8337:d930] has joined #lnd 16:45 < spoke0> any LND experts around to bug with questions ? 16:46 -!- pioklo [~Pioklo@static-91-225-135-27.devs.futuro.pl] has quit [Ping timeout: 272 seconds] 16:46 <@roasbeef> don't ask to ask, just ask 16:49 -!- michaelfolkson [~textual@82-132-246-32.dab.02.net] has joined #lnd 16:56 < bitconne1> speak0, yes 16:56 < molz> i guess that was all he wanted to ask and roasbeef isn't expert enough.. lol jk :D 17:02 < spoke0> sorry, got distracted, 17:04 < spoke0> my question is about opening reverse channels, let's say i have a mobile wallet and want to open a channel to a node that will initalise the channel and send token over (bitrefill like), is that supported by LND or does this need a web application that handles the initialisation 17:06 < bitconne1> spoke0, lnd will accept channels opened to it, but the request needs to be handled out of band 17:09 < spoke0> and how would you tell lnd to send n tokens over if a node with public key k tries to open a channel ? 17:09 < bitconne1> that is the part that's handled out of band ;) 17:10 < spoke0> is there any idea on standardising that kind of behaviour, something like s BIP 17:10 < molz> i think that's what Acinq is doing with Eclair mobile isn't it? 17:11 < molz> lol no not a bip 17:11 < bitconne1> afaik no one does this at the protocol level 17:11 < molz> not a bolt either 17:11 < spoke0> thx 17:11 < molz> spoke0, if you have an LND node you can use loop 17:12 < spoke0> molz: link ? 17:12 < molz> https://github.com/lightninglabs/loop 17:12 < bitconne1> it could be an extension of dual-funded channels, if the other node agrees to let me put up zero funds 17:12 < spoke0> thx agaain 17:12 < molz> https://lightningloop.io/ 17:12 < bitconne1> np 17:15 -!- bitconne1 [~root@138.68.244.82] has quit [Quit: leaving] 17:17 -!- root____ [~root@138.68.244.82] has joined #lnd 17:18 < root____> test 17:19 -!- root____ is now known as bitconner 17:47 -!- michaelfolkson [~textual@82-132-246-32.dab.02.net] has quit [Quit: Sleep mode] 17:47 -!- scoop [~scoop@205.178.77.52] has joined #lnd 17:48 < lndbot> So I'm working on the issue re: pipelining settles to the switch immediately instead of waiting for the revoke to come in. The issue describes that force closes / link failures could occur due to duplicate settles. However, I wrote a quick PoC after reading the code in the `htlcswitch` package and it seems that no force closes / link failures could occur. When the first settle reaches the switch, the circuit is closed in memory via `s.closeCircuit(. 17:48 < lndbot> closes the circuit in the in-memory circuit map. In most of my tests, this settle already reached the incoming link and was then deleted via `DeleteCircuits` and the settle sent as a result of receiving the revocation returned a `ErrUnknownCircuit` error. But even if the first settle doesn't hit the incoming link and the second settle comes in, it should fail with `ErrCircuitClosing` since the in-memory circuit is already in the process of being closed. So i 17:48 < lndbot> that no force closes / link failures can occur. It seems to recover gracefully. Comments appreciated 17:49 -!- x000 [~x000@unaffiliated/x000] has quit [Remote host closed the connection] 17:54 -!- spoke0 [~spoke0@2001:16b8:4806:8300:b4d9:b962:8337:d930] has quit [Ping timeout: 252 seconds] 18:03 <@roasbeef> what happens when the second one is sent? it just de dups it? or it never actually gets to that incoming link? 18:05 < lndbot> It's sent to the switch and errors out on the call to `circuit, err := s.closeCircuit(packet)` in `handlePacketForward` 18:06 < lndbot> So the first settle should go through, the second one can't 18:18 < bitconner> eugene, yeah there shouldn't be an issue with duplicate settles, the circuit map dedupes them and so will the incoming link if it receives a duplicate settle for the same htlc index 18:19 < bitconner> i haven't through all the edge cases, but my initial guess as to where the complication lies is the fact that the pipelined settle won't have a SettleFailRef, which is needed to clean up the forwarding package of the outgoing link 18:20 < bitconner> that should be okay, because on startup/reconnection the forwarding package will retransmit it, and it should be deduped by circuit map and cleaned up at that time 18:21 < bitconner> (since the retransmitted one will have a proper settle fail ref, while the pipelined one won't) 18:21 < lndbot> Do you mean `DestRef`? 18:21 < bitconner> yes 18:21 -!- libertyprime [~libertypr@118.149.171.150] has joined #lnd 18:22 < bitconner> the current advantage in not pipelining is that all destrefs are cleanded up in one atomic db transaction, while the retransmitted ones will each incur a db txn of their own 18:22 < bitconner> that is something we could look into in the future tho, i wouldn't worry about it in this pr 18:24 < bitconner> actually, ignore my comment about startup/reconnect. that can happen, but they'll be retransmitted shortly after if the reovke comes in 18:25 < bitconner> this is where i suspect the dest refs will be cleaned up https://github.com/lightningnetwork/lnd/blob/master/htlcswitch/switch.go#L1404 18:26 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 252 seconds] 18:26 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #lnd 18:29 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 18:40 < lndbot> Ah yes that's where they're cleaned up in ackSettleFails. But in some cases the retransmit won't clean up the dest ref if `ErrCircuitClosing` is returned since that one doesn't touch ackSettleFails. So then upon startup/reconnect, the dest ref would be cleaned up right? 18:41 < lndbot> I think I understand most of this, but one question is that if we pipeline a settle and it fails to get to the incoming link (link flaps or something), and we don't receive the revocation on the outgoing link for whatever reason, we won't ever attempt to retransmit the settle iiuc. Because I don't think this settle is ever persisted anywhere? 18:41 < lndbot> I know the preimage is persisted in the cache, but I don't think the backing updatelog in the lightningchannel struct is ever persisted 20:08 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #lnd 20:23 -!- scoop [~scoop@205.178.106.179] has joined #lnd 20:25 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Remote host closed the connection] 20:28 -!- scoop [~scoop@205.178.106.179] has quit [Remote host closed the connection] 20:45 -!- libertyprime [~libertypr@118.149.171.150] has quit [Read error: Connection reset by peer] 20:58 -!- scoop [~scoop@205.178.106.179] has joined #lnd 21:01 -!- scoop [~scoop@205.178.106.179] has quit [Remote host closed the connection] 21:01 -!- libertyprime [~libertypr@118.149.171.150] has joined #lnd 21:04 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 21:06 -!- scoop [~scoop@205.178.106.179] has joined #lnd 21:06 -!- x000 [~x000@unaffiliated/x000] has joined #lnd 21:07 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 21:08 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lnd 21:08 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Ping timeout: 246 seconds] 21:23 -!- scoop [~scoop@205.178.106.179] has quit [Remote host closed the connection] 21:24 -!- scoop [~scoop@205.178.106.179] has joined #lnd 21:38 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 21:43 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Remote host closed the connection] 21:54 -!- scoop [~scoop@205.178.106.179] has quit [Remote host closed the connection] 21:54 -!- scoop [~scoop@205.178.106.179] has joined #lnd 21:59 -!- libertyprime [~libertypr@118.149.171.150] has quit [Quit: leaving] 21:59 -!- scoop [~scoop@205.178.106.179] has quit [Remote host closed the connection] 22:20 -!- scoop [~scoop@205.178.106.179] has joined #lnd 22:25 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 22:29 -!- scoop [~scoop@205.178.106.179] has quit [Ping timeout: 258 seconds] 22:30 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Ping timeout: 268 seconds] 23:05 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has joined #lnd 23:10 -!- ccdle12 [~ccdle12@n218103251046.netvigator.com] has quit [Ping timeout: 268 seconds] 23:14 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd 23:28 -!- scoop [~scoop@205.178.77.52] has joined #lnd 23:33 -!- scoop_ [~scoop@205.178.77.52] has joined #lnd 23:33 -!- scoop [~scoop@205.178.77.52] has quit [Read error: Connection reset by peer]