manime on Nostr: These are my thoughts so far… Right now, Nostr already has “event signer” apps ...
These are my thoughts so far…
Right now, Nostr already has “event signer” apps and browser plugins (for both web and native clients), which limit exposure to a private key by providing “signing” services for the “numerous” clients that need to sign events.
A new class of “key manager” apps and browser plugins, in addition to offering “event signing”, would primarily limit exposure to a “master” private key by providing “disposable” keypairs that could be used in any client. Such a key manager could “simply” deactivate any of the keypairs it has generated, without effecting the underlying signed events OR the profile that created them. Newly generated keypairs would all be able to sign for the same events.
This technology is already specified and in wide use as Bitcoin BIP32.
An onboarding client, being a users “first” app, would be an ideal client to provide such “key management” services.
Right now, Nostr already has “event signer” apps and browser plugins (for both web and native clients), which limit exposure to a private key by providing “signing” services for the “numerous” clients that need to sign events.
A new class of “key manager” apps and browser plugins, in addition to offering “event signing”, would primarily limit exposure to a “master” private key by providing “disposable” keypairs that could be used in any client. Such a key manager could “simply” deactivate any of the keypairs it has generated, without effecting the underlying signed events OR the profile that created them. Newly generated keypairs would all be able to sign for the same events.
This technology is already specified and in wide use as Bitcoin BIP32.
An onboarding client, being a users “first” app, would be an ideal client to provide such “key management” services.
quoting nevent1q…pa5zHow is this better than “simply” having a “master” key pair (like Bip32 “xpub” and “xprv”) that generates disposable pubkeys for use in any client? (where the “xpub” is actually exposed for anyone to verify the “ownership” of generated pubkeys)
AFAF : Dr. Hax (npub16v8…eqha)