Updated to use `account` instead of `address_index` thanks to excellent feedback already in the PR.

Proposed an update to NIP-06 to allow infinite key generation from a single parent Bitcoin seed:

https://github.com/nostr-protocol/nips/pull/412

This will allow you to derive a practically infinite amount of Nostr keys from a single Bitcoin seed, especially useful if you run many different Nostr accounts.

Yes, sadly 😢

Not sure how you can check that before allowing posting of polls, though...

Yes!

Your votes are merely donations 😅

Nevermind, don't vote, won't workout without proper NIP-57 support for Zaps on BTC Pay 😭

Ah this won't work without NIP-57 support 😭

P.S. this is possible thanks to the latest update on Amethyst, love it!

#[1]

A day without an Amethyst update is a day without sunshine.

#[0]

👀

Looks very similar for Damus, would love to see it added there!

Think it's separate as it's a root key signing another root key as the ancestor.

Does anyone know if there is a spec or tool for properly signing over your account to a new set of keys?

Would be great to have an event that points clients to a new pubkey/profile when users switch keys.

Bounty is now 3.5m sats thanks to an anonymous Nostrich 😎

We've added a free Passport unit to the bounty to help whoever takes it on properly test the flow:

https://github.com/vitorpamplona/amethyst/issues/331#issuecomment-1496137923

Obviously requires some proof of capabilities before we'll ship this out, but would love to see this offer taken to help speed alone implementation and properly reward good work!

Yeah, something in my setup is flaky right now and I'm not sure what...

This is really the ideal approach for key security, but does add a bit of friction.

I think many people will be happy with login from root key over QR code as implemented now, but the more cautious approach will be NIP-26 style delegated keys.

Especially useful for enterprises and shared or company accounts as well.

New 1.5m sat bounty is live for NIP-26 implementation in Amethyst!

https://github.com/vitorpamplona/amethyst/issues/331

Specifically asking for login via delegated key signing, allowing you to authorize a login on Amethyst from a cold storage device like Passport without ever revealing your root Nostr key to Amethyst.

Your Nostr key stays cold, but you get full client functionality, and you can sign in in just a few seconds with a simple QR code exchange 👀

I have responded to every one of his claims, despite him using personal attacks, aggressive rhetoric, and attempting to wield me being able to admit when I'm wrong and learn from it as some sort of insult.

I'm done engaging with him, utterly pointless to waste time and brain cells engaging with him when he will just leverage any true compromise as a weapon against me later (for the umpteenth time).

How so?