I am trying to figure out how a pubkey can assign ‘child keys’ on its behalf.
Ex: Employees need the ability to engage on behalf of their company.
Is there any work on this? #AskNostr
Discussion
nostr:npub1c3lf9hdmghe4l7xcy8phlhepr66hz7wp5dnkpwxjvw8x7hzh0pesc9mpv4 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Nip-26 “Delegated Event Signing” seems to be the closest way to implement such a feature. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 had something to say a while back about this NIP having the potential to force its usage onto all of Nostr, but I cannot find the article. As a result, however, delegated event signing (using this nip) has fallen out of vogue. I do believe nos2x still implements it? Not sure what other signers or clients also do …
Here’s the spec:
Thank you.
There was a nip for key delegation that I thought was pretty cool, but the spec got dropped.
Yes, the company keypair says: "these are my employees, they can speak on behalf of the company", and then the employees publish from their own accounts.
Or the company hosts a small NIP-46 bunker signing service and employees use that to publish. The bunker server can make sure nothing too horrible can be published against its will and enforce custom permissions and limits.