Replies (14)

#subkeys are local, instant, and secure—no remote signer, no waiting, no extra attack surface. Bunkers add dependency & friction; subkeys just work.
I think so. Each #safebox has its own nsec. It stores an owner npub, which is supposed to be the npub of the owner. This proposal might be useful for safeboxes that need to be publicly known, for example that they are operated on behalf of an owner (medical clinic) to issue medical records, credentials, etc. This would enable anyone to see that the wallet is properly delegated, anyone who needs to see that the medical record is properly signed and authorized.
Awesome! I know you'll do a great job. Just be aware that subkey field is an array, though parsing a string should be fine too. We have a few use cases with agentic and multi agents systems. But I think I will implement scratching an itch for some apps I made sharing bookmarks, todo lists and pastebins between devices:
Noted! It may come to pass. But we learnt the hard way in Linked Data that n-adic tags become hard to work with. Years of trial and error tells me a simple array in the profile will work well. But, I could be wrong. We'll know more after implementing it. Let's see...
Interesting- tags versus structured json in the .content field. My hunch is that tags are better for relays that wish to index on the tags, so that might be better if a relay wants to make it easy to retrieve and index the delegated keys. I don’t think it makes much of a difference from a client perspective, but I envision, like followers/following, subkeys could range into the thousands.