--- Log opened Tue Apr 06 00:00:18 2021 00:11 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 00:12 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 00:19 -!- mips [~mips@gateway/tor-sasl/mips] has joined #lnd 01:11 -!- laptop [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has joined #lnd 01:40 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 01:40 < lnd-bot> [lnd] halseth merged pull request #5172: lnrpc: Change State -> state in SubscribeStateResponse (master...state-small) https://github.com/lightningnetwork/lnd/pull/5172 01:40 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 01:40 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 01:40 < lnd-bot> [lnd] halseth pushed 2 commits to master: https://github.com/lightningnetwork/lnd/compare/786568fa460a...2338a12729a0 01:40 < lnd-bot> lnd/master a7c43fb Hampus Sjöberg: lnrpc: Change State -> state in SubscribeStateResponse 01:40 < lnd-bot> lnd/master 2338a12 Johan T. Halseth: Merge pull request #5172 from hsjoberg/state-small 01:40 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 02:04 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Remote host closed the connection] 02:05 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd 03:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 03:54 < lnd-bot> [lnd] halseth opened pull request #5178: make: pass mobile subserver prefix to docker when generating mobile RPC (master...mobile-docker-prefix) https://github.com/lightningnetwork/lnd/pull/5178 03:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 04:32 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 04:33 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 04:35 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 04:35 < lnd-bot> [lnd] halseth merged pull request #5010: [mobile] Allow state API on mobile, simplify callback mechanism (master...walletunlocker-unify-mobile) https://github.com/lightningnetwork/lnd/pull/5010 04:35 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 04:35 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 04:35 < lnd-bot> [lnd] halseth pushed 6 commits to master: https://github.com/lightningnetwork/lnd/compare/2338a12729a0...173342a46379 04:35 < lnd-bot> lnd/master 8789247 Johan T. Halseth: print current falafel version 04:35 < lnd-bot> lnd/master db28e7c Johan T. Halseth: lnd: consolidate WalletUnlocker- and AdminAuthOptions 04:35 < lnd-bot> lnd/master cf5b0b7 Johan T. Halseth: mobile: include stateservice, use same listener for all services 04:35 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 05:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 05:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 05:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 05:54 < lnd-bot> [lnd] halseth merged pull request #5178: make: pass mobile subserver prefix to docker when generating mobile RPC (master...mobile-docker-prefix) https://github.com/lightningnetwork/lnd/pull/5178 05:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 05:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 05:54 < lnd-bot> [lnd] halseth pushed 2 commits to master: https://github.com/lightningnetwork/lnd/compare/173342a46379...d1c7059f1469 05:54 < lnd-bot> lnd/master 2868b22 Johan T. Halseth: make: pass mobile subserver prefix to docker when generating mobile RPC 05:54 < lnd-bot> lnd/master d1c7059 Johan T. Halseth: Merge pull request #5178 from halseth/mobile-docker-prefix 05:54 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 06:02 -!- reallll is now known as belcher 06:48 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Remote host closed the connection] 06:49 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd 06:49 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 06:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 07:34 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 07:34 < lnd-bot> [lnd] GameXG opened pull request #5180: lnd: fix #5179 panic: runtime error: invalid memory address or nil po… (master...master2) https://github.com/lightningnetwork/lnd/pull/5180 07:34 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 07:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 07:49 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 08:01 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Remote host closed the connection] 08:37 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Ping timeout: 240 seconds] 08:38 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 08:38 -!- MalkbabY_ [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 08:39 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd 10:02 -!- mol_ [~mol@unaffiliated/molly] has quit [Read error: Connection reset by peer] 10:03 -!- mol [~mol@unaffiliated/molly] has joined #lnd 10:36 -!- Talkless [~Talkless@mail.dargis.net] has joined #lnd 11:10 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 11:11 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 11:27 -!- laptop [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has quit [Remote host closed the connection] 11:27 -!- laptop [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has joined #lnd 11:32 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 11:32 < lnd-bot> [lnd] yyforyongyu opened pull request #5181: itest: move funding tests into one file (master...refactor-itest) https://github.com/lightningnetwork/lnd/pull/5181 11:32 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 11:52 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Remote host closed the connection] 11:56 -!- deusexbeer [~deusexbee@080-250-076-051-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 11:57 -!- deusexbeer [~deusexbee@080-250-076-051-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:13 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 12:32 -!- mol_ [~mol@unaffiliated/molly] has joined #lnd 12:35 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 12:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 12:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 12:52 -!- MalkbabY_ [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 12:52 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 12:55 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd 12:57 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 12:58 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 14:42 -!- Kostenko [~Kostenko@2001:8a0:724d:7f00:6ab5:a213:a600:6f33] has joined #lnd 14:44 -!- Kostenko [~Kostenko@2001:8a0:724d:7f00:6ab5:a213:a600:6f33] has quit [Client Quit] 15:02 -!- Snowgoose [5efe33c2@94.254.51.194] has joined #lnd 15:04 < Snowgoose> Could anyone try to identify why this channel of mine has become stuck in limbo? : 15:04 < Snowgoose> lncli pendingchannels 15:05 < Snowgoose> { 15:05 < Snowgoose>     "total_limbo_balance": "1563213", 15:05 < Snowgoose>     "pending_open_channels": [ 15:05 < Snowgoose>     ], 15:05 < Snowgoose>     "pending_closing_channels": [ 15:05 < Snowgoose>     ], 15:05 < Snowgoose>     "pending_force_closing_channels": [ 15:05 < Snowgoose>     ], 15:05 < Snowgoose>     "waiting_close_channels": [ 15:05 < Snowgoose>         { 15:05 < Snowgoose>             "channel": { 15:05 < Snowgoose>                 "remote_node_pub": "02bd2ed32599f0a52ce507ee18366623e51c639f7f5729e9b9029799cd6d8bb8cd", 15:05 < Snowgoose>                 "channel_point": "c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1", 15:05 < Snowgoose>                 "capacity": "1578942", 15:05 < Snowgoose>                 "local_balance": "1563213", 15:05 < Snowgoose>                 "remote_balance": "0", 15:05 < Snowgoose>                 "local_chan_reserve_sat": "15789", 15:07 < Snowgoose> I couldnt find either of the local or remote txid in a block explorer so i guessed it was due to some fee being to low? But i tried "bumpclosefee" but still the channel has been stuck for a long time 15:09 < Snowgoose> Running lnd 0.10.0-beta btw. 15:16 < mol_> Snowgoose, it looks like you do have a channel and the local balance is 1563213 15:16 < mol_> Snowgoose, have you tried to restart the node? 15:16 < Snowgoose> yeah, many times over the past days 15:17 < Snowgoose> It is my only remaining channel, wanted to take this node down and start fresh since i was seeing unstable performance, but i dont want to until i get my funds out. 15:18 < mol_> if you want to get your fund out of this channel you need to close the channel 15:19 < Snowgoose> How though, when i do listchannels its not there 15:19 < Snowgoose> lncli listchannels 15:19 < Snowgoose> { 15:19 < Snowgoose>     "channels": [ 15:19 < Snowgoose>     ] 15:19 < Snowgoose> } 15:20 < Snowgoose> i can add that i did close all my channels through "zap". the others closed successfully but this one didnt. Its still listed as "closing" in zap and no controls were available, so i tried checking out the cli but not sure what to do there 15:20 < lndbot> any log messages for the channel that could indicate why it’s stalled? 15:21 < lndbot> the channel is still unspent in the chain, so seems the closing transaction isn’t propagating for whatever reason 15:22 < Snowgoose> i tried to connect to the peer but it said that peer was already connected so that doesn't seem the issue at least. 15:22 < Snowgoose> not very good at navigating the logs 15:25 < Snowgoose> 66]: 2021-04-05 23:19:38.347 [WRN] CNCT: Channel c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1 is in state ChanStatusCoopBroadcasted, but no coop closing tx to re-publ 15:25 < Snowgoose> this seems relevant? this is from the lnd service at startup 15:26 < mol_> wilmer, it looks like maybe it's a zap issue? 15:26 < mol_> Snowgoose, have you asked for help in the zap slack? 15:28 < Snowgoose>  Dispatching historical spend rescan for outpoint=c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1, script=0 5956ec4ae4669a56dd9f1427552582542cfa85721 15:28 < Snowgoose> ChannelArbitrator(c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1): starting state=StateDefault, trigger=chainTrigger, triggerHeight=677931 15:28 < Snowgoose>  Close observer for ChannelPoint(c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1) active 15:28 < Snowgoose>  Starting contract observer, watching for breaches. 15:28 < Snowgoose> its that channel atleast, but i dont know if that is normal or not 15:29 < Snowgoose> alright mol, no i havent yet. but from zap there is nothing i can do, i think i need to resolve it through the cli 15:31 < mol_> Snowgoose, c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b is the TXID for the channel when you opened the channel, and it looks like the closing didn't happen 15:31 < mol_> Snowgoose, you can see the tx here: https://www.smartbit.com.au/tx/c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b 15:42 < Snowgoose> so the opening tx had a fee of 1sat/vbyte, can this be the cause of it being stuck now? but then i should see the closing tx somewhere just not confirmed right? 15:45 <@roasbeef> Snowgoose: can you upgrade to v0.12.1 if possible Snowgoose ? 15:46 <@roasbeef> also paste bins are better vs dumping it on IRC as well 15:47 <@roasbeef> what's your node backend being used? 15:47 <@roasbeef> looking on chain, the transaction has been confirmed for a while now, maybe it missed teh cinformation ? 15:47 <@roasbeef> Snowgoose: I think first try to update if possible 15:47 < Snowgoose> the closing tx is confirmed? where can i see that? 15:48 <@roasbeef> err now sorry that's teh funding trnasaction, but not it doesn't appear to be actually closed 15:48 <@roasbeef> on restart, lnd will attempt to rebroadcast the transaction 15:48 <@roasbeef> so maybe that's just not what's propagating? 15:48 <@roasbeef> if yuo're just trying to close it, then maybe the fee is too low and it's being rejected? 15:48 < Snowgoose> yeah for sure, if you think upgrading could help i can do it. was afraid it could make things worse though 15:49 <@roasbeef> nah I think it could help some, as there's more debugging info, etc 15:49 < Snowgoose> i did restart lnd a couple of times. my backend is bitcoind running on the same rpi 15:49 <@roasbeef> yeah so afaict it broadcsated the co-op close transaction, and it hasn't been confirmed for w/e reason 15:49 < Snowgoose> but i have both sent and received transactions through my node while waiting for this one, so it seems my node can broadcast fine 15:49 <@roasbeef> you could also try to just force close it possibly, the commitment transaction is usually at a higher fee rate 15:50 <@roasbeef> if you look at the bitcoind logs, you should be able to tell if it's being rebroadcast or not 15:51 < Snowgoose> how could i tell the fee is too low, and how would i increase it? i tried "lncli wallet bumpclosefee c927979fd2420d66c8fa28b16f7befd4ed82f9f9adc05431dbc018fe78c7410b:1 --sat_per_byte 150" 15:51 <@roasbeef> you need to try to bump the _co op close_ trnasaction instead 15:51 <@roasbeef> that txid is the funding transactino 15:52 <@roasbeef> also if you did a co-op close w/ a newer version of lnd, then it won't resume if things broke down for w/e reason, meaning at times a force close is the only way forward 15:53 < Snowgoose> and how do i find that transaction, its not the "local_txid" or "remote_txid" from my first paste? (sorry by the way) 15:54 < Snowgoose> im fine with either the bump fee or force close, but right now i dont know how to do either of the two 15:59 < Snowgoose> Something like - restart lnd while watching bitcoind log output, try to find a transaction being broadcasted and assume this is my closing tx, then bump? 16:00 < Snowgoose> This i could try tomorrow, and upgrading lnd if im not successful 16:00 <@roasbeef> there should be another txid there 16:01 <@roasbeef> Snowgoose: if you know how to use the command line, force close isn't too hard 16:01 <@roasbeef> lncli closechannel --funding_txid= --output_index= --force 16:01 <@roasbeef> it should return w/ a txid 16:01 <@roasbeef> then the process has started, and you'll just need to wait for the CSV delay 16:08 -!- laptop [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has quit [Ping timeout: 265 seconds] 16:15 -!- lnd-bot [~lnd-bot@165.227.7.29] has joined #lnd 16:15 < lnd-bot> [lnd] PierreRochard opened pull request #5182: rpcserver+lnrpc: make graph node addresses consistent (master...node-update-addresses) https://github.com/lightningnetwork/lnd/pull/5182 16:15 -!- lnd-bot [~lnd-bot@165.227.7.29] has left #lnd [] 16:22 -!- common [~common@unaffiliated/common] has joined #lnd 16:24 -!- mol [~mol@unaffiliated/molly] has joined #lnd 16:27 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 268 seconds] 17:00 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 17:01 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 17:20 < cluelessperson> Hi there. I have an old lightning sqlite data dir, and I'm not sure if it contains funds or not 17:24 < cluelessperson> How do I examine this and close it out? 17:24 < cluelessperson> maybe I should just try to figure out which version it was and recover it 17:29 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 17:33 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 17:51 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:51 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 18:03 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 18:03 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 18:12 -!- mol_ [~mol@unaffiliated/molly] has joined #lnd 18:16 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 268 seconds] 18:19 <@roasbeef> cluelessperson: try #c-lightning 18:26 -!- mol [~mol@unaffiliated/molly] has joined #lnd 18:29 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 19:22 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 19:22 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 19:35 -!- ironhelix [~x@2.57.169.15] has joined #lnd 19:35 -!- RusAlex [~Chel@unaffiliated/rusalex] has quit [Ping timeout: 240 seconds] 19:38 -!- dermoth_ [~dermoth@unaffiliated/dermoth] has joined #lnd 19:39 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined #lnd 19:41 -!- dermoth [~dermoth@unaffiliated/dermoth] has quit [Ping timeout: 260 seconds] 20:21 < nibbier> how do I figure out if my watchtower is up to date? "lncli tower info" gives me the URI, not more. on the client, tower/towers gives me active_session_candidate (true/false if i add/remove the tower),num_sessions (3,5 now 7) and sessions (usually empty array) 20:21 <@roasbeef> up to date as in like synced to the chain? 20:22 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #lnd 20:22 < nibbier> no, up to date, as has all my latest chain states 20:22 < nibbier> channel states, like, protecting my node 20:23 < nibbier> wtclient stats hat num_backups and num_pending_backups at an equally high number (210), i restarted everything, no it's "0" for both. no fails/exhausted. currently num_sessions_acquired 4 20:24 < nibbier> hat=had 20:24 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds] 20:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 20:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 20:48 < nibbier> okay, now I increased verbosity on the tower to DEBUG. getting now "State update 6 accepted for XX..." and "ending MsgStateUpdateReply(code=0 last_applied=6) to XX". This looks like the tower got the clients state updates. yet on the client num_backups=num_pending_backups=6, 20:49 < nibbier> so still... how can the client figure out, that it's states are stored with the WT 20:49 <@roasbeef> you want like challenge and response or something? 20:49 <@roasbeef> you should see some client logs related to like negotiating sessions (basically blocks of storage for states) 20:50 <@roasbeef> which version of lnd are you running? 20:50 -!- mips [~mips@gateway/tor-sasl/mips] has joined #lnd 21:05 < nibbier> roasbeef: I'm on 0.12.1-beta. I need to monitor somehow if my WT is actually being a WT. Some status I can query to see "all current channel status data was successfully commited to 2 out of 3 watchtowers" 21:06 < nibbier> how would I notice if a configured WT is not reachable, responding, saving my states? 21:06 -!- qprime [~irc@gateway/tor-sasl/qprime] has quit [Ping timeout: 240 seconds] 21:06 <@roasbeef> hmm yeah other than the logs rn, we're def missing the ability to monitor things passively and do things like check the total # of states, etc 21:07 <@roasbeef> nibbier: would you be inclined to make an issue desribing some of your desired functionality? 21:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 21:07 < nibbier> roasbeef: sure! 21:07 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 21:07 <@roasbeef> thx :) 21:08 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 240 seconds] 21:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 21:16 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has quit [Remote host closed the connection] 21:16 -!- MalkbabY [MalkbabY@gateway/vpn/protonvpn/malkbaby] has joined #lnd 21:28 -!- yzernik [~yzernik@107-194-14-24.lightspeed.miamfl.sbcglobal.net] has quit [Quit: ZNC 1.7.5 - https://znc.in] 21:29 -!- yzernik [~yzernik@107-194-14-24.lightspeed.miamfl.sbcglobal.net] has joined #lnd 21:33 -!- qprime [~irc@gateway/tor-sasl/qprime] has joined #lnd 21:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 22:10 -!- mol_ [~mol@unaffiliated/molly] has joined #lnd 22:14 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 23:35 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 23:35 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd --- Log closed Wed Apr 07 00:00:18 2021