Replying to Avatar fiatjaf

Well, my point was that no one thought about this question a single minute. Everybody just read NIP-26 and assumed it was the solution. NIP-26 is not a solution for this, it was made for temporarily delegating to third-party services because of the https://minds.com/ integration. And it was meant to be the least disruptive possible.

I can think of multiple other methods for doing delegation/revocation that would be better if the goal is to protect keys.

Can this be chewed up and spit out? I’d love to see your take:

https://github.com/swbratcher/nips/blob/master/NSUB.md

Reply to this note

Please Login to reply.

Discussion

No replies yet.