Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhanced proposal to NIP6: Multi-seed nostr key pairs #282

Open
ecurrencyhodler opened this issue Feb 22, 2023 · 2 comments
Open

Enhanced proposal to NIP6: Multi-seed nostr key pairs #282

ecurrencyhodler opened this issue Feb 22, 2023 · 2 comments

Comments

@ecurrencyhodler
Copy link

Using multiple seeds to generate nostr key pairs will allow nostr identities to be:

  1. redundant
  2. flexible

Redundant
With a 2-3 keyset, a user can still retain access to their nostr identity using the other two keys to log-in if one key gets compromised.

Flexible
The key set can dynamically change as long as two keys are used to rotate one out. This allows a user to easily restore their keyset and re-introduce flexibility again if a key gets compromised.

Other advantages are that bitcoiners already use an m-of-n model for their multisig wallets. That means this isn't a foreign concept and current multisig wallets could even be repurposed for their nostr identities. We don't have to reinvent the wheel for securing the seeds either as they are well-established through hardware wallets or encrypted mobile keys. And it has built-in multifactor authentication, which is doubly important when using a protocol that has no undo button.

@ghost
Copy link

ghost commented Apr 13, 2023

Enhanced proposal to NIP6: Multi-seed nostr key pairs

Your proposal reminds me something like: horcrux, skewthreads/QR-secret-sharing

image

@dacervera
Copy link

Just want to build on @ecurrencyhodler's idea. This is another example of a cool feature which some power users may use, but become more or less essential for organizations, where key custodianship should be split across multiple authorizing officers for high-assurance event signing. Quorum control functions are instantiated at key generation, and are used on key activation (authorizing key for routine operational use), key backup and recovery, and in some cases event signing if the event is particularly significant enough to require multi-party agreement (FIAH ZEE MISS-ILES!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants