Weird, I removed the cache for nips 34. It's now fixed.

Faut quand même être préparé à l'avance 😅 Je suis toujours d'avis que Nostr a un gros problème d'ux...

Comment tu peux te connecter en utilisant Nostr sur une borne publique ? 🤔 Tu as pu essayer ?

It should work with password manager that supports passkeys.
I didn’t know, passkeys on android are stored in google password manager by default.

My implementation is really basic. I use the passkey's signature as Input in HKDF. Not an expert, maybe it's a really bad idea?

The workflow you described with 2 keys looks great, but I'm not sure how it can be deterministic?

I built this lib for this specific use case. I'm building a PWA hot wallet with Ark

Probably possible yes, I don't know.
I would use this library for an everyday wallet with <100$ on it, but not to generate my hardware wallet mnemonic for example

Weird... Maybe @Egge could help on this?

That's currently the biggest problem with passkeys. A passkey is tied to a domain name. The only thing you can do is back up your mnemonic manually

If the domain name changes to another one, here's a solution: https://otpless.com/docs/knowledge-base/passkey/relateddomain

I hope a better solution will appears in the near future

Well, maybe it works by scanning the QR Code showed on desktop with your iPhone. Not sure about that 😅

You should use a cloud-synced passkey provider. I know Apple and Google provide native cloud backup for passkeys, so you can use the same passkeys between your iPhone and Mac, for example.

But I'd prefer a strong password manager with passkey support, because Apple's passkeys won't work on your Windows/Linux computer...