I made a pivot toward something better and now need some real world testing. I’ve built out passkey login for Zap Cooking.
In this flow, the passkey is not your identity and it is not a copy of your nsec. It is just the lock. Your key is encrypted, and the passkey is used to unlock/sign through Zap Cooking.
This is on a staged site, but it uses live Apple/Google passkey functionality, so please use a throwaway nsec only. Do not use your main key. Delete the passkey after testing.
Looking for feedback on UX, warnings, trust, and anything that feels confusing or sketchy.
Reply or DM if you’re willing to help. 🍳 sats will flow to the helpers ⚡️
Zap Cooking now supports Google-backed key backup on web and Android.
New users can create a Nostr key, encrypt it with a PIN, and store the encrypted backup in their own Google Drive. Same Google account + PIN restores it later.
This lowers friction for normal users without handing Google the key.
Thinking about adding the same backup option for existing Nostr users.
Poll below: good tradeoff, or bad habit?
View quoted note →
