--- Day changed Sun Jan 21 2018 00:08 -!- daouzo235 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has joined #lnd 00:10 -!- daouzo23 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has quit [Ping timeout: 248 seconds] 00:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 00:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 00:14 -!- erols [~erols@dhcp-077-251-249-036.chello.nl] has quit [Quit: erols] 00:20 -!- ls64 [~ls64@S0106a84e3fe5f3b3.ed.shawcable.net] has quit [Quit: Leaving] 00:23 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has joined #lnd 00:25 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 255 seconds] 00:27 -!- daouzo2355 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has joined #lnd 00:28 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 00:30 -!- daouzo235 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has quit [Ping timeout: 260 seconds] 00:59 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 01:00 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 01:05 -!- daouzo2355 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has quit [Remote host closed the connection] 01:06 -!- daouzo2355 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has joined #lnd 01:07 -!- daouzo2355 [~daouzo23@178.115.129.163.wireless.dyn.drei.com] has quit [Client Quit] 01:18 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 248 seconds] 01:20 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 01:21 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Client Quit] 01:22 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 01:22 < meshcollider> why is travis failing on all PRs for the RACE=false jobs 01:22 < meshcollider> is that test just super flakey or has something happened 01:22 < meshcollider> because its passing on master but failing for even doc-only changes 01:37 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 01:49 < meshcollider> Ah looks like the tests are just super flakey, channel not opened before timeout errors look very common 01:50 < meshcollider> do the jobs on master have to be restarted a few times before passing completely? Or just luck that they don't hit that timeout too 01:51 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #lnd 01:52 -!- spinza [~spin@196.212.164.26] has joined #lnd 01:56 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 268 seconds] 02:00 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 02:05 -!- jukuli [jrasi@kapsi.fi] has quit [Ping timeout: 268 seconds] 02:07 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #lnd 02:08 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 02:10 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has joined #lnd 02:11 -!- anome [~anome@unaffiliated/anome] has joined #lnd 02:16 -!- deusexbeer [~deusexbee@080-250-076-170-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 260 seconds] 02:17 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has quit [Ping timeout: 248 seconds] 02:19 -!- Guest17 [~textual@144.48.36.29] has joined #lnd 02:20 -!- deusexbeer [~deusexbee@079-170-138-254-dynamic-pool-adsl.wbt.ru] has joined #lnd 02:21 -!- sour [50febceb@gateway/web/freenode/ip.80.254.188.235] has joined #lnd 02:21 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 02:22 -!- Martin-BTG [5f2bdcb5@gateway/web/freenode/ip.95.43.220.181] has joined #lnd 02:23 < Martin-BTG> hey 02:23 < Martin-BTG> someone from LND team here ? 02:24 < meshcollider> Martin-BTG: well, this is the lnd channel... ;) 02:24 < Martin-BTG> yes it is 02:24 < Martin-BTG> I'm looking for someone to reach about collaboration opportunity with Bitcoin Gold 02:25 < Veggen> I guess the focus now would be to get it ready, not expand it to other coins. 02:25 < Veggen> ...but bitcoin gold runs same software? so shouldn't be that hard? 02:26 < Martin-BTG> yup 02:26 < Martin-BTG> Exodus integrated us for like 2 hours 02:26 < Martin-BTG> 2 days ago, 12 hours before the release 02:26 < Martin-BTG> they have told us : "Ok, make an insight servers for us, and you will be included in the next version" 02:27 < meshcollider> Martin-BTG: I doubt support for bgold will ever be added to lnd at least in the main repo, you could make a fork and add support yourself though 02:27 < Veggen> LND is open source. Download it, play with it, fire it up towards your servers. 02:27 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 02:27 < Veggen> ...and see what needs to be done. 02:27 -!- sdfgsdfg [~fgfsdfgsd@58.84.104.182] has quit [Changing host] 02:27 -!- sdfgsdfg [~fgfsdfgsd@unaffiliated/sdfgsdfg] has joined #lnd 02:28 < Veggen> you have a bitcoin gold testnet, I would presume? 02:29 < Martin-BTG> We are going to restart the testnet in the upcomming days 02:29 < Martin-BTG> because we are adding new difficulty algorithm 02:29 < Martin-BTG> but yes, we do have 02:29 < Martin-BTG> also the regtest network is working pretty fine 02:29 < Veggen> then, that is the way to go. 02:29 < Veggen> I think adding more coins is pretty low on developer priority list now. 02:30 < Martin-BTG> Our idea was to first ask the LND team if they can add us, as we are going to offer a bounty for this 02:30 < Veggen> Sure. How many LND developers is the bounty for? 02:30 < Veggen> I mean, how many LND developers would you pay? 02:30 < Martin-BTG> this is why I would like to have a call to you 02:31 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has joined #lnd 02:31 < Veggen> I am no developer, really. I just contribute where I can. Testing, etc. 02:31 < Martin-BTG> (: 02:31 < Martin-BTG> we already have explored the way LND is working 02:31 < Veggen> Martin: Not gonna happen. Do it yourself, then it might. 02:31 -!- spinza [~spin@196.212.164.26] has joined #lnd 02:31 < Veggen> Martin: LND team is a bit low on developer resources already. 02:31 < Martin-BTG> as we do 02:32 < Veggen> Martin: Go play with it first, *then* come back if you have specific questions :) 02:33 < meshcollider> I have an unrelated meta question: with bitcoin core, there is really no concept of the "team", anyone who contributes is a core developer. Is that different with LND because it is coded by lightning labs company? So only employees are considered part of the "team"? 02:33 < Martin-BTG> however my email is martin@bitcoingold.org. Even if you don't want to do this, for future we may find common interest for implementation and our team to help your, your to help our, etc. 02:34 < Veggen> sure. Btw, I don't speak for LND team :) 02:34 < Martin-BTG> We do have a lot of respect for Ligthning labs, and you are the first to be contacted 02:35 < Veggen> Martin: the point is - right now getting a stable beta out is pri-1. 02:35 < meshcollider> Martin-BTG: I expect you'll get a similar response from c-lightning and eclair as well btw, you'll likely have to do it yourself if you want to add BTG support to any of them 02:35 < Veggen> and there is a small degree of urgency. Adding a new - and let's face it - not that large/important coin would take time off from that. 02:36 < Martin-BTG> top 6 mineable coin, that forked from bitcoin version 0.15.0.1 02:36 < Martin-BTG> however 02:37 < Martin-BTG> nice chatting with you 02:37 < Veggen> trying to be nice, but readjust your expectations :) If you do the work, it might happen. 02:38 < Veggen> And if you after you have tried for a while, do have som question, you could probably come back to ask. 02:38 < Veggen> but I don't think you'd see someone commiting to a collaboration at this point. 02:38 < Martin-BTG> If we don't ask, it will never happen you know 02:39 < Veggen> Martin: If you create a patch that can easily be merged, it might. 02:39 < Martin-BTG> fair enough 02:39 -!- nirved [~nirved@2a02:8071:b58a:3c00:1da9:c42:9818:9061] has joined #lnd 02:39 < Veggen> ...or you could just maintain a fork. 02:39 < Martin-BTG> as I said it is highly likely to offer a bounty for that 02:39 < Martin-BTG> so we are adjusting the parameters 02:40 < Veggen> Sure. Announce it openly somewhere, and see if anyone takes it? 02:40 < Martin-BTG> of the bounty as it must be done, to be able to be another branch or a patch 02:40 < Martin-BTG> to LND 02:40 < Veggen> if the changes aren't that large, maintaining a fork wouldn't be hard. 02:40 < CubicEarths> Anyone know of a network explorer other than ACINQs? 02:43 < meshcollider> CubicEarths: not for testnet, no. There is another one for mainnet though 02:44 < sour> but i think you can start this on the testnet: 02:44 < sour> https://github.com/chemicstry/recksplorer 02:45 < meshcollider> yeah they must have added mainnet support to LND for the live mainnet one but running it for testnet should be easy 02:46 < CubicEarths> thanks 02:47 < CubicEarths> the acinq explorer seems to be down.... no map... LOST! 02:47 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 02:50 -!- Guest17 [~textual@144.48.36.29] has quit [Quit: Poka] 02:50 -!- bitconto [~bitconto@141.255.166.214] has quit [Remote host closed the connection] 02:53 -!- paul_ [6d51d05d@gateway/web/freenode/ip.109.81.208.93] has joined #lnd 02:53 -!- Martin-BTG [5f2bdcb5@gateway/web/freenode/ip.95.43.220.181] has quit [Quit: Page closed] 02:54 < paul_> hey, do I need btcd to create paynment channel? I end up with Payment route failure error. 02:54 < meshcollider> paul_: are you using bitcoind currently or no node at all? 02:55 < paul_> no node at all 02:55 < meshcollider> paul_: neutrino? 02:56 -!- pokaret [52c0f4f2@gateway/web/freenode/ip.82.192.244.242] has joined #lnd 03:00 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 03:02 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 255 seconds] 03:03 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #lnd 03:05 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 03:06 -!- brg444 [sid207215@gateway/web/irccloud.com/x-eqzedhvskjmxlxzg] has quit [Quit: Connection closed for inactivity] 03:09 -!- pokaret [52c0f4f2@gateway/web/freenode/ip.82.192.244.242] has quit [Quit: Page closed] 03:11 -!- pioklo [~Pioklo@188.146.64.146.nat.umts.dynamic.t-mobile.pl] has joined #lnd 03:14 -!- paul_ [6d51d05d@gateway/web/freenode/ip.109.81.208.93] has quit [Quit: Page closed] 03:14 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 03:23 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has joined #lnd 03:24 -!- YungMoonHodler_ is now known as YungMoon 03:25 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has quit [Max SendQ exceeded] 03:25 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has joined #lnd 03:35 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Quit: Leaving] 03:42 -!- anome [~anome@unaffiliated/anome] has quit [] 03:50 -!- bitconto_ [~bitconto@179.43.159.242] has joined #lnd 03:50 -!- anome [~anome@unaffiliated/anome] has joined #lnd 03:53 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 03:57 -!- whphhg [~whphhg@unaffiliated/whphhg] has quit [Read error: Connection reset by peer] 03:57 -!- whphhg [~whphhg@unaffiliated/whphhg] has joined #lnd 04:00 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 04:01 -!- anome [~anome@unaffiliated/anome] has joined #lnd 04:05 -!- LordCow [~lordcow@lordcow.org] has joined #lnd 04:06 -!- anome [~anome@unaffiliated/anome] has quit [] 04:07 -!- anome [~anome@unaffiliated/anome] has joined #lnd 04:08 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 04:18 -!- sdfgsdfg [~fgfsdfgsd@unaffiliated/sdfgsdfg] has quit [Changing host] 04:18 -!- sdfgsdfg [~fgfsdfgsd@58.84.104.182] has joined #lnd 04:26 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 04:26 -!- CubicEarths [~cubiceart@46.243.136.25] has joined #lnd 04:31 -!- sour [50febceb@gateway/web/freenode/ip.80.254.188.235] has quit [Ping timeout: 260 seconds] 04:31 < Deelight> is there a reason lnd restport is not mapped to localhost by default ? 04:31 -!- bitconto [~bitconto@179.43.151.227] has joined #lnd 04:34 -!- bitconto_ [~bitconto@179.43.159.242] has quit [Ping timeout: 246 seconds] 04:36 -!- spinza [~spin@196.212.164.26] has joined #lnd 04:46 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 04:46 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Client Quit] 04:49 -!- CubicEarths [~cubiceart@46.243.136.25] has quit [Ping timeout: 246 seconds] 04:52 -!- ddd [c3d34f5f@gateway/web/freenode/ip.195.211.79.95] has joined #lnd 05:00 -!- bitconto_ [~bitconto@179.43.188.214] has joined #lnd 05:03 -!- bitconto [~bitconto@179.43.151.227] has quit [Ping timeout: 268 seconds] 05:03 -!- pioklo [~Pioklo@188.146.64.146.nat.umts.dynamic.t-mobile.pl] has quit [Ping timeout: 264 seconds] 05:22 -!- anome [~anome@unaffiliated/anome] has joined #lnd 05:25 -github-lnd:#lnd- [lnd] Deelight-fr opened pull request #646: restEndpoint now mapped to localhost instead of * (master...restEndPoint-localhost) https://git.io/vNgAk 05:33 < meshcollider> roasbeef: I notice there are a lore of branches in the repo most of which seem to have been merged into master a long time ago e.g. brar-handoff, elkremdev, sh143, perhaps those branches should be deleted to clean things up a little bit 05:38 -github-lnd:#lnd- [lnd] Deelight-fr closed pull request #646: restEndpoint now mapped to localhost instead of * (master...restEndPoint-localhost) https://git.io/vNgAk 05:44 < Deelight> (created an issue instead) 05:46 -!- troed [~troed@h-96-204.A323.priv.bahnhof.se] has quit [Remote host closed the connection] 05:48 -!- ddd [c3d34f5f@gateway/web/freenode/ip.195.211.79.95] has quit [Quit: Page closed] 05:58 -!- sdfgsdfg [~fgfsdfgsd@58.84.104.182] has quit [Quit: sdfgsdfg] 06:07 -github-lnd:#lnd- [lnd] halseth opened pull request #648: Don't reset announcement batch with unsent messages (master...fix-lost-announcement) https://git.io/vNgpB 06:11 -!- bitconto_ [~bitconto@179.43.188.214] has quit [Remote host closed the connection] 06:13 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Quit: leaving] 06:20 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has quit [Ping timeout: 246 seconds] 06:21 -!- bitconto [~bitconto@ip4d16c34a.dynamic.kabel-deutschland.de] has joined #lnd 06:24 -!- anome [~anome@unaffiliated/anome] has quit [] 06:25 -!- bitconto [~bitconto@ip4d16c34a.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 06:25 -!- bitconto [~bitconto@141.255.160.222] has joined #lnd 06:28 -!- anome [~anome@unaffiliated/anome] has joined #lnd 06:30 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has joined #lnd 06:34 -!- lnostdal [~lnostdal@85-118-92-248.mtel.net] has joined #lnd 06:37 -!- lnostdal [~lnostdal@85-118-92-248.mtel.net] has quit [Max SendQ exceeded] 06:37 -!- lnostdal [~lnostdal@85-118-92-248.mtel.net] has joined #lnd 06:45 -!- lnostdal [~lnostdal@85-118-92-248.mtel.net] has quit [Ping timeout: 248 seconds] 06:55 -!- jukuli [jrasi@kapsi.fi] has joined #lnd 06:57 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has joined #lnd 07:00 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 07:10 -!- pioklo [~Pioklo@188.146.64.146.nat.umts.dynamic.t-mobile.pl] has joined #lnd 07:15 -!- ctrlbreak [~ctrlbreak@fctnnbsc38w-47-55-95-227.dhcp-dynamic.fibreop.nb.bellaliant.net] has quit [Ping timeout: 240 seconds] 07:30 < waxwing> hmm, i guess that's one way to embed magic numbers into your code :) https://github.com/lightningnetwork/lnd/blob/master/fundingmanager.go#L1803 07:31 -!- lnostdal [~lnostdal@85-118-74-90.mtel.net] has quit [Read error: Connection reset by peer] 07:32 < waxwing> https://github.com/lightningnetwork/lnd/blob/master/fundingmanager.go#L1817-L1819 that's .. interesting 07:35 < Deelight> :D 07:55 -!- anome [~anome@unaffiliated/anome] has quit [] 07:57 -!- anome [~anome@unaffiliated/anome] has joined #lnd 07:58 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 08:01 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 08:09 -!- Beast [~Beast@221.146.26.169] has joined #lnd 08:16 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lnd 08:34 -!- davitmdesign [5f5af42b@gateway/web/freenode/ip.95.90.244.43] has joined #lnd 08:36 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tehrcxmpggddxrlo] has quit [Quit: Connection closed for inactivity] 08:46 < contrapumpkin> lol 08:47 -!- dsfhgdrges [d57f3b2e@gateway/web/freenode/ip.213.127.59.46] has joined #lnd 08:48 -!- dsfhgdrges [d57f3b2e@gateway/web/freenode/ip.213.127.59.46] has quit [Client Quit] 08:48 -!- davitmdesign [5f5af42b@gateway/web/freenode/ip.95.90.244.43] has quit [Ping timeout: 260 seconds] 08:48 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 248 seconds] 08:50 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 09:02 -!- anome [~anome@unaffiliated/anome] has joined #lnd 09:11 -!- swarm [43a97332@gateway/web/freenode/ip.67.169.115.50] has joined #lnd 09:11 -!- swarm [43a97332@gateway/web/freenode/ip.67.169.115.50] has quit [Client Quit] 09:13 < anome> is it possible to invalidate an invoice? 09:13 < anome> like, expire it 09:15 < Veggen> it expires after 1 hour per default. 09:18 < anome> but if i want to do it manually 09:18 < Veggen> you could pay it yourself? 09:18 < Veggen> "payment_error": "unable to find a path to destination", 09:19 < Veggen> didn't work very well for me :) 09:19 < anome> hmm, seems like a bit of a work around :) 09:20 < anome> also, that would make it pop up in subscribeInvoies which is what i'm trying to avoid 09:22 < lndbot> is it possible to roll back a channel close before csv expires? 09:22 < lndbot> any tricks? 09:48 -!- anome [~anome@unaffiliated/anome] has quit [] 09:50 -!- anome [~anome@unaffiliated/anome] has joined #lnd 10:08 -!- bitconto [~bitconto@141.255.160.222] has quit [] 10:13 -!- LordCow [~lordcow@lordcow.org] has quit [Ping timeout: 240 seconds] 10:17 -!- LordCow [~lordcow@lordcow.org] has joined #lnd 10:20 -!- pioklo [~Pioklo@188.146.64.146.nat.umts.dynamic.t-mobile.pl] has quit [Ping timeout: 260 seconds] 10:22 -!- anome [~anome@unaffiliated/anome] has quit [] 10:28 -!- anthonyism [~af@pool-100-14-7-68.phlapa.fios.verizon.net] has quit [Remote host closed the connection] 10:28 -!- anthonyism [~af@pool-100-14-7-68.phlapa.fios.verizon.net] has joined #lnd 10:33 -!- anthonyism [~af@pool-100-14-7-68.phlapa.fios.verizon.net] has quit [Ping timeout: 246 seconds] 10:38 -!- blademccool [~BladeMcCo@d108-180-243-50.bchsia.telus.net] has quit [Read error: Connection reset by peer] 10:51 -!- troed [~troed@h-96-204.A323.priv.bahnhof.se] has joined #lnd 10:55 -!- anome [~anome@unaffiliated/anome] has joined #lnd 10:59 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 11:05 -!- anome [~anome@unaffiliated/anome] has joined #lnd 11:31 -!- LordCow [~lordcow@lordcow.org] has quit [Ping timeout: 240 seconds] 11:32 -!- LordCow [~lordcow@lordcow.org] has joined #lnd 11:36 -!- LordCow [~lordcow@lordcow.org] has quit [Ping timeout: 240 seconds] 11:36 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has quit [Remote host closed the connection] 11:50 < anome> does something happen in subscribeinvoices when an invoice expires? 11:50 -!- anome [~anome@unaffiliated/anome] has quit [] 11:50 -!- anome [~anome@unaffiliated/anome] has joined #lnd 11:54 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 12:02 < spudowiar> Veggen: Create a channel from yourself to yourself first :P 12:18 -!- anome [~anome@unaffiliated/anome] has joined #lnd 12:19 < lndbot> I am working on a btcd node but it stalls while retrieving blocks. A little research and it looks like this was solved before. Is anyone else seeing this? Right now I have to manually disconnect peers that aren't serving blocks. https://github.com/btcsuite/btcd/pull/518 12:27 -!- anthonyism [~af@pool-100-14-7-68.phlapa.fios.verizon.net] has joined #lnd 12:35 -!- joaopbernhardt [bfbe68ba@gateway/web/freenode/ip.191.190.104.186] has joined #lnd 12:39 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 256 seconds] 12:40 -!- anthonyism [~af@pool-100-14-7-68.phlapa.fios.verizon.net] has quit [Remote host closed the connection] 12:42 -!- LordCow [~lordcow@lordcow.org] has joined #lnd 12:47 -!- capa66 [capa66@gateway/vpn/privateinternetaccess/capa66] has joined #lnd 12:51 -!- someone235 [~someone23@unaffiliated/someone235] has joined #lnd 13:00 < someone235> Hi, I read that if someone sends a previous balance from channel, the other side has "grace period" so he can double spend the transaction. Someone has an explanation on it? 13:01 < someone235> how exactly this mechanism works? 13:02 -!- mp___ [mi@hell.cx] has joined #lnd 13:03 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 13:07 -!- dalofeco [463ec862@gateway/web/freenode/ip.70.62.200.98] has joined #lnd 13:14 < waxwing> someone235, read the LN paper but basically, to update the channel to a new balance, each side gives the other side a "revocation secret" which creates the scenario you mention (your counterparty can steal the funds if you erroneously broadcast the earlier state instead of the updated one) 13:14 < waxwing> but this is probably not a topic for #lnd 13:15 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 13:17 -!- joaopbernhardt [bfbe68ba@gateway/web/freenode/ip.191.190.104.186] has quit [Ping timeout: 260 seconds] 13:19 < someone235> waxwing, the paper is up to date? Because the date on it is 2016 and I saw it mentioned somewhere tx malleability (which is irrelevant with segwit), so I wasn't sure it includes all the relevant data 13:20 < waxwing> no it isn't really up to date, i find it problematic also. basic ideas are right there but implementation is not the same as now. 13:22 < waxwing> someone235, you might find this useful (collection of info): https://www.reddit.com/r/Bitcoin/comments/7pwna9/lightning_network_megathread/ 13:24 -!- anome [~anome@unaffiliated/anome] has quit [] 13:27 < someone235> waxwing, do you have any particular article that sums it all and is mostly up to date? It doesn't have to have c++ implementation details :) But if something significant changed from the white paper I want it to read it too. Unless you think the best way is to read the white paper and then catch the gaps later? 13:28 < waxwing> i found rusty's blog posts the easiest way to get to understanding it in general terms (i.e. in the kind of terms your question is couched in), after that i read the paper and read different parts of the BOLTs (and am still reading) 13:29 < waxwing> but the paper should really be just updated to keep it simpler. the paper itself, although it's not an easy read, has the advantage of putting the entire mechanism, in detail, in one place. it's just out of date. 13:33 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 13:37 < someone235> waxwing, does rusty explain about which opcodes are used? Because I want to know it in order to understand exactly what is going in there. 13:39 < waxwing> the "coding blog" ones i meant, no, except briefly in passing. if you want to see the actual scriptPubkeys you have to go to BOLT 3. 13:39 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 13:40 < someone235> waxwing, cool thx! 13:40 -!- dalofeco [463ec862@gateway/web/freenode/ip.70.62.200.98] has quit [Quit: Page closed] 13:42 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has joined #lnd 14:05 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 260 seconds] 14:10 -!- JackH [~laptop@i25091.upc-i.chello.nl] has quit [Quit: Leaving] 14:12 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 14:16 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qldflzkjwkjdrhfq] has joined #lnd 14:19 -!- anome [~anome@unaffiliated/anome] has joined #lnd 14:19 -!- crisppY [b859fcea@gateway/web/freenode/ip.184.89.252.234] has joined #lnd 14:19 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 14:21 < crisppY> Hey. For multi-hop payments to work, do both the payee and payer have to have open channels with enough lnd funds to make the transfer? e.g Alice->Bob->Alex where Alice wants to send Alex 10 BTC but Alex's channel with Bob only has 1 BTC allocated 14:23 < crisppY> Anyone here? Would appreciate some advice in trying to implement lnd with my webapp 14:24 < meshcollider> Yes you cannot send 10BTC through a 1 BTC channel 14:24 < meshcollider> But you could send 1 BTC through there and 9 BTC through a different channel 14:24 < meshcollider> Route* 14:24 < crisppY> But what if Alex only has one channel with Bob 14:24 < crisppY> Then its not possible right? 14:25 < zyp> then Alice opens a new channel directly to Alex with enough capacity for the transfer they need to make 14:25 < zyp> and by doing that, LN grows new routes where they are needed 14:25 < crisppY> That would have to be on-chain with confirmations 14:26 < zyp> yes, but the next transaction over the same channel won't be 14:26 < meshcollider> crisppY: only to open the new channel, same as opening any new channel 14:26 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 14:26 < crisppY> See, I have been thinking of ways to implement LN in an exchange environment for ages now. I can't see how its possible without mass adoption first. 14:26 < zyp> then you're probably thinking about it wrong 14:26 < crisppY> Getting users to make buy/sell orders over lightning while keeping their private keys 14:27 < crisppY> reducing exchange responsibility and improving security 14:27 < zyp> that sounds like an orthogonal problem from LN to me 14:28 < crisppY> Hence why exchanges won't be able to support LN the way i have in mind? 14:28 < crisppY> Deposits and withdrawals maybe, but LN for buy/sell orders directly i dont think so 14:29 < crisppY> Then again, they would need to commit X BTC in the deposit channel 14:29 < crisppY> doesn't seem very useful 14:29 < zyp> how so? 14:30 < crisppY> Unless there's mass adoption, opening a channel requires fund allocation. If I open a 1 BTC channel and later on want to sell my 10 BTC, I would need to replenish the channel funds by making an on-chain tx. 14:31 < zyp> how is committing X BTC to a channel with an exchange any worse than simply sending the same X BTC through a normal onchain transaction? 14:32 < crisppY> Exactly. There isn't much a difference in the two methods. 14:33 < zyp> do you view that as a bad thing? 14:33 -!- anome [~anome@unaffiliated/anome] has quit [] 14:34 < crisppY> Well, other than a contribution to LN adoption, there isn't much to offer to users when implementing lightning in that fashion. 14:34 < zyp> I think you missed my point 14:35 < zyp> my point is that having to open a channel is the worst case, and the worst case is pretty much equivalent to the standard way before LN 14:36 < zyp> so okay, let's say you got X BTC to put into an exchange, so you open a channel with capacity X and send it all 14:37 < crisppY> I get that. I was hoping to use LN to improve the product in terms of speed, security, or whatever else outweighs the cons to getting it implemented. 14:37 < zyp> now it cost you as much as just sending X BTC directly, but now you have an open channel with the exchange with capacity X 14:38 < zyp> if you have other open channels, other notes can route transactions from the exchange, through you 14:38 < crisppY> Say you want to buy more BTC than you have allocated in your channel. You would need an on-chain transaction even though its a buy order which usually is instant 14:38 < zyp> and the balance on the opposite side of the channel would then come back to you 14:38 < zyp> which means you could reuse the channel again next time you want to buy X BTC 14:39 < zyp> this time, without opening a new channel 14:39 < zyp> alternatively, you could commit X + Y BTC to the channel when you open it 14:39 < zyp> so that even after sending X BTC, you can still send Y BTC more without paying additional fees 14:40 < zyp> but still retaining full control by holding the keys to the Y BTC yourself before you send it 14:41 < crisppY> How do I solve the receiving more than whats in your channel part? People wouldn't want to wait for an, usually instant, on-chain transaction 14:42 < zyp> who wouldn't? 14:42 < crisppY> usually instant meaning that other exchanges don't make customers wait for buy orders 14:42 < zyp> I'm not sure how you figure your direct orders are going to work 14:43 < Deelight> at the moment, i don't see why existing exchanges would try to use LN for buy/sell orders 14:43 < zyp> how would that work? 14:43 < crisppY> Well how would I liquidate the LND funds when moving BTC around in the exchange otherwise? 14:43 < crisppY> Another on-chain tx? 14:44 < crisppY> The user made the deposit, but now the funds are sitting in an lnd channel. 14:44 < zyp> back up a moment 14:44 < Deelight> they will use LN for deposits/withdrawal and keep their database to manage trades 14:45 < zyp> crisppY, if I make a limit order on an exchange, how would that work? what happens when somebody buys or sells into my order? 14:46 < crisppY> as soon as it gets filled, balance is moved of course 14:46 < crisppY> i dont understand what youre asking 14:46 < zyp> moved from where to where? who has controls of the funds before the order is filled? what if they don't want to cooperate? 14:48 < crisppY> these are questions i cannot answer either. my initial plan was that people can transfer lnd funds to the main wallet (exchange) until the order is filled which will then be moved to the buyer's wallet. in this case balance is safe in the case of a security breach 14:48 < zyp> so in essence only deposits and withdrawals would happen over LN then 14:48 < crisppY> i came across issues in channel funding and concluded its not possible quite some time ago, but i read this article on why people should implement lightning in exchanges 14:48 < crisppY> https://medium.com/@david_moser/economic-bootstrapping-of-the-lightning-network-aef8208b7e8d 14:48 < zyp> and that makes it easy 14:48 < crisppY> which is way im back trying to come up for a reason to implement 14:49 < zyp> if you make a LN withdrawal, the exchange will either find a route to you or open a channel to you, and in the latter case you'd have to wait for the channel to confirm 14:49 < zyp> which again means that the worst case is equivalent to what's normal today 14:50 < crisppY> users won't have access to their private keys then 14:50 < zyp> in what sense? 14:50 < zyp> both parties of a channel has keys to their share of the amount committed to the channel 14:50 < crisppY> im sorry yeah, my fault 14:50 < crisppY> i was thinking of something else 14:51 < crisppY> also an off topic. i've been exploring blockstream's liquid recently 14:51 < crisppY> you aware of it? 14:51 < crisppY> https://blockstream.com/liquid/ 14:52 < zyp> heard the name, don't know the details 14:52 < Deelight> it just won't change the fact than when you transfer funds to an exchange, they're not yours anymore 14:52 < zyp> Deelight, but it makes it faster to transfer funds 14:52 < Deelight> yup 14:52 < crisppY> Deelight: I thought that's something I could solve by using lightning for buy/sell orders. I guess its not very viable though 14:52 < Deelight> between exchanges too 14:52 < zyp> I can open a channel to an exchange and then just transfer bit by bit over it as I make trades 14:54 < zyp> the exchange could create a payment request when you post a buy order which needs to be paid before it's posted 14:56 < crisppY> Could I batch lightning channel creation transactions? 14:57 < crisppY> Its just an ordinary transaction so i dont think its a problem right? 14:57 < crisppY> 1 output to the lightning channel address? 14:58 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd 15:01 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 256 seconds] 15:04 < troed> I just started my lnd node on testnet. Strangely the only thing I see it do is to try endlessly to connect to the same IP over and over, and getting connection refused. I'll look into it more tomorrow. I do see I installed go 1.8 from the web page description but see 1.9.1 is recommended in the topic here. 15:19 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has quit [Quit: Leaving] 15:55 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 15:59 -!- nirved [~nirved@2a02:8071:b58a:3c00:1da9:c42:9818:9061] has quit [Quit: Leaving] 16:10 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 16:10 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 16:10 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 248 seconds] 16:17 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 16:23 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 16:26 <@roasbeef> meshcollider: yeh def should be deleted, many of them are pretty old 16:27 <@roasbeef> meshcollider: yeh some of the integration tests are bit a flaky, mostly due to variance of the size of w/e travis box that we end up on 16:28 <@roasbeef> it's been fixed progressively over the past by removing sleeps in integration tests and replacing them with hpoks from some of the streaming rpc's 16:32 <@roasbeef> meshcollider: any frequent contributor is considered part of the "team" :p 16:32 <@roasbeef> may not sound quite a prestigious as being a "core dev" tho lol 16:32 -!- yuri [42e4a228@gateway/web/freenode/ip.66.228.162.40] has joined #lnd 16:33 <@roasbeef> waxwing: lol well it's part of the protocol 16:33 < meshcollider> roasbeef: that's a good thing probably lol, "core developer" gets to people's heads ;) 16:33 < meshcollider> roasbeef: sweet I see 16:34 <@roasbeef> the funding manager code in particular could use a bit of refactoring to compress the now sprawled state machine 16:34 <@roasbeef> code itself can be much tigher, there's some patterns left over from when we were initially dual funder only 16:35 <@roasbeef> bajohns: yeh there's an issue with btcd where if it connects to like a Bitcoin ABC node then it'll stall out, we dont't yet have prallel block download so if a single peer stalls the entire sync does 16:36 < lndbot> @roasbeef I saw this bug after I asked above. https://github.com/btcsuite/btcd/issues/1024 16:37 < lndbot> There is a work around posted in the ticket. A watcher script to disconnect problematic peers 16:38 <@roasbeef> yeh that's a pretty poor solution, we need a proper one 16:41 < meshcollider> roasbeef: only reason I ask about the team thing is because it doesn't look like you've added any other collaborators to the repo outside of lightning labs staff, not even jimpo who is #5 commits, so just was curious :p 16:41 < lndbot> true; the methodology of the script works though. perhaps it could aid the real fix 16:44 < meshcollider> roasbeef: do you know if branch push builds on Travis use better machines than PR builds? That'd make sense why PRs timeout more often than master 16:46 <@roasbeef> meshcollider: not sure 16:51 < waxwing> Travis is a cryptographically sound source of randomness imo 16:52 < meshcollider> waxwing: lol 16:59 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 17:00 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #lnd 17:00 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds] 17:15 -!- mxg [~mxg@cpe-76-91-1-28.socal.res.rr.com] has joined #lnd 17:26 -!- Zouppen [joell@2002:54fb:a1cd::1] has quit [Ping timeout: 256 seconds] 17:31 -!- yuri [42e4a228@gateway/web/freenode/ip.66.228.162.40] has quit [Ping timeout: 260 seconds] 17:35 -github-lnd:#lnd- [lnd] Roasbeef pushed 1 new commit to master: https://git.io/vN2wN 17:35 -github-lnd:#lnd- lnd/master 86133e5 Matt Drollette: config: add peer, rpc, and rest listener options... 17:35 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #406: Add RPCHost option (master...add_rpc_host) https://git.io/vF253 17:35 < cloaks> yes, I am here 17:35 < cloaks> how can I help #lnd 17:36 < cloaks> alright, i'll add peer and rpc and rest listener options , on it 17:38 <@roasbeef> cloaks: just merged a pr that addresses that 17:39 < cloaks> ah gotchya, nicely done roasbeef 17:39 < cloaks> keep up the pristine work 17:42 -!- mxg [~mxg@cpe-76-91-1-28.socal.res.rr.com] has quit [Quit: afk] 18:19 -!- Zouppen [joell@2002:54fb:a1cd::1] has joined #lnd 18:47 -!- crisppY [b859fcea@gateway/web/freenode/ip.184.89.252.234] has quit [Quit: Page closed] 18:49 -!- ecks0r [182a99d3@gateway/web/freenode/ip.24.42.153.211] has joined #lnd 18:52 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 19:04 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 19:21 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 246 seconds] 19:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd 19:29 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 19:40 -!- goober [c4342715@gateway/web/freenode/ip.196.52.39.21] has joined #lnd 19:40 -!- goober is now known as Guest46060 20:20 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 20:25 -!- Guest46060 [c4342715@gateway/web/freenode/ip.196.52.39.21] has quit [Quit: Page closed] 20:29 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #lnd 20:30 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 256 seconds] 20:38 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 20:41 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 240 seconds] 20:56 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 264 seconds] 20:56 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #lnd 20:56 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 20:56 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd 21:10 -!- YungMoonHodler_ [~me@2a02:810c:c7c0:1965:74aa:c08b:b1ec:8700] has joined #lnd 21:10 -!- YungMoonHodler_ [~me@2a02:810c:c7c0:1965:74aa:c08b:b1ec:8700] has quit [Changing host] 21:10 -!- YungMoonHodler_ [~me@unaffiliated/boscop] has joined #lnd 21:13 -!- YungMoon [~me@unaffiliated/boscop] has quit [Ping timeout: 256 seconds] 21:24 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 21:24 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:26 -!- zib [zib@slick.hkt0.keff.org] has joined #lnd 21:41 -!- rrostt [9b04f009@gateway/web/freenode/ip.155.4.240.9] has quit [Ping timeout: 260 seconds] 21:43 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 21:44 -!- CubicEarths [~cubiceart@46.243.136.38] has joined #lnd 21:45 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:48 -!- CubicEarths [~cubiceart@46.243.136.38] has quit [Ping timeout: 246 seconds] 21:52 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 21:57 -github-lnd:#lnd- [lnd] Deelight-fr closed pull request #623: Fix: custom port (peerport config) in node announcement (master...master) https://git.io/vNRxg 21:57 < cloaks> great work team 22:05 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 22:07 -!- fattrat [~fattrat@85.214.132.154] has joined #lnd 22:08 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 256 seconds] 22:12 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 22:16 < Veggen> Does lnd actually have a 12-word seed or such for its private key? 22:20 < Veggen> ok, https://github.com/lightninglabs/lightning-app/issues/16 answers. 22:20 < Veggen> guess it will be fixed. 22:21 -!- Beast [~Beast@221.146.26.169] has quit [Ping timeout: 246 seconds] 22:24 -!- millerbot [47d96179@gateway/web/freenode/ip.71.217.97.121] has joined #lnd 22:34 -!- millerbot [47d96179@gateway/web/freenode/ip.71.217.97.121] has quit [Quit: Page closed] 22:35 -!- kayoh [68e8726d@gateway/web/freenode/ip.104.232.114.109] has joined #lnd 22:36 < kayoh> Hi team! Quick question, how do I set my node alias with LND? 22:43 < Deelight> it's not configurable yet 22:44 < kayoh> gotchaaaaa 22:44 < kayoh> I'm jealous of all the funny names on testnet 22:45 < Deelight> you can try to hardcore one editing server.go ;) 22:48 -!- Beast [~Beast@221.146.26.169] has joined #lnd 22:49 -github-lnd:#lnd- [lnd] wilmerpaulino opened pull request #650: invoice: avoid negative msat amounts (master...invoice-negative-amount) https://git.io/vN294 22:49 < cloaks> great work team 22:49 -!- kayoh [68e8726d@gateway/web/freenode/ip.104.232.114.109] has quit [Quit: Page closed] 22:50 -!- kayoh [68e8726d@gateway/web/freenode/ip.104.232.114.109] has joined #lnd 22:51 -!- Beast_ [~Beast@221.146.26.169] has joined #lnd 22:53 -!- eamonnw [~eamonnw@iceland.sdf.org] has quit [Ping timeout: 256 seconds] 22:54 -!- Beast [~Beast@221.146.26.169] has quit [Ping timeout: 260 seconds] 22:55 < meshcollider> Deelight, kayoh: or just merge https://github.com/lightningnetwork/lnd/pull/467 into your local repo before building :) 22:56 < kayoh> ohhh nice 22:58 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Ping timeout: 248 seconds] 22:58 < kayoh> I have 1 more question in the mean time, I opened a channel with the faucet, and currently have a channel balance of 50000, however my wallet balance is 0. Do I need to pull funds out of this channel into my wallet to open a channel with another peer? 22:59 < meshcollider> If you own funds in the channel, you'll have to close the channel in order to use those funds in another channel yes 22:59 < meshcollider> you cant lock up funds in two channels at once 23:01 -!- Beast_ [~Beast@221.146.26.169] has quit [Read error: Connection reset by peer] 23:01 -!- eamonnw [~eamonnw@iceland.sdf.org] has joined #lnd 23:01 < kayoh> ohhh 23:01 < kayoh> got it thanks! 23:01 < Deelight> ok you could get some regular testet btc on another faucet 23:03 < Deelight> https://testnet.manu.backend.hamburg/faucet 23:04 < kayoh> thanks deelight!@ 23:15 -!- kayoh [68e8726d@gateway/web/freenode/ip.104.232.114.109] has quit [Quit: Page closed] 23:19 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 23:21 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 23:25 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 23:26 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 23:28 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 23:28 < mlz> if you have plenty of btc in your lnd wallet, you can open many channels 23:31 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection]