--- Day changed Mon Mar 16 2020
00:35 -!- brtastic [~Thunderbi@2a02:a315:413a:7580:879e:25b4:92ae:7858] has quit [Ping timeout: 246 seconds]     
01:58 -!- lnostdal_ [~lnostdal@77.70.119.51] has quit [Remote host closed the connection]     
02:13 -!- namelesswonder [b6428b65@182.66.139.101] has joined #lnd     
02:40 -!- torzir [~nick@host86-191-160-217.range86-191.btcentralplus.com] has joined #lnd     
02:47 -!- torzir [~nick@host86-191-160-217.range86-191.btcentralplus.com] has quit [Quit: Leaving]     
02:47 -!- torzir [56bfa0d9@host86-191-160-217.range86-191.btcentralplus.com] has joined #lnd     
02:50 -!- torzir [56bfa0d9@host86-191-160-217.range86-191.btcentralplus.com] has quit [Remote host closed the connection]     
02:51 -!- jpe [~jp@i59F44F64.versanet.de] has quit [Ping timeout: 250 seconds]     
02:52 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd     
03:05 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has quit [Ping timeout: 265 seconds]     
03:07 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd     
03:07 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has joined #lnd     
03:28 -!- namelesswonder [b6428b65@182.66.139.101] has quit [Ping timeout: 240 seconds]     
03:59 -!- setpill [~setpill@unaffiliated/setpill] has joined #lnd     
04:00 < setpill> Hi all, I just restarted my node, and I'm having trouble getting it back up
04:00 < setpill> When I run lncli getinfo I keep getting some "all SubConns are in TransientFailure" error
04:01 < setpill> "transport: Error while dialing dial tcp 127.0.0.1:10009: connect: connection refused"
04:01 < setpill> Is this a common problem?
04:08 < setpill> Hard to debug if all commands give the same result
04:14 < setpill> The problem is I upgraded from 0.8.x to 0.9.2 so I can't poll the service to see if the database migration was successful
04:14 < setpill> What the fuck? It just fixed itself
04:16 < setpill> Oh, hm, not really. It just happened to once ask to unlock the wallet, and after I did that went back into "all SubConns are in TransientFailure"
04:18 < setpill> Ahhhhh. Ok. So, it took 23 minutes to go from "Started LND Lightning Daemon." to "[INF] CHDB: Checking for schema update: latest_version=12, db_version=11"
04:19 < setpill> In the meantime, it was showing the TransientFailure as the status (damn, that sucks, why the hell can't it tell me it's still starting up?)
04:19 < molly> it might be slow scanning
04:19 < setpill> Then, it needed unlock, which I did, and the service proceeded to error out with a "LTND: Unable to create server: can't set self node: unable to encode IP <nil>"
04:20 < molly> did you change anything in your lnd.conf?
04:20 < setpill> The service auto-restarted, so now it's back to "TransientFailure"
04:20 < setpill> molly: nope, no changes to lnd.conf, but a node version upgrade.
04:20 < molly> is your bitcoind fully synced?
04:20 < setpill> yep     
04:22 < molly> maybe a NAT related issue?
04:25 < setpill> Well it seems to me there's two issues. 1) LND does not give a nice indication it's still starting up, instead just throwing errors at any lncli query. 2) whatever is causing the "can't set self node: unable to encode IP <nil>" thing, which *might* be local configuration related.
04:25 < setpill> But since it worked fine on 0.8.x I find that odd.
04:27 < setpill> Also, after the service restarted, it took only 7 min to need an unlock. I did that, and now it's running smooth. 
04:27 < setpill> Weird heisenbug
04:49 -!- slivera [~slivera@37.120.218.148] has quit [Remote host closed the connection]     
06:06 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]     
06:37 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lnd     
06:44 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds]     
06:50 -!- mdunnio [~mdunnio@208.59.170.5] has joined #lnd     
07:15 -!- spoke0 [~spoke0@149.3.71.157] has quit [Ping timeout: 255 seconds]     
07:51 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd     
08:16 -!- Sajesajama_ [Salsa@gateway/vpn/protonvpn/sajesajama] has joined #lnd     
08:18 -!- Sajesajama [Salsa@gateway/vpn/protonvpn/sajesajama] has quit [Ping timeout: 240 seconds]     
08:33 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds]     
08:35 -!- mol [~molly@unaffiliated/molly] has joined #lnd     
08:40 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 246 seconds]     
08:49 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #lnd     
08:50 -!- mol [~molly@unaffiliated/molly] has joined #lnd     
08:54 < dongcarl> Hi all, trying to understand #3821. Does LND already have anchor commitments? Does this PR make anchor commitments pluggable, or does it introduce anchor commitments that are pluggable (for the first time).
09:34 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd     
09:46 < Bugz> Is something up with the LN? I can't seem to get any rebalance transactions to go through, either no path, or edge not found?
10:07 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 246 seconds]     
10:17 -!- jorijn [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has quit [Ping timeout: 256 seconds]     
10:17 -!- jorijn [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has joined #lnd     
10:23 -!- jorijn [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has quit [Ping timeout: 246 seconds]     
10:24 -!- mol [~molly@unaffiliated/molly] has joined #lnd     
10:25 -!- jorijn [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has joined #lnd     
10:26 -!- mol [~molly@unaffiliated/molly] has quit [Client Quit]     
10:27 -!- mol [~molly@unaffiliated/molly] has joined #lnd     
10:35 -!- spoke0 [~spoke0@149.3.71.157] has joined #lnd     
11:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]     
11:02 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd     
11:05 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]     
11:07 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd     
11:10 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]     
11:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd     
11:21 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/]     
11:27 -!- Netsplit *.net <-> *.split quits: so, hop3y
11:27 -!- Netsplit over, joins: hop3y
11:27 -!- Netsplit over, joins: so
12:01 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
12:33 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
12:33 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
12:38 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 246 seconds]     
12:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
12:51 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 246 seconds]     
13:03 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!]     
13:06 -!- sneak [~sneak@gateway/tor-sasl/sneak] has quit [Remote host closed the connection]     
13:27 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
13:29 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
13:31 <@roasbeef> dongcarl: yeh it's in master rn 
13:31 <@roasbeef> there's a command line flag 
13:32 < dongcarl> roasbeef: K, and the improvement from anchor commitments is allowing for easy, unilateral fee bumping?
13:32 <@roasbeef> yep 
13:32 <@roasbeef> we even have a command to do teh fee bumping for you as well 
13:33 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 256 seconds]     
13:34 < dongcarl> roasbeef: Cool, I'm writing a optech newsletter item about it so reading up. Let me know if there's anything I should point out in particular.
13:39 <@roasbeef> dongcarl: biggest thing is prob: fees are rising up a bit, and implementations taht don't have this implemented can be at risk if they can't get commitments in the chain in time 
13:39 <@roasbeef> since otherwise as you prob know, they just need to guess what their fee rate should be 
13:39 <@roasbeef> this is also linked to the cltv delta as well 
13:40 <@roasbeef> some impls may have this set to a very low value like 6 to 12 blocks or something 
13:40 <@roasbeef> so if they can't get the commitment in the chain _and_ get the second level HTLCs confirmed in the chain then bad things can happen 
13:41 <@roasbeef> the new format also lets you combine second level htlcs with the same time lock 
13:41 <@roasbeef> with single and anyonecanpay
13:42  * dongcarl reading
13:46 < dongcarl> sorry I'm admittedly quite ill-informed about lightning. To make sure I understand correctly: are you saying that the commitment transaction needs to be confirmed on chain before the cltv delta?
13:47 <@roasbeef> if the cltv delta expires, that means both incoming and outgoing htlcs have now expired 
13:48 <@roasbeef> so then there's a race condition
13:59 <@roasbeef> dongcarl: there's a time lock risk section in teh OG LN white paper 
14:00 < dongcarl> roasbeef: got it, will read and come back to this channel with questions
14:02 <@roasbeef> dongcarl: dope just lemmie know 
14:09 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
14:13 -!- manantial [~tecnecio_@unaffiliated/manantial] has quit [Remote host closed the connection]     
14:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 246 seconds]     
14:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
14:58 -!- lcpfnvcy [~mememe@snownose.org] has joined #lnd     
15:33 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd     
15:40 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]     
15:41 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
15:41 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
15:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
15:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
15:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
15:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
15:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
15:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
15:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
15:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
15:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
16:17 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 250 seconds]     
17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd     
18:37 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Remote host closed the connection]     
18:37 -!- fiddysat [~irc@gateway/tor-sasl/qprime] has joined #lnd     
19:09 -!- shibshop [~shop@204.232.243.35.bc.googleusercontent.com] has left #lnd []     
19:19 -!- jpe [~jp@fnord.cryptophone.de] has quit [Ping timeout: 246 seconds]     
19:21 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd     
19:32 -!- DeanWeen is now known as DeanGuss     
19:48 -!- fiddysat [~irc@gateway/tor-sasl/qprime] has quit [Ping timeout: 240 seconds]     
19:48 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd     
20:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
20:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]     
20:13 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
20:13 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
20:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd     
20:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]     
20:32 -!- treehug88 [~textual@pool-71-105-170-196.nycmny.fios.verizon.net] has quit [Remote host closed the connection]     
20:48 -!- jorijn_ [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has joined #lnd     
20:48 -!- jorijn [~jorijn@84-105-195-195.cable.dynamic.v4.ziggo.nl] has quit [Ping timeout: 256 seconds]     
20:58 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Ping timeout: 240 seconds]     
20:58 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd     
21:03 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Ping timeout: 240 seconds]     
21:10 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd     
21:11 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.]     
21:12 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #lnd     
21:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]