--- Day changed Wed Aug 23 2017 00:04 -!- garunyusama [c5ed1f9d@gateway/web/freenode/ip.197.237.31.157] has quit [Quit: Page closed] 00:56 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #lnd 01:27 -!- lndbot2 [~lndbot@138.197.213.35] has joined #lnd 01:28 -!- lndbot [~lndbot@138.197.213.35] has quit [Read error: Connection reset by peer] 01:52 -!- vicenteH [~user@195.235.96.150] has joined #lnd 01:58 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 01:59 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 02:03 -!- MDrollette [~MDrollett@feynman.drollette.com] has quit [Ping timeout: 240 seconds] 02:03 -!- lightningbot3 [~lightning@138.197.213.35] has quit [Read error: Connection reset by peer] 02:04 -!- lightningbot4 [~lightning@138.197.213.35] has joined #lnd 02:04 -!- lndbot2 [~lndbot@138.197.213.35] has quit [Read error: Connection reset by peer] 02:04 -!- lndbot [~lndbot@138.197.213.35] has joined #lnd 02:05 -!- MDrollette [~MDrollett@feynman.drollette.com] has joined #lnd 02:18 -!- dakk [~dakk@dynamic-adsl-78-15-237-78.clienti.tiscali.it] has quit [Ping timeout: 240 seconds] 02:30 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 240 seconds] 02:33 -!- MaxSan [~one@95.215.62.92] has quit [Ping timeout: 248 seconds] 02:37 -!- drvecctor [4db4f72a@gateway/web/freenode/ip.77.180.247.42] has joined #lnd 02:42 < drvecctor> hi! 02:43 < drvecctor> is there any community where opening of channels can be negotiated? 02:44 < drvecctor> any plans for a small scale bitcoin mainnet lightning network as soon as segwit activated? 02:44 < drvecctor> seems that lnd is quite functional already, right? 02:44 < johanth> you can try the lnd slack: https://lightningcommunity.slack.com/join/shared_invite/MjI4OTg3MzQ4MjI2LTE1MDMxNzM1NTMtNjlmOGYzOTI1Ng :) 02:45 < johanth> no timeframe set for mainnet network yet 02:45 < johanth> the implementations need to mature a bit more first 02:57 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has joined #lnd 03:01 < drvecctor> thanks! 03:47 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 04:00 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 04:01 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 04:23 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has quit [Ping timeout: 260 seconds] 04:31 < cdecker> roasbeef, this seems to suggest gossip is working with lnd: "Broadcasting batch of 4 new announcements" 04:31 < cdecker> Just need to plug in the introspection of channels and we should be good (apart from the short_channel_id mixup) 04:34 < cdecker> I can't see what goes wrong there: DISC: unable to validate channel update short_chan_id=3746036115963905: edge not found 04:35 < cdecker> And c-lightning tells me it knows about channel 3407:2:1 (which is that u64 in hex basically) 04:37 < johanth> can it be getting the channel update before it gets the channel announcement? 04:52 < cdecker> Shouldn't be, c-lightning discards updates for channels it doesn't know 05:09 < lndbot> cdecker are you on master? I had that same issue with some of the changes committed the other day, latest master works fine. 05:09 < lndbot> unless it's lnd <-> c-lightning specific too :P 05:10 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:12 < cdecker> I'm testing against master, my guess is it's a endianness misunderstanding as well 05:12 < lndbot> actually still getting those: : verification of channel updates failed chan_id=1297321466195673088 05:13 < lndbot> lnd <-> lnd with channels that do exist 05:13 < cdecker> Weird 05:21 -!- trotski2000 [sid206086@gateway/web/irccloud.com/x-xtlphhtucejtpnun] has quit [Ping timeout: 276 seconds] 05:23 -!- brg444 [sid207215@gateway/web/irccloud.com/x-olpvbyyyfivkvllx] has quit [Ping timeout: 276 seconds] 05:24 -!- trotski2000 [sid206086@gateway/web/irccloud.com/x-sbdvzrsnnukgcezr] has joined #lnd 05:26 -!- brg444 [sid207215@gateway/web/irccloud.com/x-zgoxwtbtopnejhmi] has joined #lnd 05:27 < cdecker> Yay, gossip integration tests pass ^^ 05:28 < cdecker> (now we broke eclair which is missing the chain_hash) 05:49 -!- sstone [~sstone@3.46-14-84.ripe.coltfrance.com] has joined #lnd 06:22 -!- MaxSan [~one@194.187.251.115] has joined #lnd 06:29 -!- dakk [~dakk@host135-80-dynamic.16-87-r.retail.telecomitalia.it] has joined #lnd 06:43 < cdecker> roasbeef, regarding the chain_hash in open_channel, we seem to actually send 0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206 as chain_hash for regtest over the wire 06:43 < cdecker> Could lnd be reversing it before checking with the chain_hash? 06:56 -!- buZz [~buzz@192.161.48.59] has joined #lnd 06:56 -!- buZz [~buzz@192.161.48.59] has left #lnd [] 06:56 -!- HolyNoodle [d589ac8a@gateway/web/freenode/ip.213.137.172.138] has joined #lnd 06:57 < HolyNoodle> hello ! 06:57 < HolyNoodle> I'm new to BlockChain but I'm trying to test the lightning implementation done by MIT 06:58 < HolyNoodle> Anyone wants to help me ? 06:59 < HolyNoodle> but for the moment i just reach the github address above. I'll check this for the moment ! 07:03 < molz> HolyNoodle, are you testing LIT? 07:03 < molz> HolyNoodle, you can ask in #lit channel 07:04 < MaxSan> Lit is the only one i aint looked at it 07:05 < molz> i think i'd stick with lnd for now, and waiting to see if i can test c-lightning 07:05 < HolyNoodle> Yeah but I followed what my coworker gave me... 07:05 < HolyNoodle> I think i'll look at lnd ! 07:05 < molz> HolyNoodle, if you install lnd we can help you better here 07:05 < HolyNoodle> LIT by MIT doesn't seem to be a working implementation 07:06 < molz> :) 07:06 < HolyNoodle> ok thank you for your offer. I'll look by myself and come back to you later :) 07:24 -!- dakk [~dakk@host135-80-dynamic.16-87-r.retail.telecomitalia.it] has quit [Remote host closed the connection] 07:57 -!- HolyNoodle_ [d589ac83@gateway/web/freenode/ip.213.137.172.131] has joined #lnd 07:59 -!- HolyNoodle [d589ac8a@gateway/web/freenode/ip.213.137.172.138] has quit [Ping timeout: 260 seconds] 08:04 -!- HolyNoodle_ [d589ac83@gateway/web/freenode/ip.213.137.172.131] has quit [Ping timeout: 260 seconds] 08:36 -!- MaxSan [~one@194.187.251.115] has quit [Quit: Leaving.] 09:10 -!- lndbot3 [~lndbot@138.197.213.35] has joined #lnd 09:11 -!- lndbot [~lndbot@138.197.213.35] has quit [Remote host closed the connection] 09:11 -!- rabidus [~rabidus@85-23-137-40.bb.dnainternet.fi] has quit [Remote host closed the connection] 09:32 -!- esotericnonsens_ [~esoteric@unaffiliated/esotericnonsense] has joined #lnd 09:34 -!- esotericnonsense [~esoteric@unaffiliated/esotericnonsense] has quit [Ping timeout: 240 seconds] 09:34 -!- esotericnonsens_ is now known as esotericnonsense 09:54 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #lnd 10:16 -!- sstone [~sstone@3.46-14-84.ripe.coltfrance.com] has quit [Quit: Leaving] 10:42 -!- MaxSan [~one@194.187.251.115] has joined #lnd 10:59 -!- ritchie_ [05c79b1e@gateway/web/freenode/ip.5.199.155.30] has joined #lnd 11:19 < aakselrod> drvecctor: re. opening of channels, all you have to do is connect to any lightning node (including the faucet) to get the network graph, and enable autopilot (in lnd) to start opening channels to other nodes 11:20 < aakselrod> the first part will also soon be automated by BOLT 10 implementations (DNS-based seeding for auto-connection) 11:35 -github-lnd:#lnd- [lnd] Roasbeef pushed 3 new commits to master: https://git.io/v5Lzd 11:35 -github-lnd:#lnd- lnd/master 6e3abdf Olaoluwa Osuntokun: macaroons: ensure all bytes read from db are copied before returning... 11:35 -github-lnd:#lnd- lnd/master d0b192c Olaoluwa Osuntokun: discovery: print proper error message when sigs fail to validate 11:35 -github-lnd:#lnd- lnd/master d4d5198 Olaoluwa Osuntokun: peer: if we don't have an advertised routing policy, fall back to default... 11:54 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 11:55 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [Client Quit] 11:57 -github-lnd:#lnd- [lnd] Roasbeef pushed 1 new commit to master: https://git.io/v5Lay 11:57 -github-lnd:#lnd- lnd/master 4871252 Olaoluwa Osuntokun: lnd+cmd/lncli: bump to version 0.3 12:17 -!- PaulCape_ [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 12:18 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 12:22 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Client Quit] 12:25 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 12:41 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 12:43 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 12:52 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 12:53 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [Client Quit] 12:53 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 12:57 < roasbeef> cdecker: nice! 12:58 < roasbeef> cdecker: you'd get that error "edge not found" if you try to process a channel_update before the channel_announcement message, which order to you send them in? 12:58 < cdecker> Pretty sure I'm sending them in the correct order (channel_announcement, followed by channel_update and then node_announcement) 12:59 < roasbeef> justin: that bug was fixed in a recent commit, was that didn't add the chain_hash do the updated channel_update messages 12:59 < cdecker> I guess lnd is not mixing the order right? 12:59 < roasbeef> yep that's the order we expect as well 12:59 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 12:59 < roasbeef> cdecker: re-reversing the chain hash, that's possible will look into it 13:00 < cdecker> It's strange because we send it in the same byteorder as bitcoin-cli provides it, but lnd complains about it not matching and showing it reversed 13:03 -!- adiabat [~adiabat@45.63.20.152] has joined #lnd 13:03 < roasbeef> hmm possible mismatch in the channel_id sent? as we attempt to look up the channel via that ID to validate the update announcement 13:04 < roasbeef> do you have logs you can share? thanks 13:04 < roasbeef> will take a look at the possible byte order reversal as well 13:05 -!- drvecctor [4db4f72a@gateway/web/freenode/ip.77.180.247.42] has quit [Quit: Page closed] 13:05 -!- adiabat [~adiabat@45.63.20.152] has left #lnd ["WeeChat 1.4"] 13:44 < cdecker> roasbeef, is it possible that you're not sending anything if open_channel fails? It just hangs there forever 13:45 -!- blockologist [41f6ae64@gateway/web/freenode/ip.65.246.174.100] has joined #lnd 13:45 < blockologist> hello all, I had some questions about how Lightning payment channels can affect supply and demand imbalances 13:46 < blockologist> I've heard and read a lot of things, but don't see any of this described on github or the website, it is just a bit hard to extrapolate 13:47 < blockologist> true or false: operating a payment channel requires a deposit of the host network's token (ie 'bitcoin') which indicates the token amount of the largest transaction which can flow through that channel 13:47 < blockologist> well, not true/false but how does this conform to my understanding? 13:47 < cdecker> true :-) 13:48 < blockologist> @cdecker what circumstance requires a payment channel to close? 13:48 < cdecker> You open a shared account so that both endpoints have to agree to spend it, and then you start negotiating who gets how much 13:48 < blockologist> does it get depleted based on number of transactions? 13:49 < blockologist> hm 13:49 < cdecker> No, you eventually want to use the funds in the channel for something else, e.g., another channel or an on-chain payment 13:49 < cdecker> You basically settle the final agreement on the blockchain and walk away with your share of the funds 13:49 < blockologist> and like 1,000 people can use the same payment channel? 13:51 < cdecker> Currently a channel can only have two endpoints 13:51 < cdecker> But you can forward other peoples payments over your channel 13:51 < blockologist> okay, still a bit abstract but lets look at another example 13:52 < blockologist> custodial exchanges and the current way they handle deposits and withdrawals, on most exchanges everyone gets a unique address 13:52 < blockologist> so instead they could all get a unique payment channel 13:52 < cdecker> No, the exchange creates an invoice 13:52 < blockologist> an invoice that the user has to agree to and that opens the payment channel 13:52 < blockologist> ? 13:52 < cdecker> The user uses that invoice to transfer the coins through a series of channels to the exchange 13:53 < blockologist> a series of channels?? 13:53 < cdecker> The exchange can then see to which user it gave the invoice and credit that user 13:53 < blockologist> I just imagined it was similar to a websocket 13:53 < cdecker> Opening a channel takes time, so we reuse them all the time 13:54 < cdecker> Think of it like the way your network at home works 13:54 < cdecker> If you have a cable from your PC to a switch and then on to another PC or to your ISP router 13:55 < cdecker> If you want to talk between two PCs you don't need to draw a direct cable from one to the other, all you need is that they are indirectly connected (through a switch) 13:55 < blockologist> I think I get it, but lets say a user wants to transmit 10,000 BTC to an exchange over a payment channel, and neither the exchange knows this, and the user also hasn't decided it would be this many yet 13:55 < blockologist> from pressing send on the user's side, how does the 10,000 BTC get credited to that user on the exchange 13:55 < cdecker> You send packets (payments) on your cable (channel) to the switch (other node), which will then forward it over the next cable until it gets to its destination 13:56 < cdecker> So the exchange creates an invoice (containing a hash that identifies the invoice) 13:57 < cdecker> The user gets the invoice and looks for a path that allows him to reach the exchange 13:57 < cdecker> The user then initiates the payment over that path, referencing the invoice hash 13:58 < cdecker> Upon receiving the payment (containing the invoice hash) the exchange looks up to which user it handed the invoice and credits that user's account 13:58 < cdecker> (btw 10k BTC is way too much...) 13:59 < blockologist> @cdecker so I imagine the exchange already has various payment channels already open (the path), does this mean that at least an additional 10,000 BTC is locked up supporting the payment channel? 13:59 < blockologist> the payment channels 13:59 < blockologist> plural 14:02 < cdecker> Yep, the smallest capacity along the path dictates the maximum amount you can transfer, hence you look for a path whose individual hops have at least the required capacity 14:03 < blockologist> interesting 14:03 < blockologist> @cdecker by default would the 10k btc get broken up in any way? 14:04 < roasbeef> cdecker: hmm atm if y'all send an uknown error code doesn't respond back to the RPC client, will fix that 14:04 < roasbeef> (if we send an open_channel and y'all reject it) 14:04 < cdecker> roasbeef, killing the connection would be easiest actually ^^ 14:05 < roasbeef> mhmm, left over from when we had specific error codes, atm we examine the first byte of the error data bytes 14:13 < cdecker> Latest test results btw: https://cdecker.github.io/lightning-integration/97839c27a65bd75d0ae86e2cc98f6e8d4b27ba72e6338bcac8dd4c1307d0f9e0.html 14:14 < cdecker> Adding chain_hash killed gossip with eclair but now works with lnd 14:14 < cdecker> :-) 14:14 < cdecker> 2 steps forward, 1 step back 14:17 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 14:23 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 14:25 < roasbeef> nice! 14:25 < roasbeef> cdecker: do you have a logs available forthe failed open channel attempt? 14:26 < roasbeef> initiated in either direction 14:34 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has quit [Ping timeout: 240 seconds] 14:41 -!- deusexbeer [~deusexbee@093-092-178-095-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 14:45 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 14:53 -!- ritchie_ [05c79b1e@gateway/web/freenode/ip.5.199.155.30] has quit [Ping timeout: 260 seconds] 14:54 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 15:03 < Emcy> roasbeef good job gettin new alpha out for segwit tonight 15:04 < Emcy> youre a good boi 15:13 -!- johanth [uid223041@gateway/web/irccloud.com/x-nbltkxucsiettyol] has quit [Quit: Connection closed for inactivity] 15:14 -!- at_rifat [2d2066ff@gateway/web/freenode/ip.45.32.102.255] has joined #lnd 15:15 -!- Me [d8470633@gateway/web/freenode/ip.216.71.6.51] has joined #lnd 15:16 -!- Me is now known as Guest4112 15:20 -!- Guest4112 [d8470633@gateway/web/freenode/ip.216.71.6.51] has quit [Ping timeout: 260 seconds] 15:25 < cdecker> roasbeef, here's the logs for openchannel c-lightning -> lnd https://seashells.io/v/nfVyzdy6 15:35 < cdecker> And here's the other way around (lnd -> c-lightning) https://seashells.io/v/vGDWEkm6 15:41 < Emcy> is the LN protocol encrypted at its core, inside the onion route 15:41 < Emcy> like https over tor for eg 15:46 -!- at_rifat [2d2066ff@gateway/web/freenode/ip.45.32.102.255] has quit [Quit: Page closed] 15:58 -!- deusexbeer [~deusexbee@093-092-178-095-dynamic-pool-adsl.wbt.ru] has joined #lnd 16:02 -!- blockologist [41f6ae64@gateway/web/freenode/ip.65.246.174.100] has quit [Ping timeout: 260 seconds] 16:07 -!- q-biq [q-biq@unaffiiliated/q-biq] has quit [Ping timeout: 260 seconds] 16:09 -!- deusexbeer [~deusexbee@093-092-178-095-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 16:10 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 16:11 -!- q-biq [q-biq@153.92.126.244] has joined #lnd 16:11 -!- q-biq [q-biq@153.92.126.244] has quit [Changing host] 16:11 -!- q-biq [q-biq@unaffiiliated/q-biq] has joined #lnd 16:12 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 16:23 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 16:26 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 16:30 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Client Quit] 16:36 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 17:00 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:17 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has joined #lnd 17:24 -!- deusexbeer [~deusexbee@093-092-178-095-dynamic-pool-adsl.wbt.ru] has joined #lnd 17:25 < aakselrod> Emcy: LN is encrypted at its core like tor hidden services (not HTTPS over tor - in fact, HTTPS isn't really used over tor for hidden services - see part 4 of https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs) 17:26 < roasbeef> adding to that, the connections between each node themselves are secured using some modern crypto: https://github.com/lightningnetwork/lightning-rfc/blob/master/08-transport.md 17:26 < roasbeef> the payments add an additionl internal routing onion encryption layer 17:27 < Emcy> right o 17:28 < Emcy> i keep forgetting to look at these "bolt" documents. Theyre like chapters in the LN spec i guess 17:29 < roasbeef> yep each doc covers a specific aspect of the protocol 17:30 < Emcy> what about ah, timing analysis attacks by a high level adversary? I know its not possible to guarantee privacy from that, but even small random forwarding delays can at least obfuscate fairly well? 17:31 < Emcy> or even completely fake payment traffic now and again..... 17:31 < aakselrod> the ping/pong messages help with that, but anything more would be premature optimization at this time 17:31 < aakselrod> need to get it all working reliably/interoperably first 17:31 < Emcy> sure 17:32 < Emcy> exciting. I cant believe this stuff about instant atomic cross chain swaps but without sidechains/pegs 17:33 < Emcy> it seems obvious now but it didnt occur to me before. Any random relay that is bridging can act as an autonomous coin exchange 17:34 < aakselrod> when there *are* sidechains that support lightning, cross-chain swaps will be available for those as well (and easier because you don't have to keep tabs on prices, only fees) 17:35 < Emcy> the cryptocoin landscape is going to change quite drastically 18:13 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 18:59 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has quit [Killed (Sigyn (Spam is off topic on freenode.))] 19:27 -!- douche [6c2f0f0e@gateway/web/freenode/ip.108.47.15.14] has joined #lnd 19:48 < grubles> grats guys 20:02 -!- cluelessperson [~cluelessp@cpe-76-85-20-142.tx.res.rr.com] has joined #lnd 20:02 -!- cluelessperson [~cluelessp@cpe-76-85-20-142.tx.res.rr.com] has quit [Changing host] 20:02 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has joined #lnd 20:15 -!- douche [6c2f0f0e@gateway/web/freenode/ip.108.47.15.14] has quit [Ping timeout: 260 seconds] 20:26 -!- B3B9A1 [49bd0ad0@gateway/web/freenode/ip.73.189.10.208] has joined #lnd 20:34 < B3B9A1> Anyone know how to build neutrino? I'm a bit of a go novice. My initial guess is `glide install` 20:36 < lightningbot4> neutrino is a library that is used by other software like lnd 20:39 < B3B9A1> I just came here to write the same thing. Turns out there's no need to manually build neutrino and it's built and linked in the lnd `glide install` 20:51 -!- bobleyy [2a730221@gateway/web/freenode/ip.42.115.2.33] has joined #lnd 20:53 -!- bobleyy [2a730221@gateway/web/freenode/ip.42.115.2.33] has quit [Client Quit] 21:09 -!- B3B9A1 [49bd0ad0@gateway/web/freenode/ip.73.189.10.208] has quit [Ping timeout: 260 seconds] 21:44 < molz> guys.. upvote pls: https://www.reddit.com/r/Bitcoin/comments/6vo2wt/towards_a_unified_lightning_network/ 21:44 < molz> and congratz, everyone, segwit is here! 21:52 -!- f4t4l [46738a13@gateway/web/freenode/ip.70.115.138.19] has joined #lnd 21:52 -!- f4t4l [46738a13@gateway/web/freenode/ip.70.115.138.19] has quit [Client Quit] 21:58 -!- moxie [49524074@gateway/web/freenode/ip.73.82.64.116] has joined #lnd 21:58 < moxie> Great show! 21:59 -!- moxie [49524074@gateway/web/freenode/ip.73.82.64.116] has quit [Client Quit] 23:18 -!- JackH [~laptop@46.189.28.188] has joined #lnd 23:18 -!- JackH [~laptop@46.189.28.188] has quit [Max SendQ exceeded] 23:18 -!- JackH [~laptop@46.189.28.211] has joined #lnd 23:18 -!- fr33dom_l0v3r [ce7d4be7@gateway/web/freenode/ip.206.125.75.231] has joined #lnd 23:29 -!- fr33dom_l0v3r [ce7d4be7@gateway/web/freenode/ip.206.125.75.231] has quit [Ping timeout: 260 seconds] 23:57 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd