What about allowing subkeys in nip-05?
then you say subkey user@host is that same as masterkey user@host
{
"names": {
"_": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645"
},
"subkeys": {
"_": ["63788a374051653757367fd221bbf9c1b5c68bacc60ac45daa0b5877c6baf49c"]
}
}
What could be the use?
I see on the horizon one of the criticism that plagued NIP-26: the clients need to merge more keys in the visualization.
I like the Mastodon and Bsky way of delegating access tokens. Masto is really good with granularity.
Not sure how that can be done with the npub/nsec current structure if at all without breaking a lot of things.
