Super Testnet's avatar
Super Testnet 10 months ago
It's good to hear that ldk gives you a new bolt12 every time, I think that's what all wallets should do > it’s not “because you reuse the same public key”, it’s because it’s the same thing! True, I agree, the problem is reusing the same payment string across multiple accounts, regardless of whether that payment string unwraps to a bolt12 or an lnurl or anything else For every new account at any service, you should make a new payment string

Replies (5)

Super Testnet's avatar
Super Testnet 10 months ago
I appreciate the correction you offer in the post I reply to below, and I think this is a good recommendation: for good privacy, don't reuse a bolt12 or any other payment string across multiple services. Instead, make a new payment string for each service you use. View quoted note →
Super Testnet's avatar
Super Testnet 10 months ago
I appreciate the correction you offer in the post I reply to below, and I think this is a good recommendation: for good privacy, don't reuse a bolt12 or any other payment string across multiple services. Instead, make a new payment string for each service you use. View quoted note →
Super Testnet's avatar
Super Testnet 10 months ago
I appreciate the correction you offer in the post I reply to below, and I think this is a good recommendation: for good privacy, don't reuse a bolt12 or any other payment string across multiple services. Instead, make a new payment string for each service you use. View quoted note →
It the service knows who you are it's not very important to give them a new bolt12 invoice. That's doubly true when they have a personal relationship with you, eg my consulting clients.