Oddbean new post about login | logout 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
@Raymon @jb55 @rabble @ManiMe @fiatjaf
Nip-26 “Delegated Event Signing” seems to be the closest way to implement such a feature. @fiatjaf 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: https://github.com/nostr-protocol/nips/blob/master/26.md
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.