--- Day changed Mon Jan 29 2018 00:17 -!- AndBobsYourUncle [~AndBobsYo@cpe-23-240-21-154.socal.res.rr.com] has quit [Quit: Textual IRC Client: www.textualapp.com] 00:42 -!- Soopaman [~soopaman@198.16.243.66] has quit [Quit: Leaving.] 01:02 -!- creslin_ [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 01:03 -!- jungly [~quassel@79.8.200.97] has joined #lnd 01:16 -!- creslin [~textual@178.214.193.58] has joined #lnd 01:34 -!- creslin_ [~textual@deposing-waterfront.volia.net] has joined #lnd 01:34 -!- creslin [~textual@178.214.193.58] has quit [Ping timeout: 248 seconds] 01:35 < mlz> roasbeef, the latest Go version is 1.9.3 01:45 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 01:47 -!- sovjet [~sovjet@193.189.166.102] has joined #lnd 01:52 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:52 -!- nirved [~nirved@2a02:8071:b58a:3c00:ad92:eca7:97d5:1b42] has joined #lnd 02:02 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 264 seconds] 02:18 -!- kunla [~kunla@bl13-61-148.dsl.telepac.pt] has joined #lnd 02:51 -!- mkl [3ed82bae@gateway/web/freenode/ip.62.216.43.174] has joined #lnd 02:53 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-jivggjsjuynusrfu] has joined #lnd 02:55 -!- creslin [~textual@46.211.146.111] has joined #lnd 02:56 -!- creslin_ [~textual@deposing-waterfront.volia.net] has quit [Read error: Connection reset by peer] 02:59 -!- creslin [~textual@46.211.146.111] has quit [Ping timeout: 240 seconds] 03:00 -!- creslin [~textual@deposing-waterfront.volia.net] has joined #lnd 03:24 -!- creslin [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:29 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 04:45 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-xavieucymdtpcvrr] has quit [Quit: Connection closed for inactivity] 04:47 -!- creslin [~textual@deposing-waterfront.volia.net] has joined #lnd 04:56 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #lnd 05:06 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has joined #lnd 05:06 < kbasali> Hi 05:07 < kbasali> Have question, What is the server requirements for LN 05:08 < kbasali> 200 GB hdd, 16 Ram, 8 core CPU is it enough or can I go for cheaper server? 05:09 -!- kbasali_ [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has joined #lnd 05:10 -!- kbasali_ [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has quit [Client Quit] 05:15 < kbasali> ? 05:25 < zyp> it certainly doesn't need that much 05:32 < kbasali> 100 GB 8 GB ram 4 Core will be enough? 05:34 < kbasali> or could it be less? 05:34 < zyp> why don't you just try and see? 05:34 < zyp> I don't think anybody here is gonna give you any hard numbers 05:35 < kbasali> Becouse maybe someone already tired and knew it 05:36 < zyp> lnd does not require a significant amount of storage on its own 05:36 < zyp> if you're running it alongside a bitcoin node, however, the bitcoin node needs room to store the blockchain 05:45 < kbasali> Thank you so much. 05:50 < kbasali> I have another question about backup? 05:50 < kbasali> what files do I need to backup? 06:02 -!- Mark___ [5bd4cf04@gateway/web/freenode/ip.91.212.207.4] has joined #lnd 06:07 < Mark___> A question, when I'm following these instructions https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md and do 'glide install' I get four errors 06:07 < Mark___> ERROR] Failed to set version on github.com/lightninglabs/gozmq to 0d266ba6d55ea65c18c7a02d8992c89355149e80: Unable to update checked out version: exit status 128 06:07 < Mark___> ERROR] Failed to set version on github.com/lightninglabs/neutrino to 6c8f30a130bb170348ceb754ce4204156efe2741: Unable to update checked out version: exit status 128 06:07 < Mark___> ERROR] Failed to set version on github.com/roasbeef/btcwallet to 4f4765c3e3baf4c7b40c311340a076ec83c5ef3a: Unable to update checked out version: exit status 128 06:07 < Mark___> ERROR] Failed to set references: Unable to update checked out version: exit status 128 06:08 < Mark___> Anything serious? 06:09 < Mark___> should also mention, this was after doing a git update. Don't remember getting it the first time 06:12 < Mark___> then 'go install . ./cmd/...' runs fine without any output and a new lnd binary was produced 06:18 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has quit [Ping timeout: 260 seconds] 06:32 -!- sovjet [~sovjet@193.189.166.102] has quit [Ping timeout: 256 seconds] 06:34 < Mark___> Nobody else getting those 'exit status 128' ? 06:35 -!- dbolser [~dbolser@unaffiliated/faceface] has joined #lnd 06:35 < dbolser> hihi 06:37 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #lnd 06:37 -!- creslin [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 06:46 -!- mkl [3ed82bae@gateway/web/freenode/ip.62.216.43.174] has quit [Quit: Page closed] 07:02 -!- creslin [~textual@93.73.60.116] has joined #lnd 07:07 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-jivggjsjuynusrfu] has quit [Quit: Connection closed for inactivity] 07:08 -!- ozguruzden [b0eafcd8@gateway/web/freenode/ip.176.234.252.216] has joined #lnd 07:08 < ozguruzden> Hello 07:09 < ozguruzden> I need a small help about my node 07:09 < ozguruzden> I could not find a solution on google :) 07:09 -!- creslin [~textual@93.73.60.116] has quit [Read error: Connection reset by peer] 07:09 -!- creslin_ [~textual@deposing-waterfront.volia.net] has joined #lnd 07:09 < ozguruzden> How can I change my alias of node? 07:10 < ozguruzden> I will really appreciate if someone help me. 07:12 < Mark___> lnd --alias=xxx should do it 07:14 < ozguruzden> lnd: command not found :( 07:16 < Mark___> you should find it in $GOPATH/bin You can read more here about installation https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md 07:17 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Read error: Connection reset by peer] 07:18 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 07:19 -!- ozguruzden [b0eafcd8@gateway/web/freenode/ip.176.234.252.216] has quit [Quit: Page closed] 07:28 < devachandra> ozguruzden: seems it is yet to be implemented. there is gRPC api call SetAlias for this, should be implemented in lncli 07:29 < devachandra> just had interest in same question right now ) 07:33 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lnd 07:33 < mlz> it has been implemented 07:34 < mlz> lnd --alias="xxx" 07:35 < mlz> Mark___, i've never had those errors.. maybe check to make sure your GOPATH is correct? 07:44 < devachandra> mlz: yeah, i see, just had to update. thanks 07:46 -!- spinza [~spin@196.212.164.26] has joined #lnd 08:01 -!- JackH [~laptop@212.78.169.180] has quit [Ping timeout: 252 seconds] 08:10 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 255 seconds] 08:17 -!- peter_ [055f502f@gateway/web/freenode/ip.5.95.80.47] has joined #lnd 08:24 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 246 seconds] 08:28 -!- Soopaman [~soopaman@198.16.243.66] has joined #lnd 08:29 -!- iv4n [~iv4n@1.46.64.197] has quit [Ping timeout: 265 seconds] 08:37 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 08:39 -!- peter_ [055f502f@gateway/web/freenode/ip.5.95.80.47] has quit [Quit: Page closed] 08:39 -!- kunla [~kunla@bl13-61-148.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 08:40 -!- Soopaman [~soopaman@198.16.243.66] has quit [Quit: Leaving.] 08:51 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 08:55 -!- capa66 [capa66@gateway/vpn/privateinternetaccess/capa66] has joined #lnd 08:56 -!- Soopaman [~soopaman@198.16.243.66] has joined #lnd 08:56 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has joined #lnd 08:56 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has quit [Client Quit] 09:01 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has joined #lnd 09:04 -!- zaptrem [~Mutter@2600:380:bc6e:82bf:c444:e3c9:f099:cfb5] has joined #lnd 09:05 < zaptrem> Good morning. Is it possible to create an open lightning invoice that can receive multiple payments? (E.g., a donation box) 09:08 -!- deepcore [~deepcore@62-210-36-142.rev.poneytelecom.eu] has joined #lnd 09:10 < deepcore> is there any guides for running lnd with neutrino on the mainnet? 09:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-meihvxlillhpkdwn] has joined #lnd 09:11 < zaptrem> Mainnet is dangerous, neutrino on mainnet is downright suicidal 09:11 -!- zaptrem_ [6b4d6a3c@gateway/web/freenode/ip.107.77.106.60] has joined #lnd 09:11 -!- zaptrem [~Mutter@2600:380:bc6e:82bf:c444:e3c9:f099:cfb5] has quit [Quit: Mutter: www.mutterirc.com] 09:11 < zaptrem_> Test 09:11 < deepcore> heh, well btcd takes forever to sync 09:12 < zaptrem_> Try bitcoind 09:12 < deepcore> not going to use it for a lot of money anyway 09:12 < deepcore> does it work with lnd? 09:12 < zaptrem_> Yeah 09:12 < deepcore> cool 09:12 < zaptrem_> I'm throwing together a guide on Medium for the crazies, it should be ready later today. 09:12 < deepcore> nice 09:15 -!- spinza [~spin@196.212.164.26] has joined #lnd 09:19 -!- zaptrem [~Mutter@2600:380:bc6e:82bf:c444:e3c9:f099:cfb5] has joined #lnd 09:21 -!- zaptrem [~Mutter@2600:380:bc6e:82bf:c444:e3c9:f099:cfb5] has quit [Client Quit] 09:22 -!- colatkinson [~colatkins@gear-190.dynamic2.rpi.edu] has joined #lnd 09:34 < blademccool> was just reading an article about a japanese startup with their own LN implementaiton that isnt lnd, clightning or eclair. so there is at least 4 implementations now 09:35 < blademccool> Nayuta, and they call their LN implementation "Thunderbird" 09:37 -!- aakselrod [aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has joined #lnd 09:56 < zaptrem_> When writing LN node addresses, can the system resolve domain names after the @ sign? 09:57 < zaptrem_> e.g., 3892jrui1n290jg8hj982h@test.com:9735 09:59 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has joined #lnd 10:00 < blademccool> i established connections from my lnd to other nodes using domain names like that in the past yeah 10:08 -!- zaptrem_ [6b4d6a3c@gateway/web/freenode/ip.107.77.106.60] has quit [Ping timeout: 260 seconds] 10:16 -!- grubles [~grubles@unaffiliated/grubles] has joined #lnd 10:24 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 240 seconds] 10:25 -!- colatkinson [~colatkins@gear-190.dynamic2.rpi.edu] has quit [Quit: colatkinson] 10:30 < Soopaman> If I want to create a lightning node on a server with the proper amount of storage, is there a way to create smaller lnd instances (on rpi's) that can piggy back off of that storage? 10:32 -!- iv4n [~iv4n@1.47.65.243] has joined #lnd 10:42 < blademccool> the lnd doesnt seem to store that much data. and you can point multiple lnds at the same btcd or bitcoin core backend 10:45 < cryptodechange> Isn't Neutrino the only node that allows for lightweight general connections? 10:45 < cryptodechange> So far that is? Unless I'm missing something 10:45 < spudowiar> cryptodechange: Neutrino is a client for nodes with compact block filters 10:46 < blademccool> i dont really know anything about neutrino, but i do know that my lnd is in a vm and its talking to the bitcoin core that runs on the host that it sees as a different machine. 10:46 < cryptodechange> So unless I'm mistaken, thats one massive caveat before lnd is mainnet ready? Unless lnd is focused on full nodes for the time being 10:46 < cryptodechange> I just remember seeing something regarding neutrino, that it shouldn't be used on mainnet 10:46 < spudowiar> cryptodechange: People can host a btcd instance with compact block filters that users can connect to 10:47 < cryptodechange> using RPC right? 10:48 < cryptodechange> I suppose most lightweight bitcoin clients have a singular/primary server point 10:48 < cryptodechange> I wonder if an Electrum's approach how clients connect to nodes/servers would be suitable 10:48 < cryptodechange> to how* 10:49 < cryptodechange> or even an lnd dedicated server, where clients can connect to automatically and share some of the hop fees with in exchange 10:50 < cryptodechange> my typing is terrible this evening... 10:54 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 10:55 -!- colatkinson [~colatkins@2620:0:2820:503:5ee0:c5ff:fe8c:502d] has joined #lnd 10:56 < ChunkyPuffs> Is there a guide on how to quickly set up a lightning node and open a payment channel for autopilot to use under ubuntu or any other linux distro? 10:57 < ChunkyPuffs> I just wanna set it up, get it online, then worry about configuration later. 10:58 < ChunkyPuffs> Mainnet, of course, sorry. 10:58 < blademccool> word in the street is zaptrem is gonna post a guide for that later today to Medium 10:59 < ChunkyPuffs> First thing that comes up on google is a guide for Windows. And my first response is "ew" 10:59 < blademccool> that windows guide .. is it even for lnd? 10:59 < ChunkyPuffs> Is lightning.exe the same as lnd? 10:59 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 10:59 < blademccool> i am guessing that is windows version of c-lightning .. our exe would be lnd.exe 10:59 < ChunkyPuffs> https://medium.com/@jadmubaslat/bitcoin-lightning-network-node-easy-setup-tutorial-for-windows-desktop-users-a-how-to-guide-9937b5a8a669 11:00 < ChunkyPuffs> do I have to run the daemon as sudo or something? 11:00 < ChunkyPuffs> it tells me there's no rpc.cert, or lnd.conf, do I have to wget these from somewhere to get started quickly? 11:01 -!- Soopaman [~soopaman@198.16.243.66] has quit [Quit: Leaving.] 11:03 < deepcore> what should I set --bitcoind.zmqpath to? 11:03 -!- Soopaman [~soopaman@198.16.243.66] has joined #lnd 11:03 -!- colatkinson [~colatkins@2620:0:2820:503:5ee0:c5ff:fe8c:502d] has quit [Quit: colatkinson] 11:04 < deepcore> nevermind, i found it in the doc 11:04 < blademccool> deepcore: the ip and port that your bitcoin core is publishing the data on (eg mine is bitcoind.zmqpath=tcp://192.168.1.96:18502) 11:04 < deepcore> alright, thanks 11:04 < Veggen> would an lnd node on a dedicated rpi 3, towards a full node in the cloud (not so secure, I guess) be considered secure enough setup? 11:04 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 11:05 < Veggen> I guess it's the LND wallet that matters, security wise? 11:05 < blademccool> I feel like if the only port open is for lnd and the rpi itself is locked in a safe with a deadman self destruct switch upon ethernet cable being cut, that should be pretty safe 11:06 -!- creslin_ [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 11:06 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 11:08 -!- zaptrem_ [6b4d6a17@gateway/web/freenode/ip.107.77.106.23] has joined #lnd 11:09 < zaptrem_> Hello. Is it possible to create an LND invoice that can accept multiple payments? (E.g., a donation box) 11:10 < Veggen> why would you do that? Imo, you'd just type in a number, click *donate*, and get an invoice back. 11:10 < Veggen> now, I think there's going to be support for invoices where there's no pre-allocated value. 11:13 < zaptrem_> So one would need to implement a JS API to create a donation box that auto-generates invoices? 11:14 -!- galileopy [~galileopy@unaffiliated/galileopy] has joined #lnd 11:14 < ChunkyPuffs> where can I get a precompile of btcd 11:17 < deepcore> 2018-01-29 20:16:55.588 [ERR] RPCS: unable to shutdown password gRPC proxy: close tcp 127.0.0.1:8080: use of closed network connection 11:17 < deepcore> 2018-01-29 20:16:55.588 [INF] LTND: Primary chain is set to: bitcoin 11:17 < deepcore> 2018-01-29 20:16:55.588 [INF] LTND: Initializing bitcoind backed fee estimator 11:17 < deepcore> 2018-01-29 20:17:05.195 [INF] LNWL: Opened wallet 11:17 < deepcore> unable to start wallet: status code: 401, response: "" 11:17 < deepcore> unable to create chain control: status code: 401, response: "" 11:17 < deepcore> status code: 401, response: "" 11:17 < deepcore> does the node need to be fully synced before I can create a wallet with lncli? 11:18 < blademccool> from my experience 401 = not auth to talk to your bitcoind rpc 11:18 < deepcore> ok, thanks 11:19 < spudowiar> https://twitter.com/spudowiar/status/958056758131544064 11:19 < spudowiar> buZz: ^^ My Lightning mainnet map :) 11:19 < spudowiar> @justin ^^ 11:20 -!- creslin [~textual@deposing-waterfront.volia.net] has joined #lnd 11:20 < buZz> cool! 11:22 -!- creslin [~textual@deposing-waterfront.volia.net] has quit [Client Quit] 11:23 -!- Soopaman [~soopaman@198.16.243.66] has quit [Quit: Leaving.] 11:25 < zaptrem_> I wrote a guide for the crazies coming through asking for LN on mainnet help: https://medium.com/@zaptrem/mainnet-lightning-run-lnd-zap-desktop-on-windows-f73cf78dd633 11:26 < ChunkyPuffs> On windows 11:26 < ChunkyPuffs> sigh 11:26 < ChunkyPuffs> I give up trying to run it on liunx 11:26 < zaptrem_> Yep, on Windows 11:26 < ChunkyPuffs> I don't know who would want to run a daemon on Windows. 11:27 < ChunkyPuffs> Giving up til there's a full guide, I can't even compile btcd because its far more complicated than it needs to be with GO 11:27 < ChunkyPuffs> and there's no precompile 11:27 < spudowiar> zaptrem_: PLZ NO 11:27 < buZz> i dont understand why ppl would -want- to run windows 11:27 < ChunkyPuffs> Exactly 11:27 < spudowiar> zaptrem_: We don't need more people running it on mainnet and losing money :( 11:27 < zaptrem_> I probably would have written it for Linux, but all of the Github guides are already written for Linux people. As I learned over the past weekend (my VPS provider kicked me off after they decided that Bitcoin nodes are actually Bitcoin miners) Windows users are left out in the cold by many guides. 11:27 < ChunkyPuffs> I don't know anybody who would want to run a 24/7 thing on Windows. 11:27 < ChunkyPuffs> What guides on Linux? 11:27 < ChunkyPuffs> I can't find one. Link me one. 11:28 < buZz> zaptrem_: which provider? 11:28 < zaptrem_> WootHosting @buZz 11:28 < buZz> ChunkyPuffs: https://github.com/LN-Zap/zap-desktop 's README.md 11:28 < ChunkyPuffs> ??? 11:28 < ChunkyPuffs> That's a wallet. 11:28 < buZz> ??? 11:28 < buZz> that link was for Zap desktop aswell 11:28 < ChunkyPuffs> ??? 11:29 < ChunkyPuffs> That's a wallet. 11:29 < buZz> and? 11:29 < ChunkyPuffs> https://github.com/lightningnetwork/lnd 11:29 < ChunkyPuffs> If you could give me a guide for running LND, I would be very grateful. 11:29 < buZz> ok, you're sad a zap desktop howto for windows isnt for linux? 11:29 < buZz> because you want to run something else? :P 11:29 < ChunkyPuffs> No, I said guide for running a node. 11:29 < blademccool> anyone tracking main net lost funds and the specific method by which funds were lost? because until that is ongoing i am doubtful of lost main net money claims. 11:30 < buZz> how about https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md 11:30 < zaptrem_> @spudowiar If it is possible to remove text from an IRC chat I can remove it here, I wrote the guide in a way that people who otherwise wouldn't have been able to figure it out (those who would complain if they lost funds) still probably wouldn't be able to understand it. Mainly, the guide is for people like me who nearly threw their computers out the window after dealing with all of the Windows-specific installation and compile proble 11:30 < buZz> zaptrem_: its not, IRC isnt facebook 11:30 < ChunkyPuffs> I'm not critiscizing what you did. 11:30 < ChunkyPuffs> I just want to actually run a node, but it seems impossible on Linux right now. 11:30 < zaptrem_> ¯\_(ツ)_/¯ 11:30 < ChunkyPuffs> There is absolutely no guidance I can find. 11:30 < buZz> ChunkyPuffs: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md 11:31 < ChunkyPuffs> thx 11:31 < buZz> that link was right on the page you yourself posted 11:31 < ChunkyPuffs> Golang isn't a package in ubuntu 16.04 11:31 < ChunkyPuffs> that version, I mean. 11:32 < buZz> thats outside of scope 11:32 -!- creslin [~textual@deposing-waterfront.volia.net] has joined #lnd 11:32 < zaptrem_> @ChunkyPuffs If you don't want to do it on Windows (which is what I wrote my guide for) there was a linux-specific guide on Medium floating around last week. I think it may have been for c-lightning, though. 11:32 < buZz> you could probably find a howto setup a golang install yourself 11:32 < spudowiar> zaptrem_: Idk, I just think that it's better to not have guides floating around :/ 11:32 < blademccool> ChunkyPuffs: add universe repo or whatever. Synaptic package manager found a go 1.9 for me. 11:32 < spudowiar> But that's just my opinion 11:33 < blademccool> ChunkyPuffs: then set necc env vars and you're pretty much off to the races with go. 11:33 < buZz> blademccool: afaik all 'lost money' was in closing channels 11:33 < ChunkyPuffs> package path: unrecognized import path "path" (import path does not begin with hostname) 11:33 < ChunkyPuffs> I just get that whenever I try and get glide 11:33 < zaptrem_> More people means more setups means more bugs located means quicker development, from how I see it. At the bottom of the post I suggested people complain to me on Twitter, so I can filter out most of the stupidity. 11:33 < ChunkyPuffs> I thought I did it all right earlier, following this guide didn't change it gmm 11:34 < ChunkyPuffs> hmm 11:34 < buZz> ChunkyPuffs: dont copypaste commands without reading them ;) 11:34 < spudowiar> zaptrem_: Well, you can get more people, more setups and more bugs located on testnet :) 11:34 < ChunkyPuffs> Excuse me? 11:34 < ChunkyPuffs> This is a fresh ubuntu install, I don't understand what I'm supposed to do, if not that. 11:34 < ChunkyPuffs> I just want to set up a daemon and worry about configuration later.. 11:34 < buZz> isnt ubuntu already on 18.x ? 11:34 < ChunkyPuffs> I've never once played with GO. 11:34 < ChunkyPuffs> Don't be bourgeois 11:34 < buZz> oh 17.10 still 11:35 < ChunkyPuffs> 17.10 broke basically every cryptonight miner dependency for me. 11:35 < buZz> but i agree, 'Go' makes lnd less relevant to most people 11:35 < ChunkyPuffs> so, I need *one* bit of advice, how do I fix that issue with my path? 11:35 < blademccool> i find the fact that its in go makes it more accessible to me, heh 11:36 < ChunkyPuffs> "import path does not begin with hostname" 11:36 < buZz> blademccool: hehe, well you might be the exception that confirms the rule :P 11:36 < buZz> ChunkyPuffs: you specified a import path of "path" ? 11:36 < ChunkyPuffs> I did not specify it, no 11:37 < buZz> but that was your error 11:37 < ChunkyPuffs> it is as default 11:37 < buZz> > 20:33:27 < ChunkyPuffs> package path: unrecognized import path "path" 11:37 < ChunkyPuffs> I'm looking it up on google. 11:37 < ChunkyPuffs> "export GOROOT=/usr/local/go" is suggested, what's the default? 11:37 < ChunkyPuffs> if I have to reset my goroot 11:39 < blademccool> Chunky: my bashrc has lines like this in it that I made. i'm ubuntu 16.04 with go installed via synaptic. 11:39 < blademccool> https://paste.ee/p/J0Ob4 11:40 < ChunkyPuffs> right, the problem is that I have 1.6 11:40 < ChunkyPuffs> ffs 11:41 -!- zaptrem_ [6b4d6a17@gateway/web/freenode/ip.107.77.106.23] has quit [Ping timeout: 260 seconds] 11:41 < ChunkyPuffs> how does ubuntu get away with this 11:44 < ChunkyPuffs> do go get commands have to be ran as sudo? 11:45 -!- mb_lightning [d9696d4f@gateway/web/freenode/ip.217.105.109.79] has joined #lnd 11:45 < ChunkyPuffs> buZz, go get -u github.com/Masterminds/glide 11:45 < ChunkyPuffs> go install vendor/golang_org/x/crypto/chacha20poly1305: open /usr/lib/go-1.9/pkg/linux_amd64/vendor/golang_org/x/crypto/chacha20poly1305.a: permission denied 11:49 < ChunkyPuffs> I give up 11:49 < ChunkyPuffs> I hate go 11:49 < buZz> unix systems dont usually allow user accounts write access to system folders like /usr/lib etc 11:49 < ChunkyPuffs> So the lnd is for proper experienced sysadmins and not noobs, god it 11:49 < ChunkyPuffs> got it 11:49 < ChunkyPuffs> also god it. 11:49 < ChunkyPuffs> as in god damn it 11:50 < buZz> LN in general is not for noobs yet :) 11:50 < ChunkyPuffs> Call me when lnd is as simple to get started as the monero daemon 11:50 -!- zaptrem [6b4d6a18@gateway/web/freenode/ip.107.77.106.24] has joined #lnd 11:50 < mb_lightning> Well, you gotta give Chunky credits for making it here ;) 11:50 < ChunkyPuffs> I just wanna help the network, jesus christ 11:50 < mb_lightning> I know 11:50 < zaptrem> Hello, if anyone sent me a message after I sent my last one, I missed it due to spotty connection 11:50 < ChunkyPuffs> You're telling me there's no precompiled binary I can just run on boot to help the network? 11:51 < mb_lightning> I just managed to get lnd running myself (testnet obv) 11:51 < mesh_> 8:34 am zaptrem_: Well, you can get more people, more setups and more bugs located on testnet :) 11:51 < mesh_> That's the only one zaptrem ^ 11:51 < zaptrem> ChunkyPuffs: If you want to run on the mainnet, either follow this guide https://medium.com/@zaptrem/mainnet-lightning-run-lnd-zap-desktop-on-windows-f73cf78dd633 or this guide for Linux: https://medium.com/@dougvk/run-your-own-mainnet-lightning-node-2d2eab628a8b 11:51 < ChunkyPuffs> The problems I have are related to go 11:52 < mb_lightning> Can't install the proper version of Go? 11:52 < ChunkyPuffs> Right, this article is garbage. 11:52 < blademccool> Chunky do you have synaptic package manager? that made it really easy to end up with a go 1.9 in /usr/lib 11:52 < ChunkyPuffs> "Sync your full bitcoin node" 11:52 < ChunkyPuffs> Which one? 11:52 < meshcollider> ChunkyPuffs: not at the moment, there should be when the next release is made 11:52 < ChunkyPuffs> btcd or the official core daemon?? 11:52 < zaptrem> The people here tend to be busy getting the network ready for mainstream use. They're in a race to beat the scaling situation before it ruins the community, so it is best ot let them focus on their jobs at Blockstream/Lightning Labs/etc 11:53 < ChunkyPuffs> Oops, forgot to specify, wowza, great, just wasted hours. 11:53 < blademccool> Chunky: lnd supports btcd or bitcoin core backends. so choice is yours. 11:53 < ChunkyPuffs> Which is forgotten to be mentioned on the git description. 11:53 < zaptrem> ChunkyPuffs: Are you tlaking about my Windows article or the second Linux one? If anything is unclear on mine I can answer the question for you and fix it there as well. 11:53 < ChunkyPuffs> So conflicting info everywhere, was under the impression only btcd was supported. 11:53 < ChunkyPuffs> The linux article. 11:54 < zaptrem> Both Bitcoind and BTCD are supported, but bitcoind requires a little extra setup 11:54 < zaptrem> bitcoind support was only added recently 11:54 < zaptrem> so the conflicting info is normal 11:54 < blademccool> Chunky: this stuff is evolving daily. there are breaking changes still happening. dont expect docs to stay current without help. read source code if docs are out of date. thats where we are with this right now. 11:56 < ChunkyPuffs> This go stuff is just annoying. 11:56 < ChunkyPuffs> It'd all be set up properly by now if I didn't have permission issues by default, just by copying and pasting commands. 11:57 < ChunkyPuffs> oh.. ok.. 11:58 < ChunkyPuffs> So you have to manually make the directories for a given go package, annoying as hell, but I understand. 11:59 -!- colatkinson [~colatkins@nagini-20.dynamic.rpi.edu] has joined #lnd 12:01 < ChunkyPuffs> Can someone proficient with go tell me how to have this not be the case? 12:01 < ChunkyPuffs> You can't seriously need to manually make directories for everything you wanna install can you? 12:01 < mb_lightning> Sooo... I figured I'd try running a testnet node myself, but for some reason I'm getting an error when trying to open a channel; 12:01 < mb_lightning> [lncli] rpc error: code = Unknown desc = not enough witness outputs to create funding transaction, need 0.001 BTC only have 0 BTC available 12:01 < ChunkyPuffs> https://paste.ee/p/bkyGR 12:02 < mb_lightning> What am I missing there? 12:03 < blademccool> mb_lightning: did you fund your node, and wait for the funding tx to confirm? 12:03 < meshcollider> mb_lightning: as the error says, you don't have enough tBTC in your wallet to fund a channel :) Grab some from a faucet first 12:04 < blademccool> lncli newaddress np2wkh .... use a faucet to send get some sent to your ln wallet 12:05 < mb_lightning> Cool, I thought I had some, walletbalance says >1 btc. 12:06 < blademccool> mb_lightning: if its showing under the confirmed balance then it should be usable to make channels afaik 12:07 < mb_lightning> That's weird. 12:08 < mb_lightning> Just added the new address, let's see if I can receive funds there. 12:09 < mlz> you have to have tbtc in a segwit address 12:10 < mlz> mb_lightning, is this LND related? 12:14 < mb_lightning> You're probably right, my bad. I turned out to have the balance in a non-segwit address, it's working now, sorry for disturbing. 12:14 -github-lnd:#lnd- [lnd] sp4ke opened pull request #689: add a basic makefile (master...makefile) https://git.io/vNSSs 12:15 < cloaks> keep up the great job guys 12:17 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has joined #lnd 12:18 < ChunkyPuffs> Can anybody help me out with `go install . ./cmd/... 12:18 < ChunkyPuffs> ` 12:18 < zaptrem> If a channel is closed by a single party (e.g., counterparty goes offline) how long until the funds are usable again? 12:18 < zaptrem> Also how are aliases set in LND? 12:20 < blademccool> zaptrem: alias and color can be defined in the config file 12:21 < meshcollider> ChunkyPuffs: what about it? 12:21 < ChunkyPuffs> meshcollider, 12:21 < ChunkyPuffs> https://paste.ee/p/bkyGR 12:22 < meshcollider> are you running as an unprivileged user 12:23 < zaptrem> Does an RPC command still exist blademccool? 12:23 < ChunkyPuffs> Yes, I'm running as an unprivileged user 12:23 < ChunkyPuffs> I am not told to run privileged at any point in the lnd documentation 12:23 < ChunkyPuffs> and sudo is never supplied in any other build step for any other bitcoin related project.. 12:24 < ChunkyPuffs> Besides, running it as sudo is *wrong*, considering gopath would have to be set for it 12:24 < meshcollider> ChunkyPuffs: does the user have permission to write to your $gopath ? 12:24 < ChunkyPuffs> how do I find that out? 12:24 < ChunkyPuffs> presumably, I mean, it's just my home directory. 12:26 < blademccool> zaptrem: i believe the rpc command was removed in favor of startup config 12:26 < meshcollider> ChunkyPuffs: use ls -ld 12:27 < ChunkyPuffs> oh for fuck sake 12:28 < ChunkyPuffs> it's using go 1.6 12:28 < ChunkyPuffs> how do I stop this wtf 12:28 < ChunkyPuffs> I hate go 12:28 < zaptrem> Chill bruh 12:28 < ChunkyPuffs> It's so annoying when the monero daemon, bitcoin daemon, all just work, on any distro. 12:28 < zaptrem> You'll figure it out eventually, or you'll move on if it isn't important to you. 12:28 < zaptrem> It took me a week of fiddling in my spare time to get it working 12:30 < buZz> ChunkyPuffs: hehe, guess you never tried it on a centos machine ^_^ 12:30 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has quit [Ping timeout: 260 seconds] 12:30 < ChunkyPuffs> Well, most distros. 12:31 < ChunkyPuffs> I do wanna try centos at some point, but I'm still too noobish for that. 12:31 < spudowiar> Just run Arch Linux :) 12:31 -!- Soopaman [~soopaman@198.16.243.66] has joined #lnd 12:31 < spudowiar> Despite what people might say, it doesn't break (except when you update systemd. TBH, even that hasn't happened for a while now) 12:31 < spudowiar> And you have the latest packages all the time 12:32 < zaptrem> If I entrust a certain amount of BTC to Autopilot, how much will it put in each channel (assuming I set the max channels to approaching infinity) 12:32 < meshcollider> spudowiar: yeah I run arch 12:33 < buZz> spudowiar: heh, systemd's introduction to 'linux world' is what drove me to run devuan on all my boxes now ^_^ 12:34 -!- waxwing [~waxwing@unaffiliated/waxwing] has quit [Quit: ZNC 1.6.5 - http://znc.in] 12:35 < spudowiar> https://twitter.com/spudowiar/status/958076108913639424 12:35 < spudowiar> buZz: Eh, it's not so bad nowadays. I don't like its design but since a few months ago, it really does "just work" 12:36 < spudowiar> My Lightning explorer is coming along nicely 12:36 < spudowiar> I made it look like ACINQ :P 12:36 < spudowiar> Except for, you know, all the useful features :) 12:38 < lndbot> After opening a channel, how long do we have to wait before closing it? 12:38 < mb_lightning> spudowiar: nice, now post it on /r/lightningnetwork ;) 12:38 < lndbot> It says, unable to find chan id 12:40 < spudowiar> mb_lightning: https://www.reddit.com/r/lightningnetwork/comments/7tvctd/all_the_lightning_nodes_with_external_ip/ 12:40 < spudowiar> :) 12:40 <@roasbeef> zaptrem: guides like that aren't really helpful imo, don't direct noobs to run on mainnet 12:40 < mb_lightning> spudowiar: nice :) 12:40 < spudowiar> gtg now, bye :) 12:41 < lndbot> I see the channel in listchannels 12:41 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 12:43 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #689: add a basic makefile (master...makefile) https://git.io/vNSSs 12:43 <@roasbeef> ChunkyPuffs: you installed go incorrectly 12:43 < meshcollider> where do the messages from lndbot actually come from 12:43 < meshcollider> is it slack? 12:43 < zaptrem> roasbeef: I'm sure noobs would not be able to accomplish it even with the guide, it is mainly for people like me who were tearing their hair out dealing with specific prerequisite problems. 12:44 <@roasbeef> :/ 12:44 <@roasbeef> meshcollider: yeh it's slack 12:44 <@roasbeef> zaptrem: noob to following some set up script, and noob to LN in general are diff 12:44 <@roasbeef> guides like that aren't helpful 12:45 -!- creslin [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 12:45 <@roasbeef> if you wan'ted to make it for testnet on the other hand :) 12:47 -!- creslin [~textual@93.73.60.116] has joined #lnd 12:48 < zaptrem> Apart from screaming at me on Twitter (like I told them too), what is the worst they can do? They will simply be mocked on Reddit for being stupid with their money. I can modify it encouraging people to use testnet instead, but I feel kinda obligated to share the knowledge I gained from the time I spent setting it and its dependencies up on Windows. 12:49 < zaptrem> told them to do* 12:53 -!- colatkinson [~colatkins@nagini-20.dynamic.rpi.edu] has quit [Ping timeout: 256 seconds] 12:55 <@roasbeef> zaptrem: guess who them come to in the worst case? 12:55 < mlz> roasbeef, i think they will hire lawyers and go after zaptrem 12:56 < zaptrem> In the worst case, more bugs are revealed and fixed 12:56 < mlz> i guess this is your real name: ryan tremblay 12:56 < mlz> not hard to find you 12:56 -!- colatkinson [~colatkins@2620:0:2820:1502:5ee0:c5ff:fe8c:502d] has joined #lnd 12:56 < zaptrem> Yep 12:56 < zaptrem> Not trying to stay anonymous 12:57 < zaptrem> My name is on the Medium post :P 12:57 < ChunkyPuffs> roasbeef, what's the mainnet lnd command? 12:57 < mlz> ChunkyPuffs, "launch mainnet" 12:57 < ChunkyPuffs> --bitcoin.mainnet? 12:57 < ChunkyPuffs> No I mean the launch param 12:57 < ChunkyPuffs> what's simnet, also? 12:57 < zaptrem> "Activate money loss mode" 12:58 < blademccool> i dont believe the software currently contains the mainnet configuration. it appears to take a few lines of additional code to enable it. 12:58 < zaptrem> lnd /burncash 12:58 < ChunkyPuffs> >/ 12:58 < mb_lightning> lnd -deletebtc 12:58 < ChunkyPuffs> I guess I won't be running a node then 12:59 < ChunkyPuffs> rip 12:59 < mlz> zaptrem, you're not helping windows noobs, if you can't get them on testnet, they're a loss cause, but if you get them on mainnet, a bigger loss cause because they still can't learn anything and they're going to lose money, they're huge opportunities for hackers 12:59 < mb_lightning> Just wait till it's tested and polished before going on mainnet. 12:59 < ChunkyPuffs> No? 12:59 < ChunkyPuffs> I wanna run it now. 12:59 < ChunkyPuffs> http://lnstat.ideoflux.com:3000/dashboard/db/lightning-network?refresh=5m&orgId=1 13:00 < ChunkyPuffs> There's 340+ nodes 13:00 < mb_lightning> Yeah, 340+ people who're crazy enough to test an alpha with real money. 13:00 < zaptrem> Unless you put money in it there isn't much you can do with it ChunkyPuffs. However, if you put money in it you will likely lose said moeny. 13:00 < zaptrem> money* 13:01 < blademccool> it would be cool to see a breakdown of mainnet nodes by implementation. maybe c-lightning or eclair communities are more supporting of diving into mainnet. 13:01 < mlz> so far i don't know anyone running eclair on mainnet, except their devs probably 13:01 < zaptrem> Yeah, c-lightning is gung-ho on mainnet stuff. 13:02 < mlz> hohoho 13:02 < ChunkyPuffs> Right, thanks for your opinion. 13:02 < ChunkyPuffs> So how do I launch the node on main-net? 13:02 < mlz> ChunkyPuffs, go away 13:02 < zaptrem> lol 13:02 < ChunkyPuffs> No. 13:03 < ChunkyPuffs> So what do you think Andreas means when he says "Go and run a lightning node"? 13:03 < zaptrem> If you still can't manage it with the guides available you really shouldn't be dancing around this flame. 13:03 < mlz> zaptrem, what you need to do is convincing blockstream to let us buy the damn stickers on testnet 13:03 < ChunkyPuffs> Does he mean "Consider creating lots of payment channels" 13:03 <@roasbeef> kek 13:03 < ChunkyPuffs> No, he means "Go and run a lightning node" 13:03 < zaptrem> Lightning Nodes do basically nothing when they aren't connected to a channel 13:03 < blademccool> he means do it without distracting the devs too much, where "too much" is defined by the devs, and in this channel the threshold for "too much" may be at risk of being crossed. 13:03 < mlz> cool, i like to hear this: If you still can't manage it with the guides available you really shouldn't be dancing around this flame. 13:03 < ChunkyPuffs> I don't have to put money into this. And I want to be one of the first to make some main-net lightning payments, is it not obvious that I don't care that much about losing the money? 13:03 < mlz> :thumbsup: 13:04 < mlz> you want to be one of the first mainnet idiots? 13:04 < ChunkyPuffs> Nice. 13:04 < zaptrem> ChunkyPuffs: You *must* deposit BTC in order ot make a lightning payment, that is how it works. Did you read the Poon's Lightning paper? 13:05 < ChunkyPuffs> Read what I said. 13:05 < ChunkyPuffs> I don't need to deposit btc in order to run a node. 13:05 < ChunkyPuffs> I need to deposit btc in order to make a payment channel, which I'll do at a later date. 13:05 < zaptrem> You do, otherwise it will never connect... 13:05 < ChunkyPuffs> That's an option, right? 13:05 < mlz> there are hackers lurking and scanning mainnet, FYI 13:05 < ChunkyPuffs> Well how small is that initial cost? 13:05 < ChunkyPuffs> I'll happily put in $20. 13:05 < blademccool> tis true with just a node you could get a hubbing service to open a channel to you for a small on chain fee. (well it will be.) 13:05 < mlz> they are scanning every node and every port 13:06 < ChunkyPuffs> Well I'm running it on a not very consequential dedicated machine. 13:07 < mb_lightning> I have a question: I want to get my Raspberry Pi to run a lightning testnet node and want to automatically start the node when the Pi starts up. I tried doing that by launching lnd as a service, but I cannot figure out how to make it unlock the wallet upon startup. Any advice? 13:09 < mb_lightning> (also, I probably butchered some terms there, I might be one of those dreaded "Windows noobs") 13:12 < ChunkyPuffs> If there's parameters you can launch the daemon with to do that, you can use crontab 13:12 < ChunkyPuffs> crontab -e 13:12 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has joined #lnd 13:12 < blademccool> mb_: could run without the wallet being locked 13:12 < ChunkyPuffs> @reboot `command you want` 13:12 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has quit [Client Quit] 13:12 < mlz> mb_lightning, lncli unlock 13:13 < mlz> then put in your pw 13:13 < blademccool> or in lnd.conf "noencryptwallet=true" 13:13 < ChunkyPuffs> crontab -e, use nano @reboot `thing` add another line, `lncli unlock pw` 13:13 < mlz> ya 13:13 < mlz> lncli --noencryptwallet 13:13 < mlz> ugh 13:13 < ChunkyPuffs> you could have the crontab daemon unlock the wallet with your password, and do it on sudo, that way you don't have to not encrypt it, and it's still relatively secure since you'll need user permissions to see the sudo crontab 13:13 < mlz> s/lncli/lnd/ 13:14 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has joined #lnd 13:14 <@roasbeef> you can also unlock the wallet remotely 13:14 -!- zaptrem [6b4d6a18@gateway/web/freenode/ip.107.77.106.24] has quit [Ping timeout: 260 seconds] 13:18 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has quit [Client Quit] 13:19 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has joined #lnd 13:19 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has quit [Quit: Leaving] 13:19 < mb_lightning> Not encrypting the wallet seems horribly unsafe though. 13:21 -!- zaptrem_ [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has quit [Client Quit] 13:23 < blademccool> it has to be decrypted to operate tho so if it was going to on 24/7 it would always be unencrypted, no? 13:23 < mb_lightning> It times out. Ohwell, I'll go read up on the things and I'll be back I suppose. Either I'll learn how to get it to work or something comes out that'll make it easier ^^ 13:33 -!- zaptrem [6b4d6a18@gateway/web/freenode/ip.107.77.106.24] has joined #lnd 13:37 -!- mb_lightning [d9696d4f@gateway/web/freenode/ip.217.105.109.79] has quit [Quit: Page closed] 13:50 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 13:51 -!- zaptrem [6b4d6a18@gateway/web/freenode/ip.107.77.106.24] has quit [Ping timeout: 260 seconds] 14:15 -!- waxwing [~waxwing@91.216.245.111] has joined #lnd 14:16 -!- waxwing [~waxwing@91.216.245.111] has quit [Changing host] 14:16 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #lnd 14:17 <@roasbeef> it doesn't time out, but all access requires macaroons 14:17 <@roasbeef> those can be distributed, granular, etc 14:27 -!- colatkinson [~colatkins@2620:0:2820:1502:5ee0:c5ff:fe8c:502d] has quit [Quit: colatkinson] 14:28 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 252 seconds] 14:28 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 14:29 -!- raucao [~raucao@5.148.180.93] has quit [Quit: ZNC - http://znc.in] 14:29 -!- grubles [~grubles@unaffiliated/grubles] has joined #lnd 14:39 -!- richard87 [~richard87@237.92-221-98.customer.lyse.net] has quit [Quit: richard87] 14:39 -!- richard87 [~richard87@237.92-221-98.customer.lyse.net] has joined #lnd 14:44 -!- richard87 [~richard87@237.92-221-98.customer.lyse.net] has quit [Client Quit] 14:44 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 14:44 -!- richard87 [~richard87@237.92-221-98.customer.lyse.net] has joined #lnd 14:46 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Quit: Leaving] 14:51 < Veggen> there's no significant difference between running an LN node to a local bitcoind and to a remote one, right? 14:54 -!- grubles [~grubles@unaffiliated/grubles] has joined #lnd 14:55 < Veggen> just thinking about secure setups. I guess LND will run nicely on a rpi 3? 15:02 -!- creslin [~textual@93.73.60.116] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 15:20 <@roasbeef> Veggen: just latency 15:20 <@roasbeef> actually for bitcoind, it's all plaintext, so you might wnat to have a reverse ssh tunnel or something like that 15:21 < cryptodechange> Are there any guides for something like that? 15:24 <@roasbeef> dunno if any official, but you can prob find some by googling 15:24 <@roasbeef> on the lnd side, you'd just need to point to the endpoint of the tunnel 15:24 <@roasbeef> as far as telling it where the bitcoind node is 15:24 -!- Memetic [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 15:26 -github-lnd:#lnd- [lnd] MeshCollider opened pull request #691: Help text & sample config improvements (master...201801_docfixes) https://git.io/vN9IF 15:26 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 15:27 -!- Maky [~m@BSN-142-247-100.dynamic.siol.net] has quit [Ping timeout: 240 seconds] 15:28 -!- Maky [~m@BSN-142-247-100.dynamic.siol.net] has joined #lnd 15:46 -!- zaptrem [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has joined #lnd 15:47 < zaptrem> Is there a way to download IRC chat history? I never know if I’ve missed anything. 15:51 -!- fronti [~fronti@irc.fh-biergarten.de] has joined #lnd 15:51 -!- shtirlic [~shtirlic@Shtirlic-2-pt.tunnel.tserv6.fra1.ipv6.he.net] has joined #lnd 15:52 -!- zaptrem [~Mutter@2600:380:bd29:f398:58d1:aa32:7d7c:9415] has quit [Quit: Mutter: www.mutterirc.com] 15:54 -!- Graylan [uid277037@gateway/web/irccloud.com/x-xkjwsusivecjzvjv] has quit [Quit: Connection closed for inactivity] 15:57 <@roasbeef> should have logs up in a bit 15:58 <@roasbeef> what i do is use tmux+mosh 16:12 -!- capa66 [capa66@gateway/vpn/privateinternetaccess/capa66] has quit [Ping timeout: 240 seconds] 16:15 < mlz> ok here's my notes to install the latest Go version if anyone's interested: https://paste.ee/p/62WaS#VlbiUZHcHTWDt4TumrVQqJOZHi7JGPZy 16:16 <@roasbeef> mlz: 1.10? that's coming out soon 16:16 < mlz> wut 16:16 < mlz> this is 1.9.3, roasbeef 16:17 < mlz> Go has been very fast in pushing out new versions, now i can see why you're so speedy in everything, roasbeef lol 16:17 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has quit [Ping timeout: 248 seconds] 16:18 <@roasbeef> heh, lnd will be on a regualr schedule after 0.4 as well 16:18 < mlz> and when is this? 16:20 < meshcollider> Soon™? 16:25 <@roasbeef> on deck: finish switch/circuit persistence, expose wallet seed and allow starting from existing seed, some autopilot tweaks, fee estimation fixes 16:26 <@roasbeef> and misc bugs 16:28 -!- zaptrem [4a4716aa@gateway/web/freenode/ip.74.71.22.170] has joined #lnd 16:29 < zaptrem> I think I found my first bug(s?) 16:29 <@roasbeef> yeyy 16:29 < mlz> meshcollider, haha :D 16:30 < zaptrem> I'll get back to you, brb 16:35 -!- nirved [~nirved@2a02:8071:b58a:3c00:ad92:eca7:97d5:1b42] has quit [Quit: Leaving] 16:51 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Quit: Leaving.] 16:55 -!- crom__ [b00a89b3@gateway/web/freenode/ip.176.10.137.179] has joined #lnd 16:56 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #lnd 17:03 -!- rotarydialer_ [~rotarydia@unaffiliated/rotarydialer] has joined #lnd 17:05 < rotarydialer_> Almost bought a tshirt with lightning, but I think I hit a snag... 17:07 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 17:09 < zaptrem> Same here 17:09 < zaptrem> roasbeef: I'm currently being spammed with "PEER: Peer shutting down, could not enqueue msg." 17:10 < zaptrem> All of my channels are closing as well. 17:14 <@roasbeef> zaptrem: if the chans are closing that's no issue, just someone may be closing them 17:14 <@roasbeef> if you're trying to interface with c-ligthning, it gets twitchy at times and will force close 17:14 <@roasbeef> then when you reconnect (if doesn't send the no sync bit) it'll send the same error then d/c 17:15 <@roasbeef> then we reconnect, and so on 17:15 < zaptrem> The spamming is the main issue, I'm also getting a bunch of other juicy stuff: 17:15 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 240 seconds] 17:15 < zaptrem> Will the debug logs reveal any private information? 17:15 <@roasbeef> nah 17:15 < zaptrem> I see mostly public keys and node ids 17:15 <@roasbeef> or I guess we'll see :) 17:15 < zaptrem> okay, I'll stuff a sample in a pastebin 17:17 < zaptrem> I think this general sequence repeats every few seconds (mostly spamming the peer shutting down message): https://pastebin.com/BfG8DZ2e 17:18 < zaptrem> Originally the debug spam looked different (when I first started it), it mostly talked about ping/pings and network updates. 17:18 < zaptrem> ping/pongs* 17:19 <@roasbeef> yeh it's just c-lightning 17:19 < mlz> zaptrem, is it your first time running LND? 17:19 <@roasbeef> it'll reconnect on a tight loop 17:19 < zaptrem> Not first time. 17:21 < zaptrem> The peer shutting down spam wasn't there last night, when I had a channel or two open already. 17:21 <@roasbeef> c-lgithnig tried to close out 17:21 <@roasbeef> then realized it couldn't 17:21 < mlz> wow a lot of those msgs " PEER: Peer shutting down, could not enqueue msg." 17:21 <@roasbeef> then will just spin on this like forever 17:21 < mlz> what is it roasbeef ? some peers are shutting down? 17:21 < zaptrem> So it isn't me, but a node I'm connected to is bugging out? 17:22 <@roasbeef> yeh 17:22 < mlz> ah our friends c-lightning peers 17:22 <@roasbeef> it's that we're trying to send it some messages, but then it disconnects, then reconnects, repeat 17:22 < mlz> i just helped rusty find a bug :D 17:23 < zaptrem> Could that be the reason for the closing channels? Or is that just people deciding they don't like me anymore (they were channels I created and funded) 17:23 <@roasbeef> nah it tried to clsoe, but then didn't like what we negotiated, so it force closed 17:24 <@roasbeef> rather than just taking those fees, as now it's put itself at a disadvantage 17:25 -!- crom__ [b00a89b3@gateway/web/freenode/ip.176.10.137.179] has quit [Ping timeout: 260 seconds] 17:28 < zaptrem> One of them is a massive hub peer, why would they kick me off? 17:28 < zaptrem> Additionally, when I try to reconnect to them, I'm told I'm already connected to them. 17:31 <@roasbeef> people don't know what they are doing 17:31 <@roasbeef> is you're connected to the blockstream store, they had some issues, and maybe wanted to manually close the channel 17:41 < mlz> roasbeef, LND can set a limit of max channels we want, right? 17:42 < rotarydialer_> Well, I successfully funded a channel, and then withdrew from channel. I guess that's an accomplishment of sorts. I really want a lightning shirt to go with some alpaca socks. 17:43 < rotarydialer_> probably everyone using this guide is killing the network? https://medium.com/@dougvk/run-your-own-mainnet-lightning-node-2d2eab628a8b 17:43 < mlz> rotarydialer_, what do you mean "withdrew from channel"? 17:44 < rotarydialer_> Well, I wanted to see if I could get my bits out of the lightning and back to a btc wallet. It worked and with 3 sat/B fee 17:45 -!- rotarydialer_ is now known as rotarydialer 17:45 <@roasbeef> killing the network? nah 17:46 <@roasbeef> yeh fees are super low rn 17:46 < mlz> rotarydialer, ah you mean you sent the coins from the lightningd wallet back to your btc wallet but you didn't close the channel? 17:48 < zaptrem> I also just tried to send a payment to Y'alls after opening a few new channels and got this error: IncorrectCltvExpiry(expiry=507047, update=(lnwire.ChannelUpdate) { Signature: (*btcec.Signature)(0xc062c0f9c0)({ R: (*big.Int)(0xc05dc5cd60)(82218008190629593769969105293403528203148260455361807559564143727546095555076), S: (*big.Int)(0xc05dc5cd80)(48776818946181584091876569707020311331573034205486371987563132544044192994333) }), ChainHash: 17:48 < rotarydialer> Well, I thought the channel might be closed bc of this: "state" : "ONCHAIND_MUTUAL" 17:50 <@roasbeef> zaptrem: someone in the route isn't synced, (or at last a final payment), can happen due to a block race condition (we send, a block gets mined, etc) 17:50 < zaptrem> So the problem should go away on its own if I wait a few minutes? 17:53 -!- Giszmo [~leo@201.214.28.204] has joined #lnd 18:03 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 18:04 -!- gethh [uid264798@gateway/web/irccloud.com/x-klqarxakuddbfhwg] has quit [Quit: Connection closed for inactivity] 18:04 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #lnd 18:18 < mlz> zaptrem, are you running LND or c-lightning? 18:18 -!- Luzer [~Luzer@162-204-57-190.lightspeed.cicril.sbcglobal.net] has quit [] 18:19 -!- Luzer [~Luzer@162-204-57-190.lightspeed.cicril.sbcglobal.net] has joined #lnd 18:33 < zaptrem> I'm running LND mlz. 18:33 < zaptrem> mlz and @roasbeef, I gave it some more time and I'm still getting this error when attempting to send a payment to Y'alls: IncorrectCltvExpiry(expiry=507053, update=(lnwire.ChannelUpdate) { Signature: (*btcec.Signature)(0xc079cc1810)({ R: (*big.Int)(0xc087c020a0)(82218008190629593769969105293403528203148260455361807559564143727546095555076), S: (*big.Int)(0xc087c020c0)(4877681894618158409187656970702031133157303420548637198756313254404419 18:34 < zaptrem> ChainHash: (chainhash.Hash) (len=32 cap=32) 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, ShortChannelID: (lnwire.ShortChannelID) 506083:808:0, Timestamp: (uint32) 1517255594, Flags: (lnwire.ChanUpdateFlag) 0, TimeLockDelta: (uint16) 14, HtlcMinimumMsat: (lnwire.MilliSatoshi) 1000 mSAT, BaseFee: (uint32) 1000, FeeRate: (uint32) 10 } 18:34 < zaptrem> (it was cut off) 18:41 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 18:43 -!- Soopaman [~soopaman@198.16.243.66] has quit [Quit: Leaving.] 18:44 < mlz> zaptrem, are you running the latest master? 18:45 < zaptrem> I'm running master as of two days ago 18:57 < mlz> hm ok 18:58 < zaptrem> I can get the exact checkout date if you need it 19:02 < lndbot> chain heights are out of sync? 19:11 -github-lnd:#lnd- [lnd] aakselrod opened pull request #692: multi: upgrade macaroons to v2, replace per-method auth with interceptors (master...macaroon-encryption-upgrade) https://git.io/vN946 19:13 < zaptrem> Updated LND and I realized I'm a stupid 19:13 < zaptrem> Didn't have bitcoind txindex set ot 1 19:14 < zaptrem> *I* was the one who was out of sync :P 19:15 <@roasbeef> :p 19:15 < zaptrem> Will LND freak out if I start my node while its connected bitcoind node is still reindexing? 19:15 <@roasbeef> yes 19:16 < zaptrem> It will finish somewhere after midnight and I want LND to get back to it ASAP 19:16 < zaptrem> Will it recover or throw itself off a cliff? 19:16 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Quit: ZNC 1.6.3+deb1+trusty0 - http://znc.in] 19:17 <@roasbeef> it should recover 19:18 < zaptrem> So I'll just leave it on and let LND freak out while bitcoind reindexes, and things will be fine in the morning (assuming bitcoind finishes) 19:19 < zaptrem> Autopilot wont start messing with channels or anything, right? 19:21 <@roasbeef> well it won't start if the txindex isn't on 19:21 <@roasbeef> so wait for the indexing to finish, then start again 19:24 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 19:26 < zaptrem> @roasbeef it managed to start when it wasn't on before... bug? 19:26 <@roasbeef> well becuz you had an older version 19:26 < zaptrem> It even acted like channels were forming and being closed and so on 19:26 <@roasbeef> but dunno the order that it re-indexes 19:26 <@roasbeef> but i'd just wait for it to reindex then go from there 19:27 <@roasbeef> someone is working on a feature to allow to not txindex and also support pruned nodes 19:27 < zaptrem> LND (version from weekend) had been functioning (at least partially) with a non-txindex bitcoind node for multiple days, though it had been acting weirdly. 19:30 < zaptrem> Just to confirm: starting LND before bitcoind is finished syncing will probably break it. 19:31 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lnd 19:34 <@roasbeef> yeh actinv weirdly would make sense 19:36 < mlz> roasbeef, i doubt pruned nodes can work with lnd 19:37 < mlz> clightning: "Specify that pruned nodes are not fully supported just yet" 19:37 < mlz> https://github.com/ElementsProject/lightning/pull/791 19:39 <@roasbeef> mlz: someone is working on support for pruned nodes 19:39 < mlz> yea, good luck to them :P 19:41 < zaptrem> Weird, only now that I have set txindex=1 am I getting the error that says "txindex is not enabled," despite never receiving that error before. (Note, the node is still reindexing) I think LND currently isn't detecting nodes with txindex off like it should. 19:42 <@roasbeef> if you were running with an older version, it wouldn't detect it 19:42 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Quit: ZNC 1.6.3+deb1+xenial0 - http://znc.in] 19:42 <@roasbeef> however if the output is unspent then bitcoind will actually query the utxo set to get the transaction 19:43 < zaptrem> How old? The version I was running before was from this weekend. 19:43 < mlz> it can get old fast, we can't keep up with roasbeef lol 19:44 < zaptrem> Just not sure when the detection was added, I know bitcoind support has existed for at least a week 19:45 -!- botka1 [~nodebot@static.171.39.76.144.clients.your-server.de] has joined #lnd 19:45 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has quit [Read error: Connection reset by peer] 19:45 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 19:46 -!- booyah [~bb@193.25.1.157] has joined #lnd 19:48 -!- Soopaman [~soopaman@198.16.243.66] has joined #lnd 19:49 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 19:52 < mlz> bitcoind was added before christmas 19:53 < mlz> only for experienced testers to test 19:54 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lnd 19:56 < mlz> zaptrem, did you say you're running autopilot on mainnet? 19:58 < zaptrem> Yes, mlz 19:58 < zaptrem> Is there some game-breaking bug I should know about? 19:59 < mlz> what do you mean? 19:59 < zaptrem> You were asking about Autopilot, is there some known issue with it on mainnet? 20:00 < mlz> i think you're the only one that would run autopilot on mainnet, idk if it has any issue besides you're going to spend a lot of money in tx fees 20:00 < zaptrem> @roasbeef, can LND node connections resolve domain names? Say I wanted to connect to @testnet.testlightning.com 20:01 < mlz> sure ofc 20:01 < mlz> only clightning can't do this and i filed an issue with them 20:01 < zaptrem> Autopilot takes fee estimates from bitcoind, so wouldn't the fees be the same as always? 20:01 < mlz> why would they be the same? 20:02 < mlz> did autopilot work for you? 20:14 < zaptrem> Partially. 20:14 < zaptrem> I didn't have txindex enabled so my node was not working correctly 20:14 < zaptrem> However, it did create a few channels 20:17 < zaptrem> Well, we will see how things turned out tomorrow (if there is any reason I should disable Autopilot apart from *potential* buginess (which is what I'm here to find) before I next open my node, please tell me and I'll read it tomorrow) 20:29 < mlz> on testnet, autopilo sends the max amt that's allowed to create channels but it doesn't send a push amt 20:36 < pigeons> why does getinfo's uris: show the default port of 9735 instead of the port i specified in --listen= ? 20:40 <@roasbeef> because --externalip is what's actually exposed 20:40 <@roasbeef> err what matters at least 20:41 <@roasbeef> atm 20:47 < pigeons> can i specify a different port with --externalip? 20:48 <@roasbeef> yeh 20:48 < pigeons> thanks 20:54 -!- wef [d4fca674@gateway/web/freenode/ip.212.252.166.116] has joined #lnd 20:54 < wef> sdf 20:57 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has joined #lnd 21:08 -!- wef [d4fca674@gateway/web/freenode/ip.212.252.166.116] has quit [Ping timeout: 260 seconds] 21:10 -!- dimsumcode [~dimsumcod@pool-96-241-129-137.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds] 21:23 -!- dimsumcode [~dimsumcod@pool-96-241-129-137.washdc.fios.verizon.net] has joined #lnd 21:37 -!- Giszmo [~leo@201.214.28.204] has quit [Quit: Leaving.] 21:51 -!- Memetic [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 21:55 -!- Graylan [uid277037@gateway/web/irccloud.com/x-oxtsownryvsdnfrd] has joined #lnd 22:00 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Quit: Leaving] 22:04 -!- Graylan [uid277037@gateway/web/irccloud.com/x-oxtsownryvsdnfrd] has quit [] 22:05 -!- Graylan [uid277037@gateway/web/irccloud.com/x-zhdfxdlldpaocyif] has joined #lnd 22:35 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 240 seconds] 22:49 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 22:50 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 22:54 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Client Quit] 22:55 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 23:12 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 23:19 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 240 seconds] 23:34 -!- figitaki [~careyjane@c-73-241-109-13.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds] 23:55 -!- sovjet [~sovjet@193.189.166.102] has joined #lnd 23:57 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson]