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.
Login to reply
Replies (2)
How does Spark LSP know the end receiver of a lighting payment?
Very informative thread :)
Rizful GOAT 👍