Sebcurity on Nostr: > When a Mutiny Wallet user configures a Lightning Service Provider (LSP), which by ...
> When a Mutiny Wallet user configures a Lightning Service Provider (LSP), which by default is the Voltage LSP, all invoices created by the user will have Voltage's pubkey. From the sender's perspective, they are making payments to the Voltage LSP. The arrangement is akin to a VPN, where your interaction with websites originates from the VPN's IP address, not your home IP.
> However, Voltage is NOT the actual payment recipient, nor do they have custody of the funds. The secret (preimage) needed to unlock the funds is only known to the user. Consequently, Voltage cannot claim the funds upon receiving the payment. To successfully process the payment, Voltage has to pay the user's invoice, known only by Voltage. Both invoices lock to the same preimage. Only after the user claims their funds can Voltage redeem the payment. This process mirrors how Lightning onion routing works today, where each router in the path can't claim the funds routed to them unless their payment has been redeemed by the next node in line.
https://blog.mutinywallet.com/enhanced-lightning-privacy-for-mutiny-users/
> However, Voltage is NOT the actual payment recipient, nor do they have custody of the funds. The secret (preimage) needed to unlock the funds is only known to the user. Consequently, Voltage cannot claim the funds upon receiving the payment. To successfully process the payment, Voltage has to pay the user's invoice, known only by Voltage. Both invoices lock to the same preimage. Only after the user claims their funds can Voltage redeem the payment. This process mirrors how Lightning onion routing works today, where each router in the path can't claim the funds routed to them unless their payment has been redeemed by the next node in line.
https://blog.mutinywallet.com/enhanced-lightning-privacy-for-mutiny-users/