Some interesting possibilities for new types of delegate keys đź‘€

CC nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

Reply to this note

Please Login to reply.

Discussion

Not sure why the image is broken here's a copy

This is what nsec bunker already does.

But this would be totally trustless. No need to have a custodian hold your key or run your own bunker

From the “functional encryption” description it’s unclear what he means.

From my understanding, it's sort of like homomorphic encryption where you can create a function key based on a particular private key, which allows a certain function to operate on the encrypted data as if it was not encrypted. Thus, allowing for a note signing without revealing the nsec.

https://en.wikipedia.org/wiki/Functional_encryption#:~:text=Functional%20encryption%20(FE)%20is%20a,what%20the%20ciphertext%20is%20encrypting.

Ahhh. This looks fun. 🤓

This just sounds like NIP-26. It still requires the client to validated the delegation and remember who the real author was

This would allow the delegate to create a real signature as if they had the actual nsec based on some constraints. So somthing like x key can generate valid signatures for kind 1's with created_at < Y. And that would create valid signatures, clients would just verify them as any other note and you would have no idea that it was created via one of these delegate keys.