--- Day changed Fri Jan 11 2019 00:04 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 00:09 -!- eamonnw [eamonnw@faeroes.sdf.org] has quit [Ping timeout: 245 seconds] 00:35 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 00:36 -!- jungly [~quassel@79.8.200.97] has joined #lnd 01:40 -!- Deadlyelder [~textual@2001:7e8:c92a:2f00:c079:e50f:396c:c841] has joined #lnd 01:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 01:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 01:44 -!- Deadlyelder [~textual@2001:7e8:c92a:2f00:c079:e50f:396c:c841] has quit [Client Quit] 01:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 01:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 01:59 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 02:14 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 02:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 02:32 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 02:38 -!- eamonnw [eamonnw@faeroes.sdf.org] has joined #lnd 02:54 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 02:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 02:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 03:09 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 03:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 03:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 03:19 -!- gethh [uid264798@gateway/web/irccloud.com/x-oprrjufmklirpryt] has quit [Quit: Connection closed for inactivity] 03:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 03:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 03:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 04:00 -!- aielima_ [~aielima@gateway/tor-sasl/aielima] has joined #lnd 04:04 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 04:14 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 04:18 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 04:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 04:24 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 04:28 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 04:29 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 05:29 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:29 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 05:33 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 05:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 06:24 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 06:28 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 06:29 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 06:39 < Veggen> hmm...would neutrino et rid of some of the ZMQ problems? (like, with handling more than one client etc) ? 06:40 < Veggen> ...i.e. would you benefit from running neutrino instead of traditional towards your own node (thaat even runs on same box, maybe) ? 06:43 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #lnd 06:49 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 06:52 -!- Abel_L [52c5da61@gateway/web/freenode/ip.82.197.218.97] has joined #lnd 06:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 06:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 06:57 < molz> Veggen, Neutrino is not ready for mainnet and i don't understand your other question 06:58 < molz> Neutrino is a backend used for light lnd client and soon for mobile lnd 07:02 < Veggen> molz: sure, but you could also use it for regular? 07:03 < Veggen> what would be the drawbacks etc? 07:03 < Veggen> not that I currently have problems with ZMQ. Guess some of the changes done earlier helped a lot generally. 07:04 -!- Abel_L [52c5da61@gateway/web/freenode/ip.82.197.218.97] has quit [Quit: Page closed] 07:04 < molz> ah that, yes, that's the benefit that like, because neutrino is only supported in btcd, and btcd doesn't need ZMQ so that is a plus, but it takes a long time for btcd to fully sync, if you want to use your own btcd node to run neutrino 07:05 < Veggen> mmm, but neutrino is likely coming to bitcoind, no? 07:05 < Veggen> was thinking more future. 07:05 < molz> hopefully 07:06 < molz> i do hope someone can work on btcd and it can be optimized to sync faster 07:07 < molz> the problem with bitcoind is some core devs don't like the fact we use ZMQ in bitcoind 07:07 < Veggen> molz, btw: Any comments re my (non-completed) LND networking guide: https://random.engen.priv.no/archives/574 07:07 < molz> oh i haven't looked at it yet, been busy 07:08 < Veggen> no problem. 07:16 -!- booyah_ is now known as booyah 07:34 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 07:38 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 07:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 07:46 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 07:46 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has quit [Quit: gkrizek] 07:47 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 07:47 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has joined #lnd 07:49 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 07:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:58 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #lnd 07:59 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 08:00 -!- kim0 [uid105149@ubuntu/member/kim0] has joined #lnd 08:06 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Ping timeout: 246 seconds] 08:07 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has quit [Quit: gkrizek] 08:08 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 08:09 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 08:10 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has joined #lnd 08:11 < molz> Veggen, it looks good 08:12 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has quit [Client Quit] 08:12 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has joined #lnd 08:13 < molz> something will be changed soon like the cert? 08:19 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Quit: farmerwampum] 08:19 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 08:23 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Client Quit] 08:24 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 08:34 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Quit: farmerwampum] 08:34 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 08:38 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Client Quit] 08:39 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 08:39 < Veggen> molz: mm, there are work around real certs, yes? 08:39 < Veggen> that's what you mean? 08:39 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 08:41 < Veggen> think someone is creating a PR for letsencrypt support. (I have wanted to do that for a while, but have been too lazy lately :)) 08:41 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Client Quit] 08:45 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has joined #lnd 09:06 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 09:09 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Quit: farmerwampum] 09:09 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 09:09 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection] 09:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 09:13 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Client Quit] 09:14 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 09:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 268 seconds] 09:20 < molz> Veggen, yea that's what i've seen 09:29 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Quit: farmerwampum] 09:29 -!- farmerwampum [~farmerwam@104.129.28.146] has joined #lnd 09:37 -!- farmerwampum [~farmerwam@104.129.28.146] has quit [Ping timeout: 245 seconds] 09:38 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 09:59 < ctrlbreak> molz, I was actually trying to figure out my issue with my first bitcoind/ln node setup and noticed that most folks in the bitcoin channel informed me that ZMQ wasn't needed or compiled in by default... until I mentioned I was trying to set up LND and then it was 'well... they still use it, yes. So that's likely your issue'. 09:59 < molz> lol 09:59 < molz> don't talk in that channel, very frustrating to see how stupid they are 10:01 -!- cryptocashback20 [~cashback@185.195.16.74] has joined #lnd 10:01 -!- cryptocashback20 [~cashback@185.195.16.74] has quit [Client Quit] 10:02 -!- cryptocashback20 [~cashback@185.195.16.74] has joined #lnd 10:02 -!- cryptocashback20 [~cashback@185.195.16.74] has left #lnd [] 10:29 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 10:29 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 10:33 -!- kexkey [~kexkey@199.229.249.116] has joined #lnd 10:33 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Client Quit] 10:33 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 10:35 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 10:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 10:43 -!- so [~so@unaffiliated/so] has quit [Ping timeout: 246 seconds] 10:51 -!- so [~so@unaffiliated/so] has joined #lnd 11:12 -!- gethh [uid264798@gateway/web/irccloud.com/x-duoaqqmjscryhuhq] has joined #lnd 11:12 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has left #lnd [] 11:19 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 11:26 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 244 seconds] 11:26 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 11:28 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 11:29 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 258 seconds] 11:39 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 11:39 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 11:40 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 11:48 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 11:48 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 11:59 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 11:59 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 12:03 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Client Quit] 12:04 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 12:05 <@roasbeef> Veggen: a bit lighter weight on the client end 12:05 <@roasbeef> ctrlbreak: ah yeh you need to compile it in 12:09 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 12:09 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 12:10 < Veggen> roasbeef: but what about the server end? 12:10 <@roasbeef> doesn't need zmq compiled in? 12:11 <@roasbeef> you're asking why you'd run with neutrino if you already have a local full node? 12:11 < Veggen> well, yeah. I'm asking if there would be an advantage. 12:12 < Veggen> And say I wanted to run more LNDs to it. Would that be lighter with neutrino than zmq? 12:13 <@roasbeef> possibly 12:14 < lndbot> ZMQ does come with bitcoin core by default now 12:18 < ctrlbreak> I does! My last couple test VMs I stood up... I installed from repo and was pleased to find that ZMQ was already in the binaries :-) 12:18 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 12:18 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 12:19 < ctrlbreak> My previous VMs, where I compiled from source... I had to check and make sure I was compiling in ZMQ. 12:25 < ctrlbreak> Okay. Time to try and read GO. 12:54 -!- manantial [~tecnecio@unaffiliated/manantial] has quit [Remote host closed the connection] 12:55 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has quit [Quit: Leaving.] 13:04 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 13:04 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 13:06 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 13:08 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Client Quit] 13:09 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 13:42 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 13:43 -!- ABCLightning [c84488a8@gateway/web/freenode/ip.200.68.136.168] has joined #lnd 14:21 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 14:25 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 14:29 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 14:29 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 14:33 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Client Quit] 14:34 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 14:54 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 14:55 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 14:55 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 14:55 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 14:55 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 14:59 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 15:24 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 16:01 -!- aielima_ [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 16:08 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 16:22 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 250 seconds] 16:22 -!- kexkey [~kexkey@199.229.249.116] has quit [Read error: Connection reset by peer] 16:38 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has joined #lnd 16:38 < gmaxwell> Dunno if people saw Theymos' feeback, but I think it's interesting: https://bitcointalk.org/index.php?topic=5094384.0 16:43 <@roasbeef> proxy replied to him via achow101 a bit, if he wants his node to not route at all then he can make all his channel private and run this PR when it's merged https://github.com/lightningnetwork/lnd/pull/2203 16:43 <@roasbeef> it'll not accept any htlc's at all, and he can also set the "disable bit" on any public channels he may have 16:44 <@roasbeef> i don't get the DoS thing, would be just like any other layer 4 protection along with protocol level DoS mitigations that implementations have 16:44 <@roasbeef> not sure what he means by: Create a system where third-parties can trustlessly proxy incoming LN payments. 16:45 < gmaxwell> well, maybe the DOS is answered with a guide. Dunno. Usually though best practice DOS mitigation requires taking actions to prevent attackers from knowing the underlying host IPs, which might require implementation support. (for example, thats one of the reasons we support disabling address discovery in bitcoin core) 16:45 <@roasbeef> he also doesn't need to publcly advertise any tor or ip info at all as well, doesn't even need to listen, can make all the connectinos out bound 16:45 <@roasbeef> def, we're working on more guide for routing node operators, and also better protocol level DoS detection/banning within lnd itself 16:46 < lndbot> Once hop hints are better supported in implementations, merchants should probably start to keep their node details more hidden 16:48 < gmaxwell> roasbeef: on the trustlessly route comment, I think what he basically wants is somethign where someone else who is routing for third parties can host his channels without risk of funds loss for him. Not clear to me if thats really possible. 16:48 <@roasbeef> in terms of being able to source channels for inbound payment bandwidth, and managing that effectively, we're working on some other tools that shoudl help with that bootstrapping and managemnt case 16:49 < gmaxwell> what he's observing there though is that his node would make a _really_ good routing node, as he does bidirectional traffic (people paying for adds, him paying forum moderators) and quite a bit of it.. but he doesn't really want to be in the 'routing payments business' 16:49 < lndbot> The defaults in lnd may also change at some point to making routing and being public more of an opt-in thing 16:49 <@roasbeef> gmaxwell: ahh gotcha, it's kiiinda possible, like if you imagine the node has some special signing hardware/software that's able to distinguish routing/sending from regular forwrding. so if it knows the circuit map, then it can know to reject signing anything that isn't a regular fowward as a payment won't have an incoming htlc 16:50 <@roasbeef> gmaxwell: mhmm understand there's extra maintenence w/ actively routing etc, but for that there's options (tho maybe they aren't well documented) for him to opt out of routing all together 16:58 -!- ABCLightning [c84488a8@gateway/web/freenode/ip.200.68.136.168] has quit [Ping timeout: 256 seconds] 16:59 -!- valwal [sid334773@gateway/web/irccloud.com/x-vsndukrreixmvkxj] has joined #lnd 17:02 <@roasbeef> as for the current state of sidechains (his other recommendation) can't really find much info on if rootstock is actually even operational these days, and then there's a drivechain testnet or something like that? 17:09 -!- aerth [~aerth@gateway/tor-sasl/aerth] has quit [Remote host closed the connection] 17:09 -!- aerth [~aerth@gateway/tor-sasl/aerth] has joined #lnd 17:15 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 246 seconds] 17:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:50 < lndbot> Having third parties handle the routing for you should be perfectly fine, that’s kind of a use-case for hop hints 17:51 < lndbot> Choose a set of well-connected nodes to make channels with, then give out their nodes in your hop hints. Keep your own node private and only known to the hop-hint nodes 18:00 < gmaxwell> I think you're misunderstanding what he's talking about wrt routing. I don't think that he's referring to path calculations, etc. he doesn't want to handle third party payments himself, but wants the channels that are created for traffic with him to be usable for third party payments. 18:01 < lndbot> In theory a merchant shouldn’t require any direct channels from customers 18:01 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 18:02 < lndbot> By hiding their own node, they are proxying that routing task to the hop hint node 18:02 < gmaxwell> he isn't just a mercant, he's probably also the largest bitcoin-only-paying employer. 18:04 < lndbot> I don’t see any issue paying employees with LN if he wants to do that 18:07 <@roasbeef> gmaxwell: i think we follow, he doesn't want to passively forward right? 18:07 < gmaxwell> There isn't any 'issue' except for the fact that I keep repeating which doesn't seem to be getting communicated: He doesn't want to handle third party traffic, but thinks the channels would be really useful for third party traffic (as he has both directions to lots of different parties), which is why he wants to be able to outsource it. Obviously he could go dark, but it would be stupid for his employees 18:07 < gmaxwell> to get paid via channels since they couldn't use the channels to pay anywhere else. 18:07 < lndbot> I don’t think you can trustlessly outsource it in the sense that you directly earn the fees from the outsourcer 18:08 <@roasbeef> out source as in someone else run the nodes to accept payments for him? 18:08 < lndbot> You can select hop hints opportunistically though and they could in a sense bid on being placed as hop hints 18:09 < lndbot> Indirectly you earn the fee revenue from the good position in the graph of being a major source of bidirectional traffic 18:09 <@roasbeef> alexbosworth: he doesn't want to forward if i understand correctly, which is already handled on our end if that PR is merged and he only uses private channels 18:09 < lndbot> Yeah I am suggesting private channels 18:10 <@roasbeef> oh, he wants to out source forwarding? 18:10 < gmaxwell> He doesn't want to forward. But also if he is private then LN is a strict downgrade for his employees compared to just getting paid directly 18:10 <@roasbeef> he could still pay his employees if the chans are private 18:10 <@roasbeef> ok no fowarding: check 18:10 < lndbot> I don’t understand that, destinations don’t see anything about the origin of funds 18:11 < gmaxwell> yes, but the employees are worse off with the funds in a channel when the channel is private and can't be used for forwarding. 18:11 < lndbot> You mean the employees want liquidity in relation to his node? 18:11 < gmaxwell> Yes, but he doesn't want to be involved in forwarding himself. 18:11 <@roasbeef> ah, ok yes if the employees have direct channels, then the funds are just struck there in a sense, but if it's an inidrect path then there's no issue 18:11 <@roasbeef> he can make indirect payments w/o having to forward himself 18:12 < gmaxwell> ah., I see, so someone else opens a channel to the employee and he forwards via that. 18:12 < lndbot> Can’t he pay employees through the regular network? Then they have funds in the broader network which seems better than having it in private channels 18:12 < gmaxwell> similarly that same indirect party could get the channels people are making to pay him. 18:12 < gmaxwell> Basically giving away his graph position. 18:12 < lndbot> Yeah that sounds a lot better 18:13 < lndbot> The employee themselves can also select the hops they prefer with the same hop hint mechanism 18:14 < gmaxwell> Basically part of his concern is that his usage would make for a fantastic graph position-- well distributed traffic in both directions, but he doesn't want to forward third party traffic himself.... So it sounds like to me he could nominate some node run by a third party that all his activity would go through. He has channels with that third party, they have channels with whatever else. 18:14 < gmaxwell> They get the graph position he'd have. 18:17 <@roasbeef> yes so his direct peers (connected via private channels) know his position, but only via those un-advertised channels and nothing else 18:18 <@roasbeef> but his employees when they get paid don't learn his position, people can pay him with un-advetisd channels by encoding the "last mile" into the invoice 18:18 <@roasbeef> right now the identifier in the invoice is static, but we're working on letting that be dynamic each payment or invoic he gives out doesn't have the same ID 18:20 <@roasbeef> eventually, that can even be a full blown rendezvous route in the system, so they wouldn't even know any node ID when paying, would be route within a route type thing, get to bob and then bob can decrypt this and forward over to his initila direct connection who then dispatches that out to him 18:22 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 18:24 <@roasbeef> so right now, with hop hints, there's no plausible deniablity, Bob knows that when a payment comes across and it terminates at that private chanenl, it's going thre 18:24 <@roasbeef> we want eventually taht there's plausible deniablity, in that Bob doesn't know if there's some private network beyond that, and he only learned of it since he was in the TTL (say 3 hops) or something like that 18:26 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 18:30 -!- ekiro [~ekiro@unaffiliated/ekiro] has joined #lnd 18:33 -!- thomasan_ [~thomasand@172.83.40.67] has joined #lnd 18:38 -!- thomasan_ [~thomasand@172.83.40.67] has quit [Remote host closed the connection] 18:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 18:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 18:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 18:57 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 258 seconds] 19:17 -!- thomasan_ [~thomasand@172.83.40.67] has joined #lnd 19:21 -!- thomasan_ [~thomasand@172.83.40.67] has quit [Remote host closed the connection] 19:37 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 19:55 -!- thomasan_ [~thomasand@172.83.40.67] has joined #lnd 19:58 -!- thomasan_ [~thomasand@172.83.40.67] has quit [Remote host closed the connection] 20:10 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 20:10 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 20:33 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Quit: https://www.Quanto.ga/] 20:35 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 21:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 21:17 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 21:23 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 21:33 -!- farmerwampum [~farmerwam@184.75.210.138] has quit [Quit: farmerwampum] 21:33 -!- farmerwampum [~farmerwam@184.75.210.138] has joined #lnd 21:59 -!- ekiro [~ekiro@unaffiliated/ekiro] has quit [Quit: ekiro] 22:37 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd 23:40 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 23:41 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 23:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 23:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd