Using a single trampoline node -- like a private invoice -- identifies the last PUBLIC hop in the route. It does not identify the final destination. And -- critically -- there is no centralized server like LightSpark who also gets to gobble up the I.P. addresses associated with the receiver.
Discussion
How does Spark LSP know the end receiver of a lighting payment?
Also, I know you met with the Spark people and somehow they talked you into this, but please be assured that Spark is NOT self-custodial. They're just running Lightning Nodes for you.
This is very likely why their server-side code is not public. It would make it PAINFULLY clear that they are custodying your users' funds...
All of this will be fine until a Democrat wins in the U.S., and at that point they'll need to KYC everyone, or probably will just shut down and give up.
For what it's worth, we've never met them.
But, we would like to know how their LSP knows the end destination when no other LSPs can know. We might not be caught up with that.
Yes, if you are paying an Lightning Invoice with LightSpark's API, the funds will go from their custody (their Lightning Node), onto the Lightning Network.
So in this case David Marcus won't have full end-to-end visibility into this payment.
However, YOUR user is still fucked. He's got their IP address, payment history, amounts, balance, basically everything.
But you are right if the RECEIVER is using the Lightning Network, instead of the Spark API, then yes, the RECEIVER gets some security.
So there's an interesting question. If a Blitz users only uses Spark for Lightning swaps and also uses a VPN would you consider that ok.
There’s no cross link between users and lightspark doesn’t have the IP. Plus, they don’t know who sent or revived the payments from that user.
Very informative thread :)
Rizful GOAT 👍