iOS users, do not enter your public key into websites trying to solve the Zap issue.

nostr:nevent1qqswkkfl5v4gpcd5vmyg32xjnm96ekw4m4uwlrdyvxah4980mwtmcqgpz9mhxue69uhkummnw3ezuamfdejj7q3qym4skeakd7j9ujy9tq8kt3szzw09depa0duhrz4a7v3etvafgu3qxpqqqqqqzlqnr8n

http://nostrcheck.me/media/public/nostrcheck.me_f59c0496165b512ec746dde60601b9629fdbc31213ce5f3c.webp

Reply to this note

Please Login to reply.

Discussion

I totally get it, that step will be replaced next week with a better method. There is no zapr backend the key is stored in IndexedDB and all signing happens on the local device key is never sent anywhere.

Source code is available github.com/hendore/zapr

That said for early testing a newly created nostr key pair should be created until I replace the need for capturing the nsec

Thank you sir.

Use burner accounts to test new clients

That's what I do 😁

oof

Added warning for now 👍🏻

🫂 Zapr now supports npub use 🎉