--- Day changed Tue Aug 22 2017 00:06 -!- JackH [~laptop@46.231.18.66] has joined #lnd 01:00 -github-lnd:#lnd- [lnd] Roasbeef pushed 62 new commits to master: https://git.io/v5Ups 01:00 -github-lnd:#lnd- lnd/master 804edb8 Olaoluwa Osuntokun: autopilot: ensure all access to pendingOpens is thread-safe... 01:00 -github-lnd:#lnd- lnd/master a8576ea Olaoluwa Osuntokun: autopilot: fix bug in skip nodes test, use new instance for each run 01:00 -github-lnd:#lnd- lnd/master 77e3e74 Olaoluwa Osuntokun: autopilot: for ConstrainedPrefAttachment.Select factor in skipNodes... 01:00 <@roasbeef> ^ super duper breaking changes 01:01 <@roasbeef> the last of the planned ones though :) 01:02 <@roasbeef> high lights: switch to spec port, use mSAT internally for accounting, allow uers to generate fee reports, allow users to set fees globally or per-channel, buncha spec related fixes, some bug fixes, some autopilot bug fixes, path finding fee fix, macaroon related fixes 01:06 -github-lnd:#lnd- [lnd] Roasbeef pushed 1 new commit to master: https://git.io/v5UpX 01:06 -github-lnd:#lnd- lnd/master 90a0395 Olaoluwa Osuntokun: htlcswitch: fix linter errors 01:09 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 248 seconds] 01:15 <@roasbeef> upgrading to this latest versino will require y'all to close all channels 01:15 <@roasbeef> also the port has changed 01:15 <@roasbeef> and ther're two new RPC's you'll find in lncli, no breaking changes on the RPC sid 01:15 <@roasbeef> other than the fact that we now enforce the limit on the max payment size 01:16 <@roasbeef> we may consider exposing mSAT payment amounts on the RPC interface, but will wait to a later time to make that decision 01:16 < lndbot1> Dopee 01:16 <@roasbeef> will do a bit more testing, then start on release notes 01:17 <@roasbeef> have a few follow up blog posts we'll be making as this releae is pretty jam packed, and sets the stage for th next release: 0.4-beta 01:17 <@roasbeef> 0.3.1 is planned before then (at the very least), will fill in some missing pieces, and either add the bitcoind backend in that or 0.3.2 01:18 <@roasbeef> ahh, I should update the README as well 01:18 <@roasbeef> it's pretty old at this point 01:22 < JackH> you released it? 01:24 <@roasbeef> 0.3-alpha? not yet 01:24 <@roasbeef> but keep in mind, we won't recommend using it with real funds yet 01:24 <@roasbeef> even in that case, it's wise to wait a few weeks before using the new segwit features on mainchain 01:26 < JackH> you know its not like that ;) the game is on in about 16h 01:26 < JackH> will 0.3 alpha make it before that? 01:26 <@roasbeef> heh 01:36 < lndbot1> Do you want to lose money, because that's how you lose money lol? 02:22 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 02:24 -!- HeySteve [~0000@unaffiliated/heysteve] has quit [Ping timeout: 240 seconds] 02:39 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has joined #lnd 02:41 < kermie> I tried my luck in #lightning-dev but I'll try it here also. I asked a question on Reddit and was wondering if people here could give me more information. Can I share a Reddit link? 02:43 < cdecker> roasbeef, we seem to disagree on the endianness of the chain hash 02:43 < cdecker> DEBUG:root:lnd: 2017-08-22 11:26:18.276 [ERR] FNDG: Unable to initialize reservation: unable to create channel reservation for chain=06226e46111a0b59caaf126043eb5bbf28c34f3a5e332a1fc7b2b73cf188910f, wallet is on chain=0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206 02:47 < cdecker> lnd's is in line with bitcon-cli (little endian), while Eclair and c-lightning use big endian which most hashing tools spit out, but looks strange with trailing 0s 02:50 <@roasbeef> cdecker: ahh, yeh we use little endian like bitcoin daemons do 02:50 < cdecker> I don't know which one of us is wrong tbh 02:50 <@roasbeef> the spec doesn't expliclty say which byte ordering to use, so i'll make a pr for that 02:51 <@roasbeef> i'd say bitcoin-cli is right ;) 02:51 < cdecker> Spec says big endian for everything, but in this case I tend to prefer consistency with bitcoin 02:51 <@roasbeef> mhmm 02:51 < cdecker> I knew you'd say that 02:51 < cdecker> :D 02:51 <@roasbeef> kek 02:51 < cdecker> Thanks for the update btw 02:52 <@roasbeef> have you re-tried the gossip message case? 02:52 * roasbeef clones le repo 02:52 < cdecker> Will do now, was hanging at the openchannel testcase 02:53 <@roasbeef> gotcha 02:53 <@roasbeef> one thing we had, but removed was adding an error code field to the error message itself, so was easy to programatically respond to errors 02:53 <@roasbeef> who did y'all handle that error message sent? 02:53 <@roasbeef> how* 02:54 < cdecker> Uff, not sure, will check 02:54 <@roasbeef> actually nvm, we have the channel_id there now (so would at least know which attempted channel funding fails) 02:54 <@roasbeef> but we use an error code in the first byte to print nicer errors on the command line 02:54 <@roasbeef> 2 bytes* 02:55 < cdecker> I don't seem to get any error if lnd decides it can't open a channel with the above logs 02:55 < cdecker> Uh oh, test.py::testgossip[EclairNode_LndNode] FAILED 02:56 <@roasbeef> due to the mismatch in what the chain hash is again? 02:56 <@roasbeef> could cause us to be signing diff digests 02:57 <@roasbeef> ah but the test depends on openchannel working looks like, so should resolve that first 02:57 <@roasbeef> kermie: what's your q? 03:00 < kermie> Ah hi roasbeef ... well I'm just starting setting up a network. I understand the general concepts of the lightning network. And have a basic technical understanding of bitcoin. 03:01 < cdecker> Nope, testgossip creates a 5 node network using lightningd (those open channels) but then only connect (without opening channels) from the clients under test 03:01 < kermie> I started out with btcd + lnd 03:01 <@roasbeef> cdecker: ahh ok 03:01 < cdecker> Loads of failed connections though, so will need to investigate there 03:02 < kermie> But got stuck because I didn't know the difference between testnet + simnet / regtest. 03:02 <@roasbeef> kermie: testnet is the main bitcoin test network, many other devs+companies use it 03:02 < kermie> Then I remembered a Medium article by @btc_coach on Eclair so tried to follow that. 03:03 <@roasbeef> kermie: regtest was originally created for regression tests within bitcoind, let's you maek blocks easily 03:03 < kermie> Yeah I know testnet, just wasn't familiar with simnet / regtest ... 03:03 <@roasbeef> simnet is like regtest, but...better :D 03:03 <@roasbeef> simnet does difficulty retargets past the first period 03:03 < kermie> I used bitcoind + Eclair+UI .. but the article didn't specify the bitcoind commands so I had to figure those out 03:04 < kermie> then I realized that I had not idea how to properly fund a channel ... despite it looking so simple in the article 03:04 <@roasbeef> kermie: so you're trying to connect lnd and eclair? 03:04 < kermie> So now I'm rethinking whether I should invest my time in Eclair and perhaps use bitcoind + c-lightning (lightningd) 03:05 < kermie> So currently I'm figuring out how to start that after having my bitcoind running in regtest 03:05 <@roasbeef> both eclair and c-lightning use bitcoind 03:05 < kermie> yes 03:06 < kermie> So I have a script for bitcoind that I think should create 4 funded addresses... one to represent each of the 4 nodes that I want to setup on my local machine (but later re-create on 4 servers) 03:06 < kermie> but the script doesn't seem to work properly 03:06 < cdecker> roasbeef, seems we serialize pubkeys differently as well? 03:06 <@roasbeef> kermie: 4 funded addresses as in channels? 03:06 < cdecker> PEER: unable to read message from 127.0.0.1:16332: invalid magic in compressed pubkey string: 31 03:06 <@roasbeef> cdecker: we always use compressed 03:07 < cdecker> Same here, the wire format actually dictates compressed 03:07 <@roasbeef> which message? 03:08 < kermie> roasbeef: 4 addresses ... one for each not to fund their own channels 03:08 < kermie> *each node 03:08 < cdecker> Good Q, my guess is a channel_announcement, need to instrument 03:08 < kermie> I can paste a link to the regtest script if you don't mind on Paste.ee 03:11 -!- HeySteve [~0000@unaffiliated/heysteve] has joined #lnd 03:14 < kermie> I'm trying to figure out which of the three main BOLT implementations is most mature, suitable and stable for somebody to experiment with. Eclair, lnd or c-lightning -- although I'm not sure that I'm in a neutral channel for that. I've tried Eclair which has a nice UI, but not necessary for my server test and running on JVM, I'm guessing doesn't optimize system resources as well as c++ and Go implementations. 03:15 < kermie> lnd has a lot of documentation but depends on btcd which doesn't seem as efficient and mature and well documented (with community support) as bitcoind 03:16 < kermie> c-lightning (with lightningd) just seems straightforward. Clone repo, $ make and then run lightningd -- then use lightning-cli with very similar commands to bitcoin-cli - 03:18 <@roasbeef> kermie: lnd's works with btcd, and also has other backends you can configure. the other mode aside from btcd is neutrino which means you don't neccserily need to have a node locally. the protocol changes (to serve these new clients) haven't made it into other ndoes yet though, so you'll need to find one on testnet 03:19 <@roasbeef> kermie: we have a bitcoind chain backend planned as well 03:20 <@roasbeef> but yeh c-lightning is prob the most light weight atm when it comes to resources (for the daemon itself) 03:28 < cdecker> roasbeef, one of these messages kills the connection: https://pastebin.com/j5HP7wUj 03:30 <@roasbeef> trying em each out 03:33 < cdecker> My bet is the pubkeys in the channel_announcements ^^ 03:33 <@roasbeef> === RUN TestKek 03:33 <@roasbeef> --- FAIL: TestKek (0.00s) lnwire_test.go:623: can't read: invalid magic in compressed pubkey string: 117 03:33 <@roasbeef> first one ^ 03:33 < cdecker> Yep, that's the error I get as well 03:34 < kermie> I'll try to follow the c-lightning installation instructions first .. thanks for the replies sofar 03:35 < kermie> I might just be confused on how to setup a regtest network to support 4 lightning nodes 03:35 < kermie> I have this now: https://paste.ee/p/KYhI8 03:36 < kermie> Unfortunately I don't end up with what I expected. I thought there'd be 5 addresses, where each would have 10 BTC 03:36 <@roasbeef> kermie: you can probably just make one bitcoind, and connect all the c-lightning instances to that 03:36 < kermie> That's what I'm doing 03:37 < kermie> a single regtest with 4 addresses that can be used by each of the 4 nodes 03:46 -!- riclas [riclas@72.210.189.46.rev.vodafone.pt] has joined #lnd 03:49 <@roasbeef> cdecker: is this for both eclair and c-lightning? 03:49 < cdecker> Well, eclair and c-lightning understand and generate that format, yes ^^ 03:49 < cdecker> (this is originally from c-lightning though) 03:54 -!- roasbeef [~root@104.131.26.124] has quit [Ping timeout: 248 seconds] 03:55 -!- roasbeef [~root@104.131.26.124] has joined #lnd 03:57 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 04:00 -!- dclxvi` [~dclxvi@95-44-201-135-dynamic.agg1.whi.bdt-fng.eircom.net] has joined #lnd 04:00 -!- dclxvi [~dclxvi@95-44-201-135-dynamic.agg1.whi.bdt-fng.eircom.net] has quit [Ping timeout: 248 seconds] 04:01 -!- Sentineo [~Undefined@node.chcembitcoin.sk] has quit [Ping timeout: 248 seconds] 04:01 -!- stevenroose [~steven@vps.weuste.club] has quit [Ping timeout: 248 seconds] 04:02 -!- Zouppen [joell@moskova.liittovaltio.fi] has quit [Ping timeout: 246 seconds] 04:02 -!- Sentineo [~Undefined@node.chcembitcoin.sk] has joined #lnd 04:02 -!- Zouppen [joell@moskova.liittovaltio.fi] has joined #lnd 04:05 -!- stevenroose [~steven@vps.weuste.club] has joined #lnd 04:19 -!- HeySteve [~0000@unaffiliated/heysteve] has quit [Ping timeout: 240 seconds] 04:31 < kermie> I'm using c-lightning (lightningd) and it says in the README "Once bitcoind has synchronized with the testnet/regtest network, you can start lightningd with the following command:" but after starting a regtest network, it looks like lightningd is still trying to connect to -testnet 04:31 < kermie> How do I make sure lightningd uses regtest? 04:39 < cdecker> --network=regtest :-) 04:39 < cdecker> We might want to move to #lightning-dev for general discussions btw :-) 05:16 < cdecker> roasbeef, please disregard the second gossip message I put in the paste, it's missing the chain_hash from the recent BOLT update 05:16 < cdecker> Once we agree on node_announcement I'll generate new messages and see if they work 07:36 -!- HeySteve [~0000@unaffiliated/heysteve] has joined #lnd 07:57 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 07:58 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 08:12 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 08:12 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 08:35 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has quit [Ping timeout: 260 seconds] 08:45 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #lnd 09:06 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 09:09 -!- Sentineo|mobile [~androirc@217.12.53.71] has joined #lnd 09:13 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 09:16 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 09:16 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has quit [Quit: Leaving] 09:25 -!- MaxSan [~one@95.215.62.92] has joined #lnd 09:25 -!- MaxSan [~one@95.215.62.92] has quit [Max SendQ exceeded] 09:26 -!- MaxSan [~one@95.215.62.92] has joined #lnd 09:26 -!- MaxSan [~one@95.215.62.92] has quit [Max SendQ exceeded] 09:27 -!- MaxSan [~one@95.215.62.92] has joined #lnd 09:30 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 09:48 -!- JackH [~laptop@46.231.18.66] has quit [Ping timeout: 240 seconds] 09:54 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #lnd 09:56 -!- HeySteve2 [~0000@unaffiliated/heysteve] has joined #lnd 09:58 -!- HeySteve [~0000@unaffiliated/heysteve] has quit [Ping timeout: 260 seconds] 10:08 -!- S [~androirc@217.12.53.71] has joined #lnd 10:09 -!- S is now known as Guest18387 10:11 -!- Guest18387 [~androirc@217.12.53.71] has quit [Client Quit] 10:11 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 10:12 -!- Sentineo|mobile [~androirc@217.12.53.71] has quit [Ping timeout: 248 seconds] 10:14 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [Client Quit] 10:18 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 10:46 -!- MaxSan [~one@95.215.62.92] has quit [Ping timeout: 255 seconds] 11:15 -!- MaxSan [~one@95.215.62.92] has joined #lnd 11:40 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 11:41 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 11:42 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 255 seconds] 11:51 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 11:53 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 11:58 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 12:00 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 12:02 -!- MaxSan [~one@95.215.62.92] has quit [Quit: Leaving.] 12:37 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has joined #lnd 12:40 -!- riclas [riclas@72.210.189.46.rev.vodafone.pt] has quit [] 12:45 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 12:53 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 12:54 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 12:57 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 13:35 -!- dakk [~dakk@dynamic-adsl-78-15-211-7.clienti.tiscali.it] has quit [Ping timeout: 240 seconds] 13:35 -!- dakk [~dakk@dynamic-adsl-78-15-237-78.clienti.tiscali.it] has joined #lnd 13:37 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 13:52 -!- alt0id [~jacks@pulsar.1337.cx] has joined #lnd 13:52 < alt0id> HELP! 13:52 < alt0id> https://github.com/elementsproject/lightning 13:52 < alt0id> : recipe for target 'lightning.pb-c.o' failed 13:52 < alt0id> make: *** [lightning.pb-c.o] Error 1 13:52 < alt0id> make: *** Waiting for unfinished jobs.... 13:53 -!- johanth [uid223041@gateway/web/irccloud.com/x-nbltkxucsiettyol] has joined #lnd 13:53 < johanth> probably better to ask in #lightning-dev :) 13:59 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 14:06 < Jiamond> has the faucet https://faucet.lightning.community/ been updated based on the commits earlier today? I can't seem to connect to it; getting connection refused error. 14:10 < lndbot1> don't think so, I tried earlier 14:10 -!- HeySteve2 [~0000@unaffiliated/heysteve] has quit [Read error: Connection reset by peer] 14:21 < roasbeef> Jiamond: not yet 14:22 < Jiamond> cool, just making sure it wasn't something dumb on my side. 14:26 < roasbeef> cdecker: does that channel announcement have any set features for you? 14:30 < roasbeef> cdecker: hmm maybe we're encoding signatures differently? looking at it by hand, it all seems ot match up until the pubkeys 14:30 < roasbeef> cdecker: actually the short channel ID looks pretty funky 14:38 < alt0id> help! 14:38 < alt0id> roasbeef: 14:38 < alt0id> : recipe for target 'lightning.pb-c.o' failed 14:38 < alt0id> make: *** [lightning.pb-c.o] Error 1 14:38 < alt0id> make: *** Waiting for unfinished jobs.... 14:38 < alt0id> still have this error 14:38 < alt0id> what should i do? 14:43 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 14:46 < aakselrod> alt0id: again, probably better to ask in #lightning-dev 15:02 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 15:16 -!- spinza [~spin@196.212.164.26] has joined #lnd 15:28 -!- vicenteH [~user@13.232.15.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 15:45 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 255 seconds] 15:57 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 16:28 < aakselrod> cdecker: are you around? 16:36 < aakselrod> cdecker: https://github.com/aakselrod/lnd/commit/e612203e1479f08a152ce2df358e745a887f0d73 - looks like the test vector in https://github.com/lightningnetwork/lnd/issues/254#issuecomment-323997667 doesn't include a chain hash? 16:52 < roasbeef> cdecker: so it seems y'all haven't added the chain_hash field to chan_ann? 17:00 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:17 -!- MaxSan [~one@95.215.62.92] has joined #lnd 17:20 < stevenroose> Just updated, after coonfiguring the tls file again and the macaroon, I got this: 17:20 < stevenroose> [lncli] rpc error: code = Internal desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority" 17:20 < stevenroose> Does that mean that self-signed certificates are not supported? 17:22 < roasbeef> stevenroose: you shouldn't need to generate a new cert yourself, lnd will auto generate one 17:22 < stevenroose> I had one 17:22 < stevenroose> I just had to put it in ~/.lnd/tls.cert 17:23 < stevenroose> I created it myself with openssl. I use the same as for btcd rpc 17:23 < roasbeef> stevenroose: we had to create a diff set of certs, as languages like python etc with gRPC wouldn't accept the ECC certs we were using 17:24 < stevenroose> hmm 17:24 < roasbeef> we do generate a self signed cert as well 17:24 < stevenroose> That is when generating, right? 17:25 < stevenroose> That you had to make a specific kind of cert so that it would be compatible? But couldn't lncli still be very loose? I mean with supporting all kinds of certs 17:25 < roasbeef> had to switch to an RSA cert 17:25 < roasbeef> lncli was fine as it was Go, this change was made for Python, node.js, etc 17:26 < stevenroose> Yeah that's what I mean. The change to RSA etc should be in the generation code, should normally not affect lncli 17:26 < stevenroose> Let me look into the cert file 17:27 < roasbeef> do you have a strong reason to use your _own_ cert? 17:27 < roasbeef> you'll need to move over the server's key as well (if you didn't do that already) 17:27 < stevenroose> Oh, I copied the one from btcd it seems 17:27 < stevenroose> Issuer: O=btcd autogenerated cert, 17:28 < stevenroose> Well, I wanted to use the same for both btcd and lnd. I thought I just did openssl keygen, but I apparently took the one from btcd 17:28 < stevenroose> https://gist.github.com/stevenroose/7cc4e00041b5fbf10384ef8377fd4945 17:28 < stevenroose> Let me try with a custom cert 17:33 -!- MaxSan [~one@95.215.62.92] has quit [Ping timeout: 240 seconds] 17:36 < stevenroose> I guess it's solved. Now I get the common "transport: authentication handshake failed: x509: certificate is valid for bitcoin.roose.io, not localhost" 17:37 < stevenroose> There is only an rpcport config value, no rpclisten one to specify the interface 17:38 < stevenroose> It binds to 127.0.0.1 and a grpc proxy at localhost, should be 0.0.0.0 when serving external clients, I guess 18:04 < stevenroose> roasbeef: "[lncli] rpc error: code = Unavailable desc = grpc: the connection is unavailable" what does that mean? 18:04 < roasbeef> server isn't up? 18:04 < roasbeef> or can't bind to the port that you specified 18:08 < stevenroose> [INF] RPCS: RPC server listening on 127.0.0.1:10009 18:08 < stevenroose> and that's the port I specify 18:10 < roasbeef> has you confirmed that lnd has fully started? 18:11 < stevenroose> I did 18:12 < stevenroose> 017-08-23 03:05:12.519 [INF] CRTR: Pruning channel graph using block 000000000000 18:12 < stevenroose> getting those 18:14 < roasbeef> yep it's online 18:14 < roasbeef> are you runing lncli locally? 18:17 < stevenroose> uhu 18:17 < stevenroose> same machine. I use a domain but aliased that to 127.0.0.1 in /etc/hosts 18:17 < stevenroose> only problem I could see is that lnd serves only "localhost" instead of 0.0.0.0 18:18 < stevenroose> while the rpc http header contains the domain 18:18 < roasbeef> it doesn't use http 18:18 < roasbeef> by default lncli will look at 127.0.0.1 18:19 < roasbeef> well localhost 18:20 < stevenroose> yeah I use the --rpcserver=domain flag 18:20 < roasbeef> why not just localhost? 18:20 < roasbeef> you'll need to specify the port too for the rpcserver flag for lncli 18:20 < stevenroose> "transport: authentication handshake failed: x509: certificate is valid for bitcoin.roose.io, not localhost" 18:21 < stevenroose> can't have a cert that works remote and local apparently 18:21 < stevenroose> that;s why on btcd I have notls=1 and a different port and the regular port with TLS using nginx 18:22 < stevenroose> so that locally, I can do whatever and remotely I go through nginx who does TLS 18:22 < roasbeef> well it's possible to make the cert wildcard, but we don't currently do that 18:22 < stevenroose> CN=* does that work/ 18:23 < roasbeef> i'm confused though, if you're running all this locally, why do you need multiple certs? 18:23 < stevenroose> I want to be able to use the cli from remote 18:23 < stevenroose> instead of having to ssh 18:23 < roasbeef> we don't yet allow the rpc server to listen on anything else but localhost, as we didn't have TLS before 18:24 < stevenroose> I mean, it's not that important to me right now, but it's convenient and it should be possible in principle to have both remote and local connections, right? 18:24 < roasbeef> use mosh :) 18:24 < roasbeef> sure, previoulsy there was no auth at all, so we purposefully didn't enable such a mode 18:24 < stevenroose> haha, I considered mosh. mostly laziness as the only burden to using it :p 18:24 < roasbeef> pretty easy to install :p 18:24 < roasbeef> i'm using it right now 18:24 < roasbeef> use it on my phone as well for various things 18:25 < stevenroose> how does mosh and phone work with tmux? 18:25 < stevenroose> anyways, I got to go sleep. working early tomorrow 18:26 < roasbeef> mosh into the server, bring up tmux once connected 18:26 < roasbeef> cya 18:39 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 18:49 < aakselrod> you should be able to forward the port using nginx and it should work with your hostname 18:49 < aakselrod> (sorry, popping in for just a second) 18:49 < aakselrod> might need something other than nginx though, since lnd handles its own TLS 18:50 < aakselrod> and you need to make sure the common name for the cert you're using matches the hostname you're using to connect to it 20:13 -github-lnd:#lnd- [lnd] Roasbeef pushed 2 new commits to master: https://git.io/v5kj7 20:13 -github-lnd:#lnd- lnd/master 2d45552 Olaoluwa Osuntokun: htlcswitch: properly format chan_id on failure to find 20:13 -github-lnd:#lnd- lnd/master ff997ea Olaoluwa Osuntokun: discovery: ensure ChainHash field is populated when crafting new ChannelUpdates... 20:36 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 255 seconds] 21:01 -github-lnd:#lnd- [lnd] Roasbeef pushed 2 new commits to master: https://git.io/v5Ivj 21:01 -github-lnd:#lnd- lnd/master 1ff389b Olaoluwa Osuntokun: README: update with latest information 21:01 -github-lnd:#lnd- lnd/master ae5afcf Olaoluwa Osuntokun: docs: update installation notes with neutrino info 22:03 -!- MaxSan [~one@95.215.62.92] has joined #lnd 22:03 -!- Guest32399 [sid28048@gateway/web/irccloud.com/x-yzzfcchpdzjjwjwa] has joined #lnd 22:04 -!- Alina-malina [~Alina-mal@37.157.223.81] has joined #lnd 22:06 -!- Alina-malina [~Alina-mal@37.157.223.81] has quit [Changing host] 22:06 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #lnd 22:07 -!- Netsplit over, joins: Sentineo 22:08 -!- rabidus [~rabidus@85-23-137-40.bb.dnainternet.fi] has joined #lnd 23:16 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 23:16 -!- PaulCape_ [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 23:19 -!- lndbot1 [~lndbot@138.197.213.35] has quit [Read error: Connection reset by peer] 23:21 -!- lightningbot2 [~lightning@138.197.213.35] has quit [Read error: Connection reset by peer] 23:21 -!- lightningbot3 [~lightning@138.197.213.35] has joined #lnd 23:21 -!- lndbot [~lndbot@138.197.213.35] has joined #lnd 23:56 -!- garunyusama [c5ed1f9d@gateway/web/freenode/ip.197.237.31.157] has joined #lnd