pull down to refresh
0 sats \ 4 replies \ @ZezzebbulTheMysterious 13 Dec \ parent \ on: Lightning receiver privacy lightning
I did look at this, and looks interesting, but that's not exactly what I meant.
i was turned off by the discord thing, so didn't investigate further.
Exploring this idea more, I think its more about 'fake' nodes, eg: mitm nodes that front the traffic, analogous to domain fronting on CDNs. Rizful looks like temporary nodes, and I feel there is a bigger risk of losing funds will ephemeral full nodes, vs ephemeral fronting nodes that mitm the invoices.
Primarily, I don't want to have to create channels for the decoys. Ideally this would route to the 'real' destination via the decoy. I don't even know if this is possible!
I don't want to have to create channels for the decoys
Without channels how do you want to route private traffic?
Think about private traffic as "noise" that cannot be distinguished from other traffic or routes.
If you do not want to use disposable or decoy nodes, then as @supertestnet said, use https://lnproxy.org/
reply
Ah, we would need a private channel to route back from the decoy to the real node, and we would need the decoy with a valid public (or possibly private with hints) channel to handle the outer invoice. Ill think about this some more.
Maybe im looking for lnproxy.org like service I can spin up myself. No point using a 3rd party if I am trying to hide my true node pubkey.
reply
Maybe im looking for lnproxy.org like service I can spin up myself
you can spin up lnproxy for yourself, it's free and open source software and there are two implementations:
Go implementation: https://github.com/lnproxy/lnproxy-relay
Dotnet implementation: https://github.com/nodlAndHodl/lnproxy
reply
Thanks, ill take a look this weekend.
reply