--- Day changed Wed Feb 20 2019 00:43 < Veggen> RusAlex: yes, any active channel has to have an open TCP connection. 00:45 < RusAlex> with peer or with any node in network ? 00:45 < RusAlex> I mean peer=node that you opened channel with 01:20 < Veggen> RusAlex: with channel peers only. 01:22 < Veggen> if that TCP connection is broken, the channel goes inactivNodes will usually try to reconnect and reactivate channels by themselves, but sometimes - especially if there has been IP address changes in either end - an lncli connect might help it. 01:52 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:56 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 255 seconds] 01:59 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 255 seconds] 02:07 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 02:11 -!- trotski2000 [uid206086@gateway/web/irccloud.com/x-kjqfdeqqqbimsgcg] has joined #lnd 02:12 < trotski2000> hi guys 02:12 < trotski2000> I have a casa node 02:12 < trotski2000> how many channels would recommend me to open to make sure I'm well connected? 02:19 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 02:33 -!- foureighttwonine [~foureight@82.102.28.107] has joined #lnd 02:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 02:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 02:39 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 02:44 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 246 seconds] 02:59 -!- booyah [~bb@193.25.1.157] has joined #lnd 03:09 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has quit [Ping timeout: 246 seconds] 04:15 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has joined #lnd 04:33 -!- foureighttwonine [~foureight@82.102.28.107] has quit [Read error: Connection reset by peer] 04:34 -!- foureighttwonine [~foureight@82.102.28.107] has joined #lnd 04:45 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Quit: Leaving] 04:48 -!- siom [~siom@83.97.23.43] has joined #lnd 05:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:24 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 05:29 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 06:13 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 07:01 -!- miketwenty1 [63998f99@gateway/web/freenode/ip.99.153.143.153] has joined #lnd 07:08 -!- angelonE is now known as angelone 07:08 < miketwenty1> Hello, 07:18 -!- greypw [~greypw@45.76.80.171] has quit [Ping timeout: 255 seconds] 07:20 -!- Highway61 [~Thunderbi@96.44.142.122] has quit [Ping timeout: 246 seconds] 07:25 -!- greypw [~greypw@2001:19f0:6c01:361:5400:ff:fe78:4149] has joined #lnd 07:45 < miketwenty1> unlocking my lncli results in the lnd crashing. I want to try to restore my lnd instance to another node. 07:45 < miketwenty1> Question 1: How do I propperly kill my lnd daemon? 07:45 < miketwenty1> Question 2: Which files are needed for a full restore? 07:45 < miketwenty1> Question 3: Would I then just use the seed to recover.. then kill lnd.. restore files.. then start lnd back up? 07:46 < miketwenty1> this is in reference to this github issue that you closed @roasbeef 07:46 < miketwenty1> https://github.com/lightningnetwork/lnd/issues/2574 07:47 < Veggen> miketwenty1: did you talk to Casa? (as he suggested?) 07:49 < Veggen> currently,. backup options for LND is quite lacking. that is about to improve, though. 07:50 < Veggen> that said, it's good to backuip the .lnd directory - especially channel.db. But using that backup should be considered a last resort that might lead to loss of money too. 07:50 < Veggen> (likely will) 07:50 < Veggen> ...but if you have lost all of channel.db, it's worth it to try to save some channel funds. 08:00 -!- foureighttwonine [~foureight@82.102.28.107] has quit [Ping timeout: 245 seconds] 08:01 < miketwenty1> @Veggen im here for a reason.. i don't want to be disrespectful.. to casa.. but im just trying to recover my btc 08:02 < miketwenty1> so.. the best route is just backing up .lnd folder 08:02 < miketwenty1> Veggen: i will try this thanks 08:03 < Veggen> if lnd node is crashed, then salvaging .lnd is your best option. 08:04 < Veggen> that said, I too eagerly await static channel backups :) 08:04 < miketwenty1> correct me if im wrong.. 08:05 < miketwenty1> but after static channel backups... lnd becomes much less rektless 08:05 < Veggen> yup. 08:05 < miketwenty1> as in.. unless a bug is found or something.. you should have everything to restore channels and what not 08:05 < miketwenty1> and prevent loss of funds 08:06 < Veggen> yes, but you still rely upon a cooperative channel partner. 08:06 < miketwenty1> you can force close and do a wait out .. no? 08:07 < molz> yes i think so 08:07 < Veggen> well. static channel backuyps are...static. you need your channel partner to provide you with the state. 08:08 < Veggen> if I understood correctly. 08:10 < molz> so it seems to be the norm now, at least one or two reports of node failures on raspi everyday 08:10 < miketwenty1> so in other words.. with a partner that doesn't send you the state.. you are still "f'd"? 08:10 < molz> you can't have a backup with a partner who doesn't have DLP 08:10 < miketwenty1> DLP? 08:11 < molz> so in order to have SCB your partner's node also has Data Loss Protection 08:11 < Veggen> See https://github.com/lightningnetwork/lnd/pull/2313 08:14 < molz> My probes fail mostly due to temporary failures, not insufficient capacity... 08:14 < Veggen> molz, have you tested SCB? 08:14 < Veggen> on testnet? 08:14 < molz> not sure if their probing method is 100 percen correct but it sounds possible due to nodes being down and most of those nodes are on bad hardware 08:15 < molz> Veggen, yea im running a 2313 node on testnet 08:15 < Veggen> molz: tried losing channel.db and recovering? 08:15 < molz> it's not complete yet 08:16 < molz> if you look at that PR there're still a few things done before i can try the recovery 08:16 < Veggen> ah, ok. 08:16 < Veggen> I plan to test that on testnet myself, first possibility :) 08:17 < Veggen> no backup strategy is good unless you have tested it. 08:17 < Veggen> backup is easy, it's restore that's difficult. 08:17 < molz> i think once roasbeef get this part checked "* real world recovery attempts" we can try the recovery 08:21 < Veggen> hmm...will havew a look at it tonight. Maybe try wih a channel and see what happen:s :) 08:24 < miketwenty1> what is the proper way to kill LND daemon? 08:24 < miketwenty1> just run a kill ? 08:25 -!- angelone is now known as angelonE 08:25 < miketwenty1> i want to kill lnd before getting a backup of .lnd 08:25 < miketwenty1> im also wondering if killing lnd daemon will exit the docker container.. .... 08:26 < ysangkok> miketwenty1: lncli stop Stop and shutdown the daemon. 08:26 < miketwenty1> lncli stop [lncli] Wallet is encrypted. Please unlock using 'lncli unlock', or set password using 'lncli create' if this is the first time starting lnd. 08:26 < miketwenty1> if i unlock.. lnd crashes and i exit the docker container 08:27 < ysangkok> hmmmm 08:27 < miketwenty1> so.. maybe if i unlock.. and then immediately stop it 08:28 < peleion> miketwenty1: Stopping the process in the container stops the container as well 08:28 < miketwenty1> yeah.. i think there is a way to "attach" or something into a docker container to see the state of the fs 08:28 < miketwenty1> after it dies 08:29 < peleion> docker exec -it /bin/bash 08:30 < peleion> or any other command available in the container 08:33 < miketwenty1> i guess.. im worried that while getting a backup of .lnd.. 08:33 < miketwenty1> if lnd is running 08:33 < miketwenty1> and a transaction happens 08:34 < miketwenty1> routes through my node.. i might be fucking myself if I have old channel state 08:34 < miketwenty1> correct? 08:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 08:35 < miketwenty1> i suppose i could just kill the port.. on my router settings.. to be sure nothing interacts with my node 08:36 < peleion> you can also: "docker cp : . " to copy a directory to your host on a stopped container 08:37 < peleion> copy a directory or file 08:39 -!- sfhi [~sfhi@178.255.154.107] has joined #lnd 08:45 < molz> mikethetike, i think you can set `nolisten=1` 08:56 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 08:56 < miketwenty1> molz: does --neutrino.connect=faucet.lightning.community work for mainnet? 09:00 < molz> no it doesn't 09:00 < miketwenty1> ty 09:04 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 09:12 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 09:13 < bitconner> miketwenty1, neutrino isn't enabled on mainnet bc the protocol is still undergoing changes 09:13 < miketwenty1> thanks for the info 09:14 < bitconner> np; 09:20 < miketwenty1> if i look at my casa logs.. im seeing 09:20 < miketwenty1> panic: runtime error: index out of range 09:20 < miketwenty1> and panic: runtime error: slice bounds out of range 09:20 < miketwenty1> im wondering if this can be fixed by recovering to another node.. 09:20 < miketwenty1> or if .lnd dir is already "f'd" 09:23 < Veggen> depends. if its a localized errors, you could maybe ignore it and then just lose one channel. 09:23 < Veggen> ...or force-close it. 09:24 < bitconner> miketwenty1, is the error happening on startup? sounds like boltdb corruption 09:25 < molz> :D 09:25 < miketwenty1> it's happening when i unlock 09:25 < miketwenty1> lncli unlock 09:25 < bitconner> yep, sounds indicative 09:25 < Veggen> how far do you get? 09:25 < miketwenty1> it will crash the docker container in about 5 seconds after unlocking 09:26 < Veggen> you'll need to find more complete logs to find out. 09:26 < bitconner> did your node ever lose power? 09:26 < molz> Veggen, if you do a search for "bbolt corruption" on the slack you'll see plenty of it 09:27 < miketwenty1> https://pastebin.com/Yb4KGwis 09:27 < miketwenty1> bitconner, probably 09:27 < Veggen> molz: sure. 09:27 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 09:28 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 09:28 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 09:28 < molz> and SIGBUS too 09:29 < bitconner> interesting, most corruption issues cause the panic to happen when you try to open boltdb, this seems to happen after opening and on trying to access the channels 09:29 < Veggen> miketwenty: anything before that, in logs? 09:34 < miketwenty1> logs are pretty big.. but it seems to be repeat stuff mainly 09:35 < Veggen> miketwenty: if this for example happens when reading a specific channel, you might be able to just ignore the error. 09:37 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 09:37 < miketwenty1> Veggen, it causes a panic and exits the docker container 09:37 < miketwenty1> im not sure how to ignore this 09:39 < Veggen> might need to copy things outside and run custom compiled lnd that you control more. 09:39 < Veggen> but, need to walk the dog. 09:40 < miketwenty1> sounds like fun.. i'll try doing this.. if my backup idea fails 09:40 < miketwenty1> Veggen, just need to learn .. golang.. and then learn lnd.. 09:40 < miketwenty1> lol 09:40 < molz> nah, just learn how to manage your lnd node 09:41 < miketwenty1> sounds good.. but recovering funds.. from a crashed node.. 09:41 < miketwenty1> thought that if i bought a rasperrypi from a company i wouldn't need to be smart 09:42 < molz> currently we can recovery the funds in lnd wallet, not channel funds but this is being worked on 09:42 < miketwenty1> i can recover easily from lnd wallet... 09:42 < miketwenty1> i have the seed words 09:42 < miketwenty1> i need the channel stuff 09:43 < molz> how many channels do you have? 09:43 < molz> not a lot of money invested in channels, right? 09:44 < miketwenty1> a lot of money .. a lot of channels 09:44 < miketwenty1> enough for me to be here 09:44 < miketwenty1> :) 09:47 < molz> well maybe think of a different way to be on LN then :P 09:47 < miketwenty1> genius 09:47 < miketwenty1> i'll take your advice 09:47 < molz> i reduced my play money on LN when i realized the network got taken over by rash-hairy-pies 09:47 < molz> i prefer to play on testnet now 09:50 < molz> we're not optimized to be abused by those pies yet, it's good they're there as test devices though :P 09:52 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 10:02 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection] 10:08 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 10:12 < miketwenty1> what's the proper way to add nobootstrap=1 and nolisten=1 to the lnd daemon command 10:12 < miketwenty1> or is it only possible in the lnd.conf? 10:13 < lndbot> Locate the lnd.conf, and add it there 10:13 < miketwenty1> was trying --nobootstrap=1 and --nolisten=1 10:13 < lndbot> Tbh idt that will help but you can try 10:13 < lndbot> Panic is occurring before any networking occurs 10:14 -!- Highway61 [~Thunderbi@96.44.143.82] has joined #lnd 10:18 -!- Highway62 [~Thunderbi@ip184-186-21-239.no.no.cox.net] has joined #lnd 10:18 -!- Highway61 [~Thunderbi@96.44.143.82] has quit [Ping timeout: 246 seconds] 10:22 -!- Highway62 [~Thunderbi@ip184-186-21-239.no.no.cox.net] has quit [Ping timeout: 245 seconds] 10:33 -!- sfhi [~sfhi@178.255.154.107] has quit [Quit: Leaving] 10:43 -!- tristian [~tristian@unaffiliated/tristian] has quit [Remote host closed the connection] 10:48 -!- tristian [~tristian@unaffiliated/tristian] has joined #lnd 11:18 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 11:24 < Veggen> hrmf. 11:25 < Veggen> testnet node crashes. 11:26 < Veggen> 2019-02-20 20:26:18.307 [ERR] SRVR: unable to start server: -8: Block height out of range 11:27 < bitconner> Veggen, backend fully synced? 11:27 < Veggen> 1479750 ? 11:27 < Veggen> ...seems like. 11:28 < Veggen> been a while since I ran this lnd 11:28 < Veggen> no, wait. 11:28 < Veggen> it's not. 11:29 < bitconner> ;) 11:30 < Veggen> ...it hadn't started syncing yet :P (after starting bitcoind again) 11:31 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 11:31 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 11:33 < Veggen> but, grmf. 11:33 < molz> veggen my testnet nodes haven't crashed for a while now :D 11:33 < Veggen> what the hell is my testnet seed.. 11:33 < Veggen> I know I put it in digital form somewhere, for laziness ;P 11:33 < molz> delete everything and start new! 11:36 < Veggen> now I get to try sweepall too! 11:40 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 11:44 < Veggen> fine, new lnd rescanning...then funding, create channel, then lose, then restore :) 11:50 -!- trotski2000 [uid206086@gateway/web/irccloud.com/x-kjqfdeqqqbimsgcg] has quit [Quit: Connection closed for inactivity] 11:56 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 11:58 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 11:58 < Veggen> ok...molz, your testnet node data. I wanna lose some channels! 12:00 < Veggen> molz: Sure it doesn't work yet, btw? :) 12:01 -!- pinkTiger [pinkTiger@gateway/vpn/protonvpn/pinktiger] has joined #lnd 12:01 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 12:01 -!- miketwenty1 [63998f99@gateway/web/freenode/ip.99.153.143.153] has quit [Ping timeout: 256 seconds] 12:01 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 12:02 < pinkTiger> can I run lnd if my bitcoind is pruned 12:02 < Veggen> pinkTiger: not officially. 12:03 < Veggen> not recommended. 12:03 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:11 < molz> veggen sweepall is in master 12:14 < Veggen> molz: sure, just hadn't tested it yet. 12:14 < Veggen> do you have a publically connectable testnet node? 12:30 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 12:34 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 12:37 < molz> Veggen, pm 12:47 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 12:47 -!- miketwenty1 [041cb3ea@gateway/web/freenode/ip.4.28.179.234] has joined #lnd 12:49 -!- rudeadyet [~qxt@unaffiliated/qxt] has joined #lnd 12:52 < rudeadyet> thought I would experiment calming funds from a bad actor node. I have. How do I get a rawtransaction of a channel state. I want to replay it against my test node. 12:53 < rudeadyet> beside making a copy of .lnd and reusing it is there another way? 12:55 < Veggen> not really another way. 12:56 < Veggen> unless you want to create a malware version of lnd :) 12:56 < Veggen> well, restorechanbackup crashed my node :) 12:56 < Veggen> gonna wait till rescan is finished and test again. 12:56 < rudeadyet> Veggen, ohhh that would not be nice. Image if somebody made a malware worm that did a cp -r .lnd and then put it back after a tx 12:56 < rudeadyet> Imagine... blah 13:09 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 13:14 < Veggen> hrmf. What did I do wrong? seed restore gave me 0 BTC (test)... 13:19 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 13:20 < molz> lnd does NOT use BIP39, has been using AEZEED for almost a year but why is it there're still people out there thinking lnd uses bip39? 13:24 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Ping timeout: 250 seconds] 13:27 < Veggen> molz: was an LND seed I tried to restore. 13:27 < Veggen> ....the one I just created ;P 13:28 < molz> how did you do it? 13:28 < Veggen> lncli create, type password (twice), then enter seed (verified it), funds gone. 13:28 < Veggen> increase lookahead? 13:29 < molz> yea 13:30 < rudeadyet> Veggan were the funds in channels or your wallet? 13:31 < Veggen> wallet. 13:31 < Veggen> ...and channels :) 13:32 < Veggen> actually was trying to test channel restore functionality. 13:32 < rudeadyet> I had some fuckshit like that. dumping the tx history and a rescan fixed it. 13:32 < Veggen> I deleted all, so there's no tx history there :) 13:39 -!- miketwenty1 [041cb3ea@gateway/web/freenode/ip.4.28.179.234] has quit [Ping timeout: 256 seconds] 13:42 < molz> #reckless! 13:48 < Veggen> okok. fine. wallet funds are back, but restorechanbackup crashes lnd. 13:50 -!- tristian [~tristian@unaffiliated/tristian] has quit [Ping timeout: 272 seconds] 13:51 < Veggen> 2019-02-20 22:51:04.661 [INF] CHBU: Restoring ChannelPoint(c18d38c205872d06b90d9ac9c926687c3914014abbfa59aabb11cee0f79985a1:0) to disk: 13:51 < Veggen> panic: runtime error: invalid memory address or nil pointer dereference 13:51 < Veggen> [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x95bb29] 13:52 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 13:55 < molz> hm we have 'restorechanbackup'? 13:55 < Veggen> sure. 13:56 < Veggen> ...but it didn't work :) 13:57 < molz> oh i see 13:57 < Veggen> crashed lnd. 13:57 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Ping timeout: 268 seconds] 13:58 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 13:58 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 13:59 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 14:03 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Ping timeout: 268 seconds] 14:05 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has joined #lnd 14:20 -!- tristian [~tristian@unaffiliated/tristian] has joined #lnd 14:28 -!- thomasan_ [~thomasand@2605:a601:b021:f00:904:f745:ec20:7f89] has quit [Remote host closed the connection] 14:35 <@roasbeef> the existing branch isn't final 14:36 <@roasbeef> my local one has fixed more stuff and has passing tests 14:38 <@roasbeef> see the check boxes in the PR 14:38 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds] 14:38 <@roasbeef> the format has also changed slgihtly to be more future looking and flexible 14:39 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #lnd 14:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 14:50 < Veggen> roasbeef: ok :) So my backed up testnet channels are lost? ;) (or can they be restored next week?) 14:52 <@roasbeef> you coul dmaybe convert the old format to the new 14:53 <@roasbeef> idea is that once it's set it won't ever change, but before then we have the opportunity to ensure we have all the items we need to carry things out reliably 14:55 < Veggen> sure, I was just feeling adventurous tonight. 14:55 < Veggen> :) 14:56 <@roasbeef> hehe np, will give y'all a shout once it's done 14:56 <@roasbeef> blocked off some time today to try to finish it up 15:18 <@roasbeef> RusAlex: no, if she doens't have advertised channels, then she isn't a known entity on the graph 15:24 -!- siom [~siom@83.97.23.43] has quit [Remote host closed the connection] 15:52 -!- thomasan_ [~thomasand@136.52.18.22] has joined #lnd 16:09 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 16:14 -!- rk3y [~rk3y@unaffiliated/rk3y] has quit [Ping timeout: 258 seconds] 16:17 -!- rk3y [~rk3y@unaffiliated/rk3y] has joined #lnd 16:17 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 16:26 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 244 seconds] 16:28 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 16:28 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 16:30 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 264 seconds] 16:33 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 264 seconds] 16:35 -!- DeanGuss [~deanguss@gateway/tor-sasl/deanguss] has joined #lnd 16:37 -!- rk3y [~rk3y@unaffiliated/rk3y] has quit [Ping timeout: 252 seconds] 16:38 -!- rk3y [~rk3y@unaffiliated/rk3y] has joined #lnd 16:41 -!- jchia_ [~jchia@58.32.32.5] has quit [Ping timeout: 255 seconds] 16:44 -!- jchia_ [~jchia@58.32.32.5] has joined #lnd 16:45 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:08 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 17:08 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:09 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Client Quit] 17:09 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:19 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 17:20 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:30 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 17:31 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:41 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 17:41 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:43 -!- thomasan_ [~thomasand@136.52.18.22] has quit [Remote host closed the connection] 17:47 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has joined #lnd 17:49 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has quit [Remote host closed the connection] 17:51 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 17:51 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has joined #lnd 17:52 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 17:55 < rudeadyet> I have two test nodes. A is trying to rip off B and B will then claim everything in the channel. A made a backup of .lnd and then sent 500000 to B. After sending the funds the backup was replaced. How does B claim all all funds? 17:56 < rudeadyet> After replacing the old .lnd the funds seemed to reflect the new balances correctly? 17:57 < rudeadyet> Why no punishment? 17:57 < lndbot> You’re trying to test this out? 17:57 < rudeadyet> yes 17:57 < rudeadyet> I am on test net 17:57 < rudeadyet> ofc 17:59 < bitconner> rudeadyet, did you force close w/ the old node? 17:59 < lndbot> Make sure you attempt to force close with an old state 17:59 < rudeadyet> ahh that I did not do. Thank you 17:59 < bitconner> p 17:59 < bitconner> np 18:01 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 18:03 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 18:18 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 18:18 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 18:29 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 18:43 -!- foureighttwonine [~foureight@103.16.27.75] has joined #lnd 18:48 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has quit [Remote host closed the connection] 18:50 -!- DeanGuss [~deanguss@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 18:58 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 255 seconds] 19:04 < rudeadyet> continuing from the above. A has now force closed the channel with the outdated .lnd. My question is how does B know he has been ripped off? What does B need to do to claim all the funds? 19:05 < rudeadyet> There is a waiting period of 24 hours. Does something need to be done during this period? 19:06 < molz> B just has to be online 19:06 < rudeadyet> so it is automated? 19:06 < bitconner> did the transaction get mined? 19:07 < rudeadyet> not sure. Ill look 19:07 < bitconner> yes, it is automated so long as B is online 19:08 < rudeadyet> So it makes sense to have maybe 10 days then. Just to be sure. 19:08 < rudeadyet> This is actually kinda neat 19:09 < bitconner> it should happen pretty much immediately after the transaction is mined 19:09 < bitconner> the longer the waiting period just gives node B more time to be offline/disconnected/down for maintenance and get the justice txn confirmed 19:11 < rudeadyet> btcctl getrawtransaction a406f4cf948025abdd95a7746acfdc06e11d79de1c12e2b0f2c18b579593702f 1 19:11 < rudeadyet> there it went. Sorry 19:12 < bitconner> justice has been served 19:13 < molz> rudeadyet, have you read this thread: https://twitter.com/alexbosworth/status/978069194385252352 19:13 < rudeadyet> yes it worked perfectly 19:14 < rudeadyet> really neat shit! 19:15 < rudeadyet> molz, heh "justice" 19:15 < bitconner> i think they made shirts of those logz too lol 19:16 < molz> oh they did? :D 19:22 -!- foureighttwonine [~foureight@103.16.27.75] has quit [Read error: Connection reset by peer] 19:28 < rudeadyet> 2019-02-21 04:01:02.045 [WRN] BRAR: A channel has been breached with txid: a406f4cf948025abdd95a7746acfdc06e11d79de1c12e2b0f2c18b579593702f. Waiting for confirmation, then justice will be served! 19:28 < rudeadyet> there it is =D 19:40 < molz> rudeadyet, is this on testnet or simnet? 19:44 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 19:48 < rudeadyet> testnet 19:49 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 19:50 -!- nubnub [68bf10fc@gateway/web/freenode/ip.104.191.16.252] has joined #lnd 19:50 < nubnub> gunna ask some questions =) 19:51 < nubnub> so if i have 1 channel open for 100 satoshies and i send 1 sat through that channel will my pay limit decrease to 99 sat? 19:51 < nubnub> How does my request limit value increase above zero 19:58 < molz> not sure i understand your q 19:59 < nubnub> i have zap LN set up using pierres node launcher and im just trying to get a better understanding of how the pay and request limits change 20:00 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has joined #lnd 20:00 < nubnub> so i just opened a channel with tippin.me and it will start with only a pay limit based on what i funded the channel with. 20:00 < nubnub> I think over time that pay limit will decrease and the request limit will increase from zero but i dont really understand how 20:04 < molz> nubnub, think of something like a debit card, you put x amt of money in there, that's all you have to spend 20:05 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has quit [Ping timeout: 268 seconds] 20:05 < molz> for ln channels your spending will also include fees onchain 20:05 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Ping timeout: 268 seconds] 20:06 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has joined #lnd 20:06 < nubnub> i get that. I just really dont understand how the pay and request limits change in Zap wallet. 20:07 < nubnub> ok, i just did a test. I opened a channel with tippin.me and then i sent 100sat to my tippin.me address. The paylimit went down 100sat and the request limit increased from 0 to 100 20:10 -!- miketwenty1 [63998f99@gateway/web/freenode/ip.99.153.143.153] has joined #lnd 20:17 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has quit [Remote host closed the connection] 20:17 < molz> nubnub, zap has their own slack you can ask them for help there, but yes i guess what it means is your receive possibility is 100 but there's also a 1% rule, you can't receive back unless that amt is over 1 percent of the channel capacity 20:19 -!- nubnub [68bf10fc@gateway/web/freenode/ip.104.191.16.252] has quit [Quit: Page closed] 20:19 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has joined #lnd 20:21 < miketwenty1> molz, newbie question... why isn't the lnd or lncli sourced when i follow the README.md 20:21 < miketwenty1> what is the best way to run lnd? and have it appear as a command i can use in my PATH 20:32 -!- aero [ade33e03@gateway/web/freenode/ip.173.227.62.3] has joined #lnd 20:35 < molz> mikethetike, what do you mean? 20:35 < miketwenty1> hmm.. it was a weird thing with the GOPATH.. maybe i can amend the instructions 20:35 < miketwenty1> molz, basically if you follow the instructions word for word.. you source the wrong bin 20:35 < miketwenty1> i think 20:35 < miketwenty1> or maybe im jus tard'd 20:35 < molz> which instructions? 20:36 < miketwenty1> https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md 20:37 < molz> i've used that guide the last two years, but for go installation i don't use the go guide there 20:38 < miketwenty1> it's good.. i just missed this for some reason 20:38 < miketwenty1> export PATH=$PATH:$GOPATH/bin 20:38 < miketwenty1> where do you go? 20:38 < molz> i use this site to figure out Go https://golang.org/doc/install#install 20:39 < molz> and you can google to find sources about Go 20:39 < miketwenty1> i think lnd is the official source of how to install go... the only use case for golang is lnd 20:43 < molz> miketwenty1, here's how i install and update Go: https://paste.ee/p/EN2Q4#2NXZGAnOwp2v5Tm7SzsmRcUKkIProzKT 20:50 < miketwenty1> molz, so i have bad news 20:50 < miketwenty1> synced bitcoind today on a brand new server 20:50 < miketwenty1> restored .lnd from the Raspberry Pi 20:50 < miketwenty1> same errors as before 20:51 < molz> hm.. sorry to hear :/ 20:51 < miketwenty1> https://pastebin.com/3SLn25dC 20:51 < miketwenty1> i think it was you or someone else.. saying it might be just 1 bad channel 20:52 < miketwenty1> and i might be able to bypass the panic 20:52 < miketwenty1> would you have any ideas on this? 20:58 < molz> miketwenty1, i'm not sure, you have to ask the devs, ping roasbeef, conner 20:58 < molz> or post an issue on github 21:01 < miketwenty1> just added to a closed issue on github 21:02 < miketwenty1> i think.. i will probably pay the person who help me recover my btc 21:02 < miketwenty1> maybe like 10 years from now.. 21:02 < miketwenty1> it will be $1,000,000 21:02 < miketwenty1> worth of btc 21:02 < miketwenty1> nice way to do some forced savings 21:05 < molz> miketwenty1, were you trying to update and this happened? 21:06 < miketwenty1> molz im not sure what to say.. 21:06 < miketwenty1> this is my experience using a casa node 21:06 < miketwenty1> and not understanding that my 24 words couldn't backup all my bitcoin in the channels 21:07 < miketwenty1> and also thinking that the channels would resolve themselves automatically .. which i found out wasn't true and these channels are indefinitely long 21:12 -!- speed147 [~speed147@107.13.228.129] has joined #lnd 21:33 < molz> miketwenty1, didn't casa explain to you the seed only restores onchain coins in your wallet? 21:33 < molz> miketwenty1, and this seems to be hardware failure? you should talk to casa 21:40 -!- speed147 [~speed147@107.13.228.129] has quit [Remote host closed the connection] 21:43 -!- thomasan_ [~thomasand@2605:a601:b021:f00:8594:7fbe:59b9:22df] has quit [Remote host closed the connection] 21:48 -!- miketwenty1 [63998f99@gateway/web/freenode/ip.99.153.143.153] has quit [Ping timeout: 256 seconds] 21:51 < molz> interesting info: https://godoc.org/github.com/coreos/bbolt 21:54 -!- melvin_ [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 21:54 < Veggen> // Once we've found a valid channel bucket, we'll extract it 21:54 < Veggen> // from the node's chain bucket. 21:54 < Veggen> chanBucket := chainBucket.Bucket(chanPoint) 21:55 < Veggen> ....this is where it goes wrong, seen from lnd. 21:55 <@roasbeef> well no, it's just db corruption 21:55 <@roasbeef> it the file is messed up, then you can't read things from it 21:55 < Veggen> roasbeef: hm. 21:55 < Veggen> are we sure it is not skippable? 21:56 <@roasbeef> it's not an lnd thing 21:56 <@roasbeef> it might be but you 21:56 <@roasbeef> 'd need to go a level deeper and try to salvage the bolt metadata file 21:57 <@roasbeef> in the b+tree something is messed up, so it can't continue to traverse it 21:57 < Veggen> hmm. ok. 21:57 <@roasbeef> but yeh we only see this on pis 21:57 < molz> roasbeef, it seems it's a go thing that raspis aren't compatible with? 21:57 <@roasbeef> the db we use is used widely in many other large projects but on proper hardware, and i haven't hit this on any of my nodes (that aren't pi's) 21:58 <@roasbeef> nah it's not a go thing, it's a pi+storage thing 22:00 < molz> roasbeef, there's a "panic: runtime error: index out of range" with OSX here: https://github.com/golang/go/issues/24394 , which might not be the same but it'll be fixed in go 1.12 22:01 < Veggen> molz, that one is not related to bolt in anyway? 22:01 <@roasbeef> that's diff 22:02 < molz> yea it's different but it also causes "panic: runtime error: index out of range" why's that? 22:02 <@roasbeef> it's the error if you try to access something beyond its bound 22:02 <@roasbeef> like trying to get the 2nd element of a 1 element array 22:04 <@roasbeef> that one above looks like it may be able to be sprung up in read only mode 22:06 < peleion> I've wondered why the lnd explosion is based on the pi - a $35 box with proprietary bootloader when, for just a little more, can be done in a brix or similar mini 22:06 < peleion> Seems like false economy to me to cheap out on the hardware 22:07 < molz> well not just lnd, the first pi explosion i saw was with dash masternodes 22:07 < molz> and some people lost money on those too 22:07 < molz> and USB sticks 22:08 < peleion> Matter of time before the proprietary bootloader becomes a vector for attack 22:09 < peleion> And problems like miketwenty1 with corruption 22:21 < molz> a casa user asked Pierre Rochard for tech support help on twitter, his reply: "Ah well I’m not going to do casa support for free haha" LOL 22:22 < molz> https://twitter.com/pierre_rochard/status/1098420139811328001 22:25 < peleion> Awesome. Do people really use the twit for tech support? 22:26 < peleion> twit(ter), not rochard 22:27 < molz> some do 22:27 < peleion> Fix your problems with 255 characters. Yikes. 22:52 -!- nrobot [7824fc40@gateway/web/freenode/ip.120.36.252.64] has joined #lnd 23:21 < molz> heh bbolt crash on WSL was a WSL bug, not boltdb bug, got fixed in windows in the fall creators update. Maybe raspi enthusiast should contact pi manufacturers but i guess they wouldn't care 23:23 < peleion> Yeah, raspi target market really isn't fault tolerant secure crytocurrency projects :)