NIP-26 keys I think are limited to 30 days, in which they expire... might be tedious to renew.

Reply to this note

Please Login to reply.

Discussion

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

relevant 3 mins of what i was referring too.

https://youtu.be/sFjZ6kIJlCA?t=486

clipped to part