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 nostr:nprofile1qy8hwumn8ghj7efwdehhxtnvdakqzrthwden5te0dehhxtnvdakqqgxa7qav4pdduqu7vapdt0hnmu6jmuve6rf3ug4esk88ak59evamhc37dgp0 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...
Just built Passkey39: a library that generates the same crypto private key every time you use your Face ID or Touch ID. No more seed phrases to lose, your biometric authentication becomes your deterministic wallet key through WebAuthn magic.
What do you think? I'm curious if it's a good or bad idea 🤔
👉 https://github.com/dolu89/passkey39
🎯 Live demo: https://passkey39.dolu.dev
(Not published to npm until it's safe to use)
I'm not a cryptography expert, so if the implementation is flawed or the process isn't secure for reasons I'm unaware of, I'm open to feedback.
I'm also having passkeys synchronization issues between desktop and mobile.
What ln address you try to resolve for zaps?
Not a bad idea!
It's neither your actual fingerprint nor a random key - it's more complex. When you create a passkey, your device generates a random private key and stores it in the secure element. Your biometric (fingerprint/face) is just the unlock mechanism for that key, not the key itself.
⚠ So if you delete and re-register a new passkey, you will not be able to restore your old private key!
No, that's not how it works 😄 The private keys are generated using YOUR biometrics on YOUR specific device. You can't scan my face with your phone to access my wallet - the passkey is tied to my device's secure hardware, not just my face.
Just built Passkey39: a library that generates the same crypto private key every time you use your Face ID or Touch ID. No more seed phrases to lose, your biometric authentication becomes your deterministic wallet key through WebAuthn magic.
What do you think? I'm curious if it's a good or bad idea 🤔
👉 https://github.com/dolu89/passkey39
🎯 Live demo: https://passkey39.dolu.dev
(Not published to npm until it's safe to use)
I just published an article about data versioning issue on Nostr
nostr:naddr1qvzqqqr4gupzqkdedhud3d0xdvaetglphg2ew59xahtfhja6rpt6adjj5keq302eqq2kzuntwa2h2jry8pey24n02ymxxd6twdzrvf3vj3v
I am learning how mining pools work by building one
It's a nice challenge, I can learn more about how bitcoin works
Today I learnt a lot about Oauth2 and OpenId connect as server. It’s more difficult than I thought! 😅
Hopefully some people developed ready to use (and audited) frameworks to build oidc servers. It’s a so big part.
I keep learning