Boltz on Nostr: Good question! For full transparency: In this scenario it can: a) you used the same ...
Good question! For full transparency:
In this scenario it can:
a) you used the same rescue key for all your swaps and then use the rescue key file on a different browser to scan your rescue key for refundable swaps
In these scenarios it can't:
b) you refund using the same browser (using local storage, not the rescue key file)
c) you download a new rescue key for every swap just like before which is the default behavior for privacy browsers on a fresh local storage (see https://x.com/kilrau/status/1899852590797488332)
For privacy-conscious users, option c) avoids potential linking.
Just to have said it: we launched this for a reason
The old approach of per-swap refund files didn't work in some very painful edge cases. The idea is that with option c) we can serve both needs - privacy for the privacy-focused and emergency rescue for those in need.
Please let us know what we can improve 🙏
In this scenario it can:
a) you used the same rescue key for all your swaps and then use the rescue key file on a different browser to scan your rescue key for refundable swaps
In these scenarios it can't:
b) you refund using the same browser (using local storage, not the rescue key file)
c) you download a new rescue key for every swap just like before which is the default behavior for privacy browsers on a fresh local storage (see https://x.com/kilrau/status/1899852590797488332)
For privacy-conscious users, option c) avoids potential linking.
Just to have said it: we launched this for a reason
The old approach of per-swap refund files didn't work in some very painful edge cases. The idea is that with option c) we can serve both needs - privacy for the privacy-focused and emergency rescue for those in need.
Please let us know what we can improve 🙏