--- Day changed Thu May 16 2019
00:22 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd     
00:25 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
00:45 -!- scoop [~scoop@63.139.48.72] has joined #lnd     
00:47 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Remote host closed the connection]     
01:10 -!- scoop [~scoop@63.139.48.72] has quit [Remote host closed the connection]     
01:15 -!- scoop [~scoop@63.139.48.72] has joined #lnd     
01:19 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd     
01:33 -!- scoop [~scoop@63.139.48.72] has quit [Remote host closed the connection]     
01:33 -!- scoop [~scoop@63.139.48.72] has joined #lnd     
01:38 -!- scoop [~scoop@63.139.48.72] has quit [Remote host closed the connection]     
02:06 -!- whysthatso [5abef909@gateway/web/freenode/ip.90.190.249.9] has joined #lnd     
02:06 < whysthatso> molz fixed
02:06 < whysthatso> the backup script from raspiblitz worked after all
02:06 < whysthatso> the scan now shows the funds and the open channel
02:06 < whysthatso> yey     
02:07 < whysthatso> and as any good user after a crisis of not knowing what the fuck i'm doing, i will proceed to read the fucking manual :)
02:26 -!- botka [~nodebot@104.248.95.16] has quit [Remote host closed the connection]     
02:26 -!- botka [~nodebot@104.248.95.16] has joined #lnd     
02:40 -!- botka [~nodebot@104.248.95.16] has quit [Remote host closed the connection]     
02:40 -!- botka [~nodebot@104.248.95.16] has joined #lnd     
03:38 < tuxx> roasbeef: how terrible is it to use lnd against neutrino mainnet (as done by lightning-app)
03:54 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 246 seconds]     
03:57 -!- drexl [~drexl@188.166.71.168] has joined #lnd     
03:59 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd     
04:02 < tuxx> https://github.com/lightninglabs/lightning-app/releases <- no arm release for raspi? :(
04:03 < tuxx> guess i'll have to build it myself *wheep*
04:06 < tuxx> i expect that shld be possible? :O
04:06 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 252 seconds]     
04:18 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd     
04:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]     
04:35 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
04:55 < molz> whysthatso, do you know we have the highest rate of failures with raspis? look at the issues on GH, just about every issue of 'database corruption' happens on those pies, FYI
04:56 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Remote host closed the connection]     
04:58 -!- lnostdal [~lnostdal@151.251.252.53] has joined #lnd     
05:03 < whysthatso> understandably as an external usb disk is not the ideal storage for running a database. especially considering that the hardware is rather on the slow side, so recuperation the way i do it always takes a couple of days...
05:03 < whysthatso> then again, it's a test setup, and i don't want to invest into a bigger machine just yet
05:04 < whysthatso> i still have no clue about the lnd network, what i am doing, what the node is doing, etc. the question for me was that if i can make some funds to acutally economically run a node, then i might be interested in setting up a machine
05:04 < whysthatso> for long term
05:05 < whysthatso> as i understand there is some way to make money by providing a node, but this too i have to wrap my head around still...
05:05 < whysthatso> anyway, i'm just happy at the moment that i didn't really loose my funds, and at the same time angry that i risked so much....
05:18 < molz> are you selling phone minutes or stickers or tshirts or.. ? otherwise there's no money to make by just having a node, your 0.9 btc might be worth a million USD one day, but it can be lost on LN if you want to lose it, that's fine with me :D
05:27 -!- nibbier [~quassel@2a01:4f8:190:34f0::2] has joined #lnd     
05:30 < tuxx> roasbeef: are you using some internal travis to build lightning-app? would it be possible to submit a patch to build it for arm (raspberrypi) as well?
05:31 < tuxx> i believe lnd has arm64le builds
05:32 < tuxx> by that i mean, i would volunteer to submit a pullrequest to build on arm...
05:32 < tuxx> just not quite sure how i would test it
05:33 < molz> tuxx, you can build the app on your laptop
05:35 < tuxx> molz: you mean cross-compile it?
05:35 < tuxx> never crosscompiled go-arm.. might be doable
05:36 < molz> hm is it very much like building for linux?
05:37 < tuxx> molz: huh? its a different hardware architecture.. your laptop is likily x86-64 while the raspbarrypi is arm64le
05:37 < molz> tuxx, here's the guide to build for linux LL app:  https://hastebin.com/raw/racaqukivi
05:37 < tuxx> i know how to build it
05:37 < tuxx> i'm talking about building it for another architecture
05:40 < tuxx> https://github.com/lightninglabs/lightning-app/blob/master/assets/script/install_lnd.sh <- this file for example downloads the go compiler for amd64 its hardcoded in line 12
05:40 < tuxx> that would need to be a parameter so you can build it for arm for example
05:40 < tuxx> (talking about the release builds which are done in tavis)
05:41 < tuxx> the thing is, i can build my own arm version of lightning-app but i wont get updates
05:41 -!- lnostdal [~lnostdal@151.251.252.53] has quit [Ping timeout: 246 seconds]     
05:41 < tuxx> and wld have to build it myself each time.. would be cool if we cld just integrate it in tavis and always drop an arm version as well
05:45 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]     
05:46 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd     
05:57 < molz> tuxx, the general guide to build the app is here: https://github.com/lightninglabs/lightning-app
06:00 < molz> the app is still in alpha.. so combining the app + raspis ====> double catastrophic failures on mainnet.. not sure how that can be good for LND reputation?
06:01 < tuxx> i use it for sub-dollar amounts
06:02 < tuxx> if i lose a few cents i'll survive
06:02 < tuxx> molz: also in regards to building the app.. nothing beats .tavis.yml or .gitlab-ci.yml those are *actual* buildscripts
06:03 < tuxx> the documentation may be lacking or error prone.. unlike the actual build script 
06:13 < molz> tuxx, you want the app to run on a pi because you want the gui?
06:13 < molz> without the GUI you don't need the app, you can run lnd on neutrino right now
06:13 < molz> it's just not recommended but i know some people are doing it
06:14 < tuxx> molz: yea i want to gui
06:15 < tuxx> i have an lcd attached and i want to start xorg with "exec ./Lightning-app.AppImage &" no window decoration nothing.. just the fullscreen ui
06:18 < molz> have you tried the linux version on your pi?
06:23 < tuxx> molz: are you kidding me?
06:24 < tuxx> arm != x86
06:24 < tuxx> please read up on what hardware architectures are
06:37 < whysthatso> okay, so lnd has finished filtering the blockchain, and i have this output on lncli  listchaintxns shows three transactions
06:38 < molz> ok apology i'm ignorant on burnt pies
06:38 < molz> glad i've never wasted money on them
06:38 < whysthatso> channelbalance shows     "pending_open_balance": "7332270"
06:38 < molz> whysthatso, you have two channels, correct?
06:39 < whysthatso> so it seems, how would i confirm that?
06:39 < molz> i can see on smartbit
06:39 < molz> learn to trace your txs
06:40 < molz> bitcoin is not anonymous, your onchain txs are public for the world to see
06:40 < whysthatso> yeah, i can confirm those, i meant to ask how i can confirm if these are going to channels?
06:40 < whysthatso> i am aware of that, again, i'm trying to understand the functionality of the actual lnd
06:40 < whysthatso> as in, these transactions are what exactly?
06:41 < whysthatso> are these 'open channels
06:41 < whysthatso> ?     
06:41 < molz> do this: lncli listchannels
06:41 < whysthatso> that's an empty there
06:42 < molz> hm is your lnd node 'synced to chain: true' ?
06:42 < whysthatso> yes     
06:42 < whysthatso> "num_pending_channels": 2,
06:42 < molz> and this is the original .lnd datadir?
06:42 < molz> ah     
06:42 < whysthatso> yep     
06:42 < molz> do this: lncli pendingchannels 
06:43 < molz> is it opening pending or closing pending?
06:43 < whysthatso> yep, there's a bunch of stuff in here
06:43 < whysthatso> pending_open_channels
06:44 < whysthatso> so what does that particular info mean?
06:44 < molz> so those channels are under 'pending open'?
06:45 < whysthatso> yes     
06:45 < molz> not sure why, they've had 9000+ confirmations
06:47 < whysthatso> so what are these?
06:47 < whysthatso> and how do i close those?
06:58 -!- nibbier_ [~quassel@mx01.geekbox.info] has joined #lnd     
06:59 -!- Ed0 [~edouard@2001:41d0:401:3100::4897] has quit [Quit: WeeChat 1.0.1]     
07:08 -!- nibbier_ [~quassel@mx01.geekbox.info] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]     
07:08 -!- nibbier_ [~quassel@mx01.geekbox.info] has joined #lnd     
07:10 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd     
07:10 -!- nibbier [~quassel@2a01:4f8:190:34f0::2] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]     
07:11 < molz> lncli closechannel -h
07:13 < whysthatso> what's the funding_txid
07:16 -!- MaxSan [~four@91.214.169.69] has joined #lnd     
07:17 < whysthatso> ah is that the transaction id of the funds going out of the lnd wallet?
07:18 < whysthatso> the tx_hash that lncli listchaintxns  shows me?
07:25 -!- libertyprime [~libertypr@101.98.42.91] has quit [Remote host closed the connection]     
07:25 < whysthatso> nevermind
07:25 < whysthatso> i found it
07:25 < whysthatso> it's part of the channel_point
07:34 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has quit [Ping timeout: 246 seconds]     
07:35 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has joined #lnd     
07:41 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
07:43 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 268 seconds]     
08:26 -!- lnostdal [~lnostdal@87.97.154.160] has joined #lnd     
08:30 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd     
08:45 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
08:48 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
08:52 < queip> how should one run own server and instruct his and his friend's LND nodes to connect to it?
08:53 < queip> I know how to run own Bitcoin Core. What else is needed?  The reason for using own server is to increase security and privacy of such LND spv clients.
08:53 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
08:53 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
09:01 < waxwing> queip, iirc you will have to specifically allow connections to bitcoind with rpcallowip in config (the rules got a bit stricter recently). and you need the zmq ports as well as the rpc port (but that's covered in docs right). i think maybe you can go over Tor HS? (not sure about that, it's definitely possible using a tunnelling approach but that's a bit hairy)
09:02 < waxwing> (but 'lnd spv'? this wouldn't be spv, this is just a remote node)
09:09 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:409d:340:890d:742c] has joined #lnd     
09:21 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:409d:340:890d:742c] has quit [Quit: Sleep mode]     
09:24 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 255 seconds]     
09:24 -!- StopAndDecrypt [~StopAndDe@129.232.161.114] has joined #lnd     
09:24 -!- StopAndDecrypt [~StopAndDe@129.232.161.114] has quit [Changing host]     
09:24 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd     
09:31 < tuxx> /home/alarm/go/pkg/tool/linux_arm64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory
09:31 < tuxx> i hate the RPi
09:31 < tuxx> qemu it is i guess :/
09:36 < queip> waxwing: is such use not insecure for the node then? can't LND do what ever rpc calls?
09:36 < queip> there are several "public" "spv or something" nodes to which LND can connect right? neutrino?
09:36 < queip> I wanted to learn how to run such a "public" server, to be used by light LND nodes (by users who do not have own bitcoin core)
09:39 < waxwing> i'm not sure, i don't think such a functionality was ever intended ... i'm trying to remember exactly what lnd does, i think it just subscribes to blocks and transactions over zmq, but i think it also uses the rpc (it'd need it for fee estimates, for a start)
09:39 < waxwing> queip, ^
09:40 < queip> but LND has this mode... neutrino? where you do not run local bitcoind and LND still works by using some public service
09:40 < queip> this mode was added not so long ago I think
09:41 < waxwing> ah neutrino, right, yeah that's different. sorry i should have realised you were talking about that.
09:41 -!- lnostdal [~lnostdal@87.97.154.160] has quit [Ping timeout: 246 seconds]     
09:42 < waxwing> yeah because that's not in bitcoin core yet, but i think you can set up your Core node to that yourself, but it may only be a PR as of now? someone here should know about that.
09:52 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Quit: Leaving]     
09:54 < tuxx> hah crosscompiling go is so easy :)
09:59 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 244 seconds]     
10:02 < queip> so I guess, bitcoin-core <---- ???some program??? <----- neutrino protocol ---- LND
10:02 < queip> what is the ??? program and with options to run it, bitcoind is on localhost, let's say I have public IP (what port to open?)   
10:05 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd     
10:06 < lndbot> <alexbosworth> You can run btcd which will offer Neutrino on the normal Bitcoin p2p protocol port
10:10 < queip> btcd can connect into bitcoind or is it bitcoind replacement?
10:10 < queip> also, isn't btcd old not not too supported? wasnt there a better option
10:13 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd     
10:15 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
10:15 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
10:16 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
10:17 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
10:17 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 258 seconds]     
10:22 < molz> btcd is the root of neutrino if you want to run neutrino, do some reading
10:23 < molz> btw and neutrino is not ready for mainnet 
10:28 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd     
10:35 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd     
10:43 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
10:45 < tuxx> can someone tell me why lnd doesnt create a "admin.macaroon" file when i started as follows "./lnd --bitcoin.active --routing.assumechanvalid --historicalsyncinterval=20m --autopilot.private --bitcoin.mainnet --bitcoin.node=neutrino --neutrino.connect=165.227.7.29 --neutrino.connect=dev.conner.money --neutrino.feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json"
10:46 < tuxx> its fully synced
10:46 < tuxx> built against version: "git fetch https://github.com/halseth/lnd.git mainnet-neutrino && git cherry-pick d1c23009e00298ed50173fb7cd60bdfb2937d50f"
10:48 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
10:51 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
10:51 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
10:56 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 252 seconds]     
10:56 -!- Asara [asara@unaffiliated/asara] has quit [Ping timeout: 246 seconds]     
10:56 < tuxx> ok forget what i said.. 
11:24 -!- sfhi [~sfhi@178.255.154.106] has joined #lnd     
11:37 -!- whysthatso [5abef909@gateway/web/freenode/ip.90.190.249.9] has quit [Ping timeout: 256 seconds]     
11:55 -!- lnostdal [~lnostdal@151.251.240.131] has joined #lnd     
11:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]     
12:10 < Talkless> https://paste.debian.net/1081781/ what's these "rawtx message: frame too large" ?
12:10 < Talkless> my bitcoind is catching up after unexpeted downtime
12:53 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!]     
13:07 -!- sfhi [~sfhi@178.255.154.106] has quit [Quit: Leaving]     
13:57 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 276 seconds]     
14:11 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
14:46 -!- Djey [~Djey@86.217.218.223] has joined #lnd     
14:47 -!- Djey [~Djey@86.217.218.223] has quit [Client Quit]     
14:48 -!- Djey [~Djey@86.217.218.223] has joined #lnd     
14:48 -!- Djey [~Djey@86.217.218.223] has quit [Client Quit]     
14:56 < bitconner> queip, currently i think only btcd and bcoin have neutrino serving support in master. in btcd, the option is enabled using cfindex=1
14:58 -!- StopAndDecrypt_ [~StopAndDe@129.232.161.114] has joined #lnd     
14:58 < bitconner> hmm, actually i'm unsure if it is in bcoin master, maybe someone who knows can correct em
14:58 < bitconner> me*     
14:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds]     
15:03 < NeonLicht> Hello.  I'm running the lightning wallet which, as I understand, runs a lnd itself.  How can I figure out what my node URL is so that I can connect to it from other wallets in my phone and tablet, please?
15:04 < lndbot> <alexbosworth> If you make an invoice and plug it into https://lndecode.com/ it should show you the pubkey
15:05 < bitconner> NeonLicht, you may not have a URI if port forwarding isn't enabled fwiw
15:06 < bitconner> the connections from the lightning-app will all be outbound unless there is some other manual configuration
15:21 -!- libertyprime [~libertypr@203.86.194.68] has joined #lnd     
15:53 -!- Asara [asara@unaffiliated/asara] has joined #lnd     
15:55 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd     
15:59 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 246 seconds]     
16:14 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
16:16 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]     
16:23 < tuxx> http://95.179.133.230/
16:24 < tuxx> sweet its almost done
16:24 -!- molz [~molly@unaffiliated/molly] has joined #lnd     
16:25 < tuxx> molz: http://95.179.133.230/
16:25 < molz> ?     
16:25 < tuxx> hit "feed"
16:25 < molz> sorry no
16:26 < tuxx> lol.... ok?
16:26 < tuxx> its basically pollofeed.com
16:26 < molz> busy
16:26 < tuxx> u can run a servo by paying lightning
16:26 < bitconner> no https
16:26 < tuxx> but i trigger on invoice creations for now... not payments
16:27 < tuxx> bitconner no domain either :p
16:27 < lndbot> <alexbosworth> node not in my graph
16:27 < tuxx> ye its not funded
16:27 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
16:28 < tuxx> ill up the source to github now
16:28 < tuxx> i offload the video streaming to twitch
16:32 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:81fb:c7fe:205c:8140] has joined #lnd     
16:33 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 246 seconds]     
16:41 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:81fb:c7fe:205c:8140] has quit [Ping timeout: 258 seconds]     
17:00 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:04 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 258 seconds]     
17:25 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:29 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 252 seconds]     
17:32 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:32 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
17:32 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:34 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
17:38 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:38 < NeonLicht> What do you mean bt "fwiw", bitconner?
17:39 < bitconner> NeonLicht, for what it's worth :)
17:39 < bitconner> jk     
17:39 < bitconner> if you're running the app on your phone for example, you may not have a public port
17:40 < bitconner> if you're running desktop, you'd probably need to configure your router to give you one
17:40 < NeonLicht> Ah, OK, I thought it had something to do with the port forwarding.  What is supposed to do the port forwarding?  A firewall?  The lightning wallet?
17:40 < bitconner> you could try giving the nat options a shot if you start lnd with the nat flags, but you're router would need to support nat traversal
17:41 < NeonLicht> The problem is that I do not start lnd, the lightning wallet does it.
17:41 < bitconner> on desktop you can start the app manually via the command line
17:41 < bitconner> and pass in additional flags
17:42 < NeonLicht> I can't find the lnd executable file.  The wallet runs it automatically.  If tried finding it with "locate" and "find" and have failed.
17:42 < bitconner> https://github.com/lightninglabs/lightning-app#starting-the-packaged-app-light-client
17:43 < bitconner> the paths are for osx, so i'm not positive where they are on your desktop
17:44 -!- lnostdal [~lnostdal@151.251.240.131] has quit [Ping timeout: 255 seconds]     
17:44 < NeonLicht> So, am I supposed to first start lnd and then somehow instruct the wallet to connect to it and not launch it?
17:44 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 255 seconds]     
17:45 < bitconner> the app will pass through additional flags to lnd
17:45 < bitconner> it starts both
17:45 < NeonLicht> The app?   The app is a third thing appart form lnd and the wallet?
17:45 < NeonLicht> It's so confusing.
17:46 < bitconner> lightning wallet is the name of the app
17:47 < NeonLicht> So, I am *not* supposed to first start lnd and then somehow instruct the wallet to connect to it and not launch it?
17:47 < bitconner> did you look at the link i sent?
17:47 < NeonLicht> Of course, I'm trying to decifer it.
17:47 < bitconner> it *only* starts the app, but passes in lnd args, which get passed onto lnd as it starts
17:49 < NeonLicht> Perhaps the app is the file Lightning-linux-x86_64v0.5.1-alpha.AppImage?  that's what I lauch myself.
17:49 < bitconner> correct, there should be a binary deeper in the package structure
17:50 < NeonLicht> A binary different than "the app"?
17:50 < bitconner> yes, the lnd binary is spawned as a child process. the app communicates with it via rpc
17:51 < NeonLicht> So, am I supposed to first start lnd and then somehow instruct the wallet to connect to it and not launch it?
17:51 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
17:51 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd     
17:51 < NeonLicht> I've been looking for a lnd binary for days, and I can't find it.
17:51 < bitconner> sorry i think i see the confusion now
17:52 < bitconner> in the link i sent, ./dist/mac/Lightning.app is what would normally be displayed in the UI as an icon to double click and start
17:52 < bitconner> the actual application binary that gets run is inside the .app folder
17:52 < NeonLicht> That wold be Lightning-linux-x86_64v0.5.1-alpha.AppImage, I guess.  I don't use icons.
17:53 < bitconner> i'm not sure how the AppImage is structured, but i'd expect there to be a similar application binary packaged up inside
17:53 < bitconner> could always try passing the args directly to the AppImage and see if it works :P
17:53 < NeonLicht> By inside, do you mean inside the .AppImage or  inside of some directory tree it creates when run?
17:54 < NeonLicht> Am I supposed to somehow decompress the .AppImage instead of run it?
17:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd     
17:55 < bitconner> asked our resident linux expert, thinks you can pass the args directly to AppImage
17:56 < NeonLicht> I see, great.  Now I'd need to know what arguments I need to pass to be able to have a URL to connect to, I guess?
17:56 < NeonLicht> Because the arguments on the link you gave me are for testnet and neutrino.   I'm running on mainnet.
17:56 < molz> lol     
17:57 < bitconner> if you start the app as normal and use ps aux | grep lnd, it might give you more insight about how everything is structured
17:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]     
17:58 < bitconner> but yeah, if you set up port forwarding on your router for, say, port 9735, then pass -externalip=<your-ip>:9735
17:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd     
17:58 < NeonLicht> I've been looking at ps aux | grep lnd for days now, to try to figure out what the URL to connect to my node might be,
17:58 < bitconner> otherwise, may need resort to -nat flag, which may not work with your router
17:59 < valwal_> NeonLicht: are you trying to connect to your node to use `lncli` with it? 
18:00 < valwal_> note that the app runs its lnd node on port `10006`
18:00 < NeonLicht> No, valwal_, I'm trying to find out what my node URL is.
18:00 < valwal_> it's just localhost
18:00 < NeonLicht> Yes, valwal_, I know it runs on port 10006.
18:00 < bitconner> NeonLicht, you don't have one, unless you set up port forwarding
18:01 < valwal_> did you try adding the `--rpclisten=0.0.0.0` flag?
18:01 < bitconner> like valwal_ said, the app only listens on localhost, so would also need to pass -listen:0.0.0.0:9735
18:01 < NeonLicht> I don't have a router, bitconner.  How can I instruct LND to listen for connections?
18:01 < NeonLicht> Ok, bitconner, I'll try that.
18:01 < bitconner> how are you connecting to the internet
18:03 < molz> bitconner, via satellite ofc 
18:03 < NeonLicht> Ok, I've run it with "-listen:0.0.0.0:9735" now.  How can I figure out what the node URL is?
18:04 < bitconner> molz, lolol
18:04 < bitconner> NeonLicht, i don't know, it depends on how you are connecting to the interwebz
18:05 < NeonLicht> I'm connected directly, with a real IP, with no router, no nat, nothing in between.
18:07 < bitconner> if that's true, then -externalip=<real IP>:9735 should be all you need
18:09 < NeonLicht> Of course it's true.  I'd be retarded if I was asking for help to find out the node URL and lied about that.
18:09 < valwal_> lol     
18:09 < bitconner> sweet
18:10 < NeonLicht> I'm running now with -externalip=<real IP>:9735.   I've seen node URLs are like a kind of hash followed by the IP  and then the port.  How could I find out what that kind of hash is in my node?
18:10 < bitconner> then your URI will just be <pubkey>@<real IP>:9735, if you extract the pubkey via what alexbosworth said
18:10 <@roasbeef> valwal_: you have a tail, assert your claim to your name 
18:10 < molz> lol     
18:10 < NeonLicht> Oh, pubkey, OK.  How can I find out what the pubkey is?
18:10 < molz> hey valwal_ :D
18:11 < valwal_> heyaaaa
18:11 < molz> didn't recognize you till now :P
18:11 < valwal_> lol i'm a lurker :p
18:11 < valwal_> NeonLicht: `lncli getinfo` 
18:12 < bitconner> will need the --rpcserver=localhost:10006 and --macaroonpath=/not/totally/sure/where/this/would/be
18:13 < NeonLicht> Good, valwal_, and where is the lncli binary?  Am I supposed to uncompress the appImage or something?
18:13 <@roasbeef> you'd need to compile it yourself 
18:13 < valwal_> or rather than macaroonpath, can just do `--lnddir=~/.config/lightning-app/lnd` 
18:13 <@roasbeef> it isn't package with the app 
18:13 < bitconner> NeonLicht, make an invoice, and paste it here: https://lndecode.com/
18:13 < bitconner> it will recover the pubkey from the signed invoice
18:14 < NeonLicht> Ah, great, bitconner, I dind't think about the decoder!!!
18:15 < NeonLicht> I don't see a pubkey field there, though.
18:15 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has quit [Ping timeout: 248 seconds]     
18:16 < bitconner> cmd+f "
18:16 < bitconner> Public Key"
18:16 < NeonLicht> https://lightningdecoder.com/    does it
18:16 < bitconner> i just tired it, it works
18:17 < NeonLicht> What works?
18:17 < bitconner> cmd+f
18:18 < NeonLicht> I don't know what cmd+f means, sorry.
18:24 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has joined #lnd     
18:25 < NeonLicht> I tried to open a channel to my node and it timed out.
18:25 < lndbot> <alexbosworth> Maybe a networking issue
18:26 <@roasbeef> i'd try just making sure you can reach it 
18:26 <@roasbeef> via something like ping or netcat 
18:27 < NeonLicht> I'm not sure the "externalip" has done anything.  Should it show up in px aux | grep lnd?
18:27 < valwal_> yes     
18:27 < NeonLicht> Can reach the server, roasbeef?  I can.  I'm just not sure the node is listening.
18:31 < NeonLicht> It does not.
18:32 <@roasbeef> try on that poart
18:32 <@roasbeef> port* 
18:32 <@roasbeef> so TCP dial to the target port it's listening on 
18:33 < NeonLicht> Try what?
18:35 < NeonLicht> Tried again and now it says connection failed immediately, no time out.
18:35 < NeonLicht> I don't think it's listening on port 9735 at all.
18:36 < bitconner> NeonLicht, you have both listen and externalip?
18:37 < NeonLicht> No, bitconner, I only have externalip.
18:38 < bitconner> set both
18:38 < NeonLicht> Set both.  Same thing.  Connection failed.
18:38 <@roasbeef> if it isn't listening on 9715 externally, then you maybe need to modify your router to forward it to your computer/node 
18:39 < NeonLicht> I still can't see any of them on    ps aux | grep lnd
18:39 <@roasbeef> that's just the process args 
18:39 <@roasbeef> if you're setting it in the config, then it won't show up yet 
18:39 < NeonLicht> I have no router, roasbeef.  I'm connected with a real IP.
18:40 < NeonLicht> The config, roasbeef?  Where can I find the config?  I'm trying to pass them trhough the command line, but it doesn't seem to work.
18:40 < NeonLicht> Thins app.Image thing is a nightmare.   :(
18:43 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
18:49 < NeonLicht> Are arguments given to the AppImage on the cli supossed to reach the lnd?  I tried one dash and two dashes (-externalip and --exrernalip) and none of them show up when I do   ps aux | grep lnd
18:50 <@roasbeef> the app image isn't what's run 
18:50 <@roasbeef> there's a binary of lnd that's packaged 
18:51 < NeonLicht> Where is such a binary?  is it inside the AppImage?  Do I need to umcompress it somehow?
18:51 < NeonLicht> Where is it "packaged"?  How do I unpackage it?
18:51 < bitconner> NeonLicht, i'd suggest making an issue
18:52 < molz> roasbeef, so the goal of the app is for users who don't want to deal with URI, channels, etc.. but they still seek for those things.. maybe reconsider?
18:52 < NeonLicht> That's what somebody suggested me when I tried the deb package and couldn't make it work....  and there, in the issue, they told me to forget the debian package and use this AppImage thing.  LOL
18:54 < NeonLicht> Oh, the AppImage thing is supposed to be to not open channels manualy?  I'd rather use any normal software than this AppImage, but they told me to use it because the debian package is broken and they don't know how to fix it, apparently.
18:56 < NeonLicht> I guess the only real option is to install bitcoind and lnd myself?  I just wanted to try out with precompiled binaries before, to try to understand it before compiling and everything.
18:57 < bitconner> there are lnd and lncli binaries on the release page, you would have to install bitcoind tho
18:58 < NeonLicht> Oh, really?  I haven't been able to find those.
18:58 < NeonLicht> Won't they work with neutrino line the AppImage?
19:00 < NeonLicht> I'm on https://github.com/lightningnetwork/lnd.   Where can I find those binaries?
19:00 < bitconner> "releases"
19:02 < NeonLicht> Ah, that's wonderful!!!  So many OS!
19:02 < NeonLicht> Even OpenBSD!! :)
19:03 < bitconner> yep! go can be cross-compiled to any os/arch combo from one machine
19:03 < NeonLicht> I've been looking for this for months.
19:05 < NeonLicht> Ah! Great, lnd and lncli!! Finally!
19:07 < NeonLicht> Oh, it's wonderful, I can configure in on ~/.lnd/lnd.conf
19:08 < NeonLicht> Now a config file example would be great.  :)
19:09 < NeonLicht> Ah, found it! LOL
19:12 < NeonLicht> $ lnd
19:12 < NeonLicht>  loadConfig: neutrino isn't yet supported for bitcoin's mainnet
19:12 < NeonLicht> I though the AppImage used neutrino.  Am I wrong?
19:13 < bitconner> binaries will require a full-node backend, as mentioned before
19:15 < NeonLicht> Ah, OK, I couldn't understand it when you said, the way you said it with the little information I had. Sorry.
19:15 < NeonLicht> It runs on testnet, though!
19:28 -!- Kostenko [~Kostenko@dsl-154-81.bl26.telepac.pt] has quit [Remote host closed the connection]     
19:36 < NeonLicht> Thank you very much for helping me out finding those binaries.
19:36 < NeonLicht> Is there also a binary for the ligthning wallet for Linux appart from the AppImage, please?
19:58 -!- drexl [~drexl@188.166.71.168] has quit [Quit: drexl]     
20:06 -!- MaxSan [~four@91.214.169.69] has quit [Quit: Leaving.]     
20:18 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection]     
20:18 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
20:23 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 255 seconds]     
20:26 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Quit: ZNC 1.7.2+deb1+xenial2 - https://znc.in]     
20:27 -!- achow101 [~achow101@unaffiliated/achow101] has joined #lnd     
20:56 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Remote host closed the connection]     
21:00 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
21:02 -!- MaxSan [~four@91.214.169.69] has joined #lnd     
21:18 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 244 seconds]     
21:19 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
21:23 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 252 seconds]     
21:28 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
21:30 -!- libertyprime [~libertypr@203.86.194.68] has quit [Remote host closed the connection]     
21:50 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 246 seconds]     
21:51 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
22:08 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 244 seconds]     
22:09 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
22:14 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 268 seconds]     
22:18 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
22:33 -!- MaxSan [~four@91.214.169.69] has quit [Ping timeout: 255 seconds]     
22:34 -!- MaxSan [~four@91.214.169.69] has joined #lnd     
22:36 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 245 seconds]     
22:37 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
22:44 -!- MaxSan [~four@91.214.169.69] has quit [Quit: Leaving.]     
22:53 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Read error: Connection timed out]     
22:59 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
23:08 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 248 seconds]     
23:09 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
23:26 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 246 seconds]     
23:27 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd     
23:31 -!- scoop [~scoop@205.178.77.52] has joined #lnd     
23:31 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]     
23:31 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 258 seconds]     
23:35 -!- scoop [~scoop@205.178.77.52] has quit [Ping timeout: 246 seconds]     
23:45 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has quit [Ping timeout: 244 seconds]     
23:50 -!- ccdle12 [~ccdle12@1-64-37-052.static.netvigator.com] has joined #lnd