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.
Leo Fernevak
npub1y0…zfvpl
2024-08-28 07:42:27
in reply to nevent1q…5yh9
Author Public Key
npub1y02f89rpykzhqmrjjz99uwgyl9gh06sg0vpjmklu62rzxpx8mxps7zfvplPublished at
2024-08-28 07:42:27Event JSON
{
"id": "e8f2625af990158d0ea96d7e4bc0836eff85d2b982b77668d4b8addcf315eec4",
"pubkey": "23d49394612585706c72908a5e3904f95177ea087b032ddbfcd2862304c7d983",
"created_at": 1724830947,
"kind": 1,
"tags": [
[
"e",
"075660899eb7728610821c7ef23c0a816b0851a9f2be972f8dbe24539b881a20",
"",
"root"
],
[
"p",
"c9b19ffcd43e6a5f23b3d27106ce19e4ad2df89ba1031dd4617f1b591e108965"
]
],
"content": "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.\n\nIf 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.\n\nAs 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.",
"sig": "96962fc9077c45124f4885e29f84507d0d2436dc1ff5f1f657ac734c6fff64a8e83fb5beee886e10e6d13683cc03af29bae969bd6052e8b1f896e5852fd35b2f"
}