i envision a way in the future for an old pubkey to delegate a new pubkey, kind of tie them together in the network.
i could have sworn i heard people talking about it before on here.
#[2] am i smoking crack or is this possible
Discussion
Is it NIP26?
Yes. On that track. I think nip 26 is like if you have your keypairs stored away, in a device or signing device and don't to pull it out to sign each event/note. So you delegate a different keypairs you created to sign on your behalf.
Think an organization has a master pubkey for social media or whatever.
They can delegate with the master key, other keypairs for user to post in their behalf. Think if you hire a new employee you don't give them master keypairs you sign a dleegstion allowing their keypairs to sign for the organization. And i assume you can revoke as easily as you can grant access.
The other thing would entail your old pubkey having some flag recognized by the relays to include your new pubkey content in quietes for your old pubkey. So your old followers would get your notes w/o even having to refollow.
Like I said not sure if possible. Not a super technical guy, just enough to know I don't know enough.
NIP-26 keys I think are limited to 30 days, in which they expire... might be tedious to renew.
well thats kinda the point right?
you seem to understand the technicals a bit better than I.
something like this feasible with nip 26 in its current form? #[2]
Yeah, in some cases.
However, it looks like the 30 days was part of the `created_at` conditions, and is configurable. You can also create `conditions` for the `kind` of events.
So it could be used, I think, similar to subkeys in GPG.
Organizational use can be another case, as described. However I didn't see anything about revoking, outside of the `conditions`.
Thanks for your response! Get zapped
There is NIP-26 with delegated signing.