pull down to refresh
0 sats \ 2 replies \ @ZezzebbulTheMysterious 13 Dec \ parent \ on: Lightning receiver privacy lightning
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.
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