From my viewpoint, the relay doesn't need to implement signing or undergo any changes. To put it into perspective with my current situation, user's browser is storing private node data, say, a CLN rune. Whenever a user switches a browser or clears the local storage, they're required to re-enter the data.

The workaround I've considered involves my app generating a "vault-store" event. The user's extension would then encrypt it, sign it, and broadcast it to the relays.

Following this, when the user logs back in via nostr, my app could request the extension to decrypt the value and re-store it in the browser's local storage.

What do you think?