Global Feed Post Login
Replying to Avatar Leo Fernevak

Agreed. Then there is the problem of a single private key. If that key is compromised, we are no longer in control over our identity. This is particularly problematic for companies that need to share their private key with several people.

If Nostr were to have two private keys, one of them a master key with admin capabilities for the identity, the protocol would need a new architecture.

As a result, whenever a Nostr spin-off architecture solves this problem, every company, corporation and security-minded user will migrate to the protocol with higher security. That's just how things work.

Avatar
Carsten Keutmann 1y ago

NIP-26

Delegated Event Signing

https://github.com/nostr-protocol/nips/blob/master/26.md

Reply to this note

Please Login to reply.

Discussion

Avatar
Leo Fernevak 1y ago

That's a great NIP solution.

The main issue I see is in cases where the root key is already compromised. It also requires a fully secure handling of the root key.

If we implement NIP-26 and then create new root keys from scratch, we could safely move from our old Nostr identities to new ones.

Avatar
Carsten Keutmann 1y ago

Root key management is hard, no easy way around it.

This is one of many solutions:

https://primal.net/e/note1xw04kjsq2cnay0xua7l5cnqgu9qkfnun4npmw54tyy68v8kr2wuq4x6jq8

Thread collapsed
Thread collapsed