--- Day changed Fri Jul 13 2018 00:04 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 00:19 -!- eamonnw [~eamonnw@iceland.sdf.org] has joined #lnd 00:20 -!- jpe__ [~jpe@mue-88-130-111-248.dsl.tropolys.de] has joined #lnd 00:20 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 00:23 -!- jpe_ [~jpe@200116b8424b160010cc3b6f41a2f0d7.dip.versatel-1u1.de] has quit [Remote host closed the connection] 00:25 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 256 seconds] 00:25 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 00:27 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has joined #lnd 00:37 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has joined #lnd 00:37 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has quit [Changing host] 00:37 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 00:41 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 00:46 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 00:49 -!- bitconne1 [~conner@75.104.68.136] has quit [Read error: Connection reset by peer] 01:02 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 01:05 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd 01:07 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 256 seconds] 01:12 -!- Lucaash [c1f5222d@gateway/web/freenode/ip.193.245.34.45] has joined #lnd 01:14 -!- ziya [~ziya@82.103.140.46] has joined #lnd 01:23 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 01:28 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 276 seconds] 01:33 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 01:48 < jpe__> roasbeef, seems like I needed to restart the daemon in order to get it to rebroadcast 01:48 < jpe__> maybe I should be creating issues about some of these things? 01:58 -!- ziya [~ziya@82.103.140.46] has quit [Ping timeout: 248 seconds] 02:05 < lightningbot1> @jpe: please file (an) issue(s)! :) 02:05 < lightningbot1> much easier to keep track of than irc logs 02:42 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 02:46 -!- ziya [~ziya@82.103.140.46] has joined #lnd 03:01 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 03:25 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #lnd 03:29 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 244 seconds] 03:30 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 03:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 250 seconds] 03:38 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 03:40 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 03:41 -github-lnd:#lnd- [lnd] halseth opened pull request #1554: Filter out bitcoind mempool spends (master...bitcoind-mempool-spends) https://git.io/fNqU1 03:45 -!- spinza [~spin@155.93.246.187] has joined #lnd 03:56 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 04:01 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #lnd 04:03 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 04:05 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has joined #lnd 04:05 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has quit [Changing host] 04:05 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 04:05 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 04:15 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 04:16 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 04:19 -!- Beast [~quassel@59.6.64.209] has joined #lnd 04:20 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 276 seconds] 04:24 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 04:25 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has joined #lnd 04:25 -!- tiagotrs [~user@x2f7f90a.dyn.telefonica.de] has quit [Changing host] 04:25 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 04:31 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 04:35 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 04:42 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 04:52 < jpe__> Is it just me or is the documentation missing an explanation of the difference between an active and inactive channel? 04:56 -!- MaxSan [~user@185.9.19.107] has quit [Ping timeout: 244 seconds] 04:56 -!- dougsland [douglas@nat/redhat/x-djvtjylkjylbqbuz] has joined #lnd 05:04 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 05:48 < molz> jpe__, what do you mean? 05:51 < molz> "active" vs "inactive" is quite self-explanatory 05:54 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 06:11 -!- dougsland [douglas@nat/redhat/x-djvtjylkjylbqbuz] has quit [Ping timeout: 244 seconds] 06:15 -!- dougsland [douglas@nat/redhat/x-rybxdggnpblnvshf] has joined #lnd 06:27 < molz> we can say "on channel" and "off channel" but that doesn't sound quite correct or professional 06:33 < Veggen> I have seen a lot of people being confused. 06:34 < Veggen> hmm. I can feel a blog post brewing. That may or may not evolve to a begginers document to understanding Lighhtning. 06:35 < Veggen> and my keyboard lag is awful. 06:36 < jpe__> molz, is it? Active means somehow I can't use it, but why? How do I make it become active? 06:36 < Veggen> Actually at work, and I'm behind an evil corporate proxy that even do SSL inspection. And only way to IRC is if I access my smachine in the cloud by SSH...which is blocked. 06:38 < Veggen> So I set up my own shellinabox. SSH over https in a browser. 06:39 < Veggen> --->each and every keypress I type has to be inspected by this proxy ;P 06:40 -github-lnd:#lnd- [lnd] jraedisch opened pull request #1556: Add fwdinghistory support for relative times (master...relative-fwdinghistory) https://git.io/fNqCO 06:41 -!- TargetSpecies [4c6eb89f@gateway/web/freenode/ip.76.110.184.159] has joined #lnd 06:42 < TargetSpecies> Whats the appropriate way to restore the state? Had a hardware failure was able to successfully restore wallet with available balances however i'm unable to see my open channels via lncli 06:43 < molz> jpe__, no, "active" means the node is online, connected to your node and you can use the channel. Maybe this is just a language issue and a dictionary can help you understand the words? 06:44 < molz> TargetSpecies, currently we don't have a way to restore channels 06:45 < jpe__> but if the node is online and connected then why wouldn't the channel be active? 06:46 < jpe__> Why can't I use it? 06:46 < jpe__> active could have a lot of meanings, for example that it's currently being used "right" now 06:47 < molz> is the channel still in pending? 06:47 < jpe__> no it's open but inactive 06:47 < molz> then the node is offline 06:47 < jpe__> The other node is ASYNQ - i don't think that's offline 06:48 < molz> what's the URI? 06:48 < molz> or it could be something wrong on your side 06:49 < jpe__> 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@34.239.230.56:9735 06:50 < molz> jpe__, is this node in your 'listpeers' ? 06:50 < jpe__> apparently not 06:51 < TargetSpecies> molz, no these are channels that were established before the hardware failure 06:51 < molz> jpe__, can you try to connect to it again? 06:51 < jpe__> yeah I did 06:51 < molz> jpe__, is it in your 'listpeers' now? 06:51 < jpe__> weird I connected 3 times before but this time i see it in listpeers 06:52 < molz> yes there might be some issue between your node and this node, sometimes if there's a disagreement the other node would disconnect you instantly after you connect to it 06:53 < molz> so if you're not connected to the other node, your channel to that node would show "inactive" 06:54 < jpe__> hmm, could this still be a problem of running the master branch? Should I downgrade to the most recent tag? 06:54 < molz> this is more an issue between implementations 06:54 < molz> jpe__, i'm not sure 06:55 < molz> i'm connected to this node but i don't have a channel with it 06:55 < jpe__> now listchannels is hanging... 06:55 < TargetSpecies> molz, if there is no way to restore these channels is there at least a way to close them so as to restore the balances in them? will lncli allow me to close a channel it doesn't have in listchannels? 06:56 < molz> TargetSpecies, did you lose the .lnd files completely ? 06:57 < TargetSpecies> yup =( 06:57 < molz> i'm sorry but afaik there's not a way currently to get those channels back 06:58 < TargetSpecies> I'll definitely need to set up some backup schedule now that I know this 06:58 < molz> if you know the other parties you can ask them to close those channels but i'm not even sure if the coins will return to your lnd wallet 06:59 < molz> i don't think a backup schedule can help 06:59 < TargetSpecies> really? 06:59 < molz> do you have any old backup ? 07:00 < molz> you can try to run it, but it will be an old state and you will lose your coins in those channels, but if you think those coins would be lost anyways, might as well just give them away? :D 07:00 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd 07:02 < TargetSpecies> so just to clarify my understanding, If i set up a backup schedule where I back up the macaroons and the data etc. etc. and there is hardware failure. these cannot be used to restore channels? 07:02 < TargetSpecies> on another hardware 07:05 < molz> if your back up is right before the hardware failure and nothing has changed in the channel state, i think you can use that backup but it's iffy and risky, we still don't know if it can restore the currently state or an older state 07:05 -!- reallll [~belcher@unaffiliated/belcher] has joined #lnd 07:06 < molz> s/currently/current/ 07:07 < TargetSpecies> oh man, thats pretty scary then... even with backups of the state if hardware goes down you could lose channels -> lose funds 07:08 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds] 07:08 -!- reallll [~belcher@unaffiliated/belcher] has quit [Client Quit] 07:10 < TargetSpecies> do you think state is something you will be able to recover in the future provided your restoring a wallet or are there technical limitations that make this unfeasible 07:11 < TargetSpecies> molz, sorry for all the questions i'm just looking for the best way forward from this... 07:16 < Veggen> this obviously will have to get better. 07:17 < Veggen> Personally, I advocate backing up the files but only using them if all other options have been exhausted. 07:20 < TargetSpecies> Veggen, thanks! when u say all other options do you only mean restoring the original node hardware? 07:29 < Veggen> yup. 07:29 < Veggen> or, no. 07:29 < molz> :D 07:30 < Veggen> in case there is a bug, preventing LND from starting, for example, I'd advocate creating an issue and be patient instead of restoring. 07:31 < qubenix> Do connections created with --perm persist across restarts? 07:34 < Veggen> should do. 07:34 < qubenix> ty 07:34 < Veggen> but any channels you have should also try to reconnect automatically, so for channels that should not be needed. 07:35 < qubenix> ah, nice. 07:37 < molz> oh cool.. satoshis.place is back online, i was afraid that node was having serious issue there 07:37 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #lnd 07:37 < Veggen> wow. 07:38 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 07:38 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 07:38 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 07:38 < Veggen> satoshis.place is already listed in our evil corporate proxy filter as "games", and is blocked. 07:39 < Veggen> that was quick. 07:40 < Veggen> neither moneni nor lightningspin is yet. 07:42 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 248 seconds] 07:44 < molz> why is it blocked? 07:44 < molz> that's not right 07:45 < molz> it's the hottest node in LN right now, shouldn't be blocked by normies 07:46 < qubenix> what is a reliable way to find out if a node is running lnd? 07:46 < Veggen> In consider it proof of winning. 07:46 < Veggen> I regularly have to bypass the proxy anyhow. 07:46 < Veggen> Even for a lot of work purposes. 07:47 < Veggen> someone seems to run that software with default settings and "block as much as possible". 07:47 < Veggen> which means that I have a hard time finding even a lot of non-corporate IT security information. 07:56 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 07:56 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 07:57 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 07:57 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 08:00 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 08:00 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 08:00 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 08:00 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 08:00 < molz> qubenix, there's not a "reliable way" that i know of, but if you're running a node for a while you kinda can tell which nodes might be running lnd or not 08:01 < molz> and we do have info of some of the big nodes, like sleepyark and satoshis.place run c-lightning, but bitrefill and yalls run LND 08:04 < molz> lightningspin.com, lightninggem.com, coinpanic.com/Lightning/CommunityJar run LND, ACINQ runs Eclair, lightningconductor.com also runs Eclair i think 08:08 -!- tiagotrs_ [~user@x4e340779.dyn.telefonica.de] has joined #lnd 08:08 -!- tiagotrs_ [~user@x4e340779.dyn.telefonica.de] has quit [Read error: Connection reset by peer] 08:11 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 08:27 < molz> or lightningconductor.net rather (not a trustless service) 08:39 -!- dougsland [douglas@nat/redhat/x-rybxdggnpblnvshf] has quit [Ping timeout: 256 seconds] 09:26 -!- jchia_1 [~jchia@58.32.69.32] has quit [Quit: Leaving.] 09:30 -!- jchia_1 [~jchia@58.32.69.32] has joined #lnd 09:31 -!- jchia_1 [~jchia@58.32.69.32] has quit [Client Quit] 09:31 -!- jchia_1 [~jchia@45.32.62.73] has joined #lnd 09:32 -!- grafcaps [~haroldbr@104.137.194.255] has joined #lnd 09:35 -!- daouzo23 [~daouzo23@wl-loc177-82.liwest.at] has joined #lnd 09:38 -!- jchia_1 [~jchia@45.32.62.73] has quit [Remote host closed the connection] 09:38 -!- jchia_1 [~jchia@58.32.69.32] has joined #lnd 09:40 -!- daouzo23 [~daouzo23@wl-loc177-82.liwest.at] has quit [Disconnected by services] 09:40 -!- daouzo235 [~daouzo23@wl-loc177-82.liwest.at] has joined #lnd 09:43 -!- daouzo2355 [~daouzo23@wl-loc177-82.liwest.at] has joined #lnd 09:43 -!- daouzo2355 [~daouzo23@wl-loc177-82.liwest.at] has quit [Remote host closed the connection] 09:44 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has joined #lnd 09:45 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has quit [Client Quit] 09:46 -!- daouzo235 [~daouzo23@wl-loc177-82.liwest.at] has quit [Ping timeout: 240 seconds] 10:03 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 10:15 < qubenix> ty molz 10:28 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 10:38 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 10:38 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 10:38 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 10:39 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 10:41 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #lnd 10:43 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 256 seconds] 10:56 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 10:57 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 11:00 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 11:10 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 11:10 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 11:10 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 11:10 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 11:12 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 11:12 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has joined #lnd 11:12 -!- tiagotrs [~user@x4e340779.dyn.telefonica.de] has quit [Changing host] 11:12 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 11:20 -!- digi_james [~JC_acct@216-144-16-94.dyn.cable.fcom.ch] has quit [Ping timeout: 240 seconds] 11:21 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 11:24 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 268 seconds] 11:24 -!- digi_james [~JC_acct@216-144-16-94.dyn.cable.fcom.ch] has joined #lnd 11:40 -!- qubenix_ [~qubenix@38.132.120.4] has joined #lnd 11:41 -!- qubenix [~qubenix@107.181.164.1] has quit [Disconnected by services] 11:41 -!- qubenix_ is now known as qubenix 12:00 -!- cryptodechange [~cryptodec@host86-142-232-112.range86-142.btcentralplus.com] has quit [Ping timeout: 248 seconds] 12:03 -!- polydin [~delphi@2602:306:b8b6:b970:4ce2:3ae1:2d0f:aa43] has joined #lnd 12:09 -!- pr1 [~Thunderbi@pD9526933.dip0.t-ipconnect.de] has joined #lnd 12:12 -!- pr1 [~Thunderbi@pD9526933.dip0.t-ipconnect.de] has quit [Quit: pr1] 12:22 -!- deusexbeer [~deusexbee@079-170-137-238-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 244 seconds] 12:22 -!- deusexbeer [~deusexbee@093-092-177-229-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:25 -!- cryptodechange [~cryptodec@host86-142-232-112.range86-142.btcentralplus.com] has joined #lnd 12:33 -!- ziya [~ziya@82.103.140.46] has quit [Ping timeout: 260 seconds] 12:35 -!- ziya [~ziya@82.103.140.46] has joined #lnd 12:43 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 12:43 -!- ziya [~ziya@82.103.140.46] has quit [Ping timeout: 240 seconds] 12:45 -github-lnd:#lnd- [lnd] Mischi opened pull request #1558: release: create source archive with vendor folder (master...patch-1) https://git.io/fNqxf 12:47 < Veggen> Hmm. Someone should create repositories with official LND releases for different platform. But actually even more useful, known good in-between snapshots :) 12:47 < Veggen> maybe it's time to create my first Ubuntu repository. 12:47 < Veggen> but not this weekend, going to a couple of mountains. 13:13 <@roasbeef> TargetSpecies: how'd you restore after the hardware failure? was the channeldb corrupted? 13:14 <@roasbeef> Veggen: official releases? we host them on github and keybase atm 13:15 < Veggen> yah, I know. 13:16 < TargetSpecies> I attempted just restoring the wallet on a new hardware 13:17 < TargetSpecies> but everything appears jacked up 13:17 < TargetSpecies> 1ml for example is saying I have 4 open channels 13:17 < TargetSpecies> https://1ml.com/node/03e9e0f9aaba1ccbb702e3f862b8eddae3f2d55944595fb09d758fedf18cc385a5 13:17 < TargetSpecies> but lncli is reporting I have nothing open 13:18 < TargetSpecies> I restored by installing LND as if it were a new installation on the new hardware 13:18 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has joined #lnd 13:18 -github-neutrino:#lnd- [neutrino] Roasbeef closed pull request #63: [wip] mainnet readiness (master...mainnet-readiness) https://git.io/vhz8b 13:18 < TargetSpecies> then used lncli create -> restore wallet 13:19 < Veggen> TargetSpecies: you should ditch that one, and try to recover the files instead. 13:19 < TargetSpecies> ditch the wallet? 13:20 < Veggen> yah, the one you restored. 13:20 < Veggen> recovering funds in channels can not be done, that way. 13:20 < Veggen> it's better to try to recover the files. 13:20 < Veggen> often it's not even that difficult to do. 13:20 < TargetSpecies> lets assume I'm able to recover the old files, is there a way to get back? 13:20 < Veggen> ....to what? 13:21 < TargetSpecies> to my node in a stable state with correct data 13:21 < Veggen> could be. If the files are unharmed. 13:21 -!- daouzo23 [~daouzo2__@wl-loc177-82.liwest.at] has joined #lnd 13:22 < TargetSpecies> i'm worried now that I restored the wallet on the recovery autopilot made a new connection, which I closed... but wouldn't that affect the old state now? 13:23 < TargetSpecies> or will the old state be able to interpret that when it catches up through the blocks? 13:23 < TargetSpecies> I'm in the process of trying to do some disk recovery on the old hardware so hopefully I can get it 13:24 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has quit [Ping timeout: 264 seconds] 13:26 < TargetSpecies> @roasbeef: If i'm able to find the old "state" files, would the restore I attempted complicate recovery of the node? 13:27 < TargetSpecies> at this point I would be happy just getting the funds out of the channels into the wallet and back on main chain to send to a new wallet and start over. 13:28 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 13:30 < TargetSpecies> @roasbeef: also wondering if recovering a wallet in the future will also recover the state or are there technical reasons this is not possible? 13:51 -!- eamonnw [~eamonnw@iceland.sdf.org] has quit [Remote host closed the connection] 13:53 -!- eamonnw [~eamonnw@iceland.sdf.org] has joined #lnd 13:54 -!- eamonnw [~eamonnw@iceland.sdf.org] has quit [Remote host closed the connection] 14:05 -!- eamonnw [~eamonnw@iceland.sdf.org] has joined #lnd 14:12 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 240 seconds] 14:26 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has joined #lnd 14:26 -!- drexl_ [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 14:27 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Write error: Connection reset by peer] 14:27 -!- lndbot [~lndbot@138.197.213.35] has quit [Read error: Connection reset by peer] 14:27 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Remote host closed the connection] 14:27 -!- lndbot [~lndbot@138.197.213.35] has joined #lnd 14:27 -!- drexl_ is now known as drexl 14:28 -!- daouzo2___ [~daouzo2__@wl-loc177-82.liwest.at] has quit [Client Quit] 14:28 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #lnd 14:29 -!- daouzo23 [~daouzo2__@wl-loc177-82.liwest.at] has quit [Ping timeout: 244 seconds] 14:29 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 244 seconds] 14:37 -!- JackH [~laptop@host-80-47-83-61.as13285.net] has joined #lnd 14:59 -!- Giszmo [~leo@ip-251-233.219.201.nextelmovil.cl] has joined #lnd 15:00 -!- TargetSpecies [4c6eb89f@gateway/web/freenode/ip.76.110.184.159] has quit [Ping timeout: 252 seconds] 15:58 -!- MaxSan [~user@185.9.19.107] has joined #lnd 16:00 -!- Giszmo [~leo@ip-251-233.219.201.nextelmovil.cl] has quit [Ping timeout: 244 seconds] 16:15 -!- Giszmo [~leo@ip-167-228-107-190.nextelmovil.cl] has joined #lnd 16:21 <@roasbeef> hm TargetSpecies left :/ 16:21 <@roasbeef> dunno how he did a recovery 16:59 < molz> roasbeef, he had a hardware problem: Whats the appropriate way to restore the state? Had a hardware failure was able to successfully restore wallet with available balances however i'm unable to see my open channels via lncli 16:59 < molz> roasbeef, then he did this: I restored by installing LND as if it were a new installation on the new hardware 16:59 < molz> then used lncli create -> restore wallet 17:04 <@roasbeef> id he have the old db? 17:04 <@roasbeef> did* 17:04 <@roasbeef> channel.db that is 17:16 < molz> i don't think so, i asked him if he lost all .lnd files he said yes 17:17 < molz> roasbeef, TargetSpecies, did you lose the .lnd files completely ? 17:17 < molz> yup =( 17:18 < molz> it's in the scrollup 17:18 -!- Giszmo [~leo@ip-167-228-107-190.nextelmovil.cl] has quit [Ping timeout: 264 seconds] 17:37 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has joined #lnd 17:37 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 17:46 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 17:54 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 17:56 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 256 seconds] 17:59 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 264 seconds] 18:12 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 260 seconds] 18:25 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 18:30 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 18:46 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 18:49 -18VAEMJJ5:#lnd- [lnd] Roasbeef closed pull request #1326: multi: switch over all imports to depend on btcsuite proper, no longer the roasbeef forks (master...btcsuite-switch) https://git.io/vh4l6 18:49 -7GHABCUVN:#lnd- [lnd] Roasbeef pushed 9 new commits to master: https://git.io/fNmnl 18:49 -7GHABCUVN:#lnd- lnd/master 6f60f13 Olaoluwa Osuntokun: multi: switch over import paths from roasbeef/* to btcsuite/* 18:49 -7GHABCUVN:#lnd- lnd/master 584834a Olaoluwa Osuntokun: makefile: update to fetch btcsuite/btcd instead of roasbeef/btcd 18:49 -7GHABCUVN:#lnd- lnd/master 054d449 Olaoluwa Osuntokun: docker/btcd: fix comment in docker file w.r.t old roasbeef fork 18:50 <@roasbeef> heads up y'all: master has been switched over to btcsuite now 18:50 <@roasbeef> my roasbeef forks are no longer a thing 18:50 <@roasbeef> if you've been running a node to serve neutrino, you'll need to switch it over to `btcsuite/btcd` now, and then run with `--dropcfindex` the first time 18:50 <@roasbeef> afterwards, it'll re-index and also update the regular block header index if you haven't done that yet as well 18:52 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 18:54 -!- grafcaps [~haroldbr@050-090-130-019.res.spectrum.com] has joined #lnd 18:59 -!- grafcaps [~haroldbr@050-090-130-019.res.spectrum.com] has quit [Ping timeout: 260 seconds] 19:07 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 19:12 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 19:28 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 19:30 -!- grafcaps [~haroldbr@050-090-130-019.res.spectrum.com] has joined #lnd 19:33 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 19:34 -!- grafcaps [~haroldbr@050-090-130-019.res.spectrum.com] has quit [Ping timeout: 260 seconds] 19:36 -!- navybluesilver1 [~user@36.88.34.196] has joined #lnd 19:36 -!- navybluesilver1 [~user@36.88.34.196] has left #lnd [] 19:49 -!- jchia_1 [~jchia@58.32.69.32] has quit [Ping timeout: 244 seconds] 19:49 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 19:54 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 264 seconds] 19:54 -!- jchia_1 [~jchia@58.32.69.32] has joined #lnd 20:03 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 20:10 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 20:14 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 20:31 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 20:35 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 20:41 -github-neutrino:#lnd- [neutrino] Roasbeef opened pull request #74: multi: update usage of filters to match latest version of BIP 158 (master...gcs-modifications-on-neutrino-fixes) https://git.io/fNmCA 20:52 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 20:56 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 21:13 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 21:17 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 21:33 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 21:38 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 21:54 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 21:59 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 22:08 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #lnd 22:13 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 22:15 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 22:20 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 244 seconds] 22:25 -!- bitconner [~conner@107.72.96.107] has joined #lnd 22:36 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 22:41 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 22:55 -!- JackH [~laptop@host-80-47-83-61.as13285.net] has quit [Ping timeout: 264 seconds] 22:57 -!- bitconner [~conner@107.72.96.107] has quit [Ping timeout: 256 seconds] 22:57 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 23:02 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 260 seconds] 23:18 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 23:23 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 264 seconds] 23:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 250 seconds] 23:39 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #lnd 23:44 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has quit [Ping timeout: 240 seconds] 23:53 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]