Replying to 9fe72c76...

I just tho thought it's not safe to keep using a single secret key to identify yourself and that is the only method to do so. If it possible to associate a nip5 identifier with multiple public keys that would be convenient.
Avatar
Disturbia 2y ago

so you are thinking of a rotating npub?

interesting...

nostr:npub1aeh2zw4elewy5682lxc6xnlqzjnxksq303gwu2npfaxd49vmde6qcq4nwx nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac

Reply to this note

Please Login to reply.

Discussion

Avatar
The Daniel 🖖 2y ago

Interested to hear what nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s learned in Nashville this week.

9f
9fe72c76... 2y ago

I am. Many systems such as GitHub recommend users to expire a key pair after a specific duration has passed for a security reason. I think that's reasonable to mitigate a risk.

Avatar
Disturbia 2y ago

the only way this would be possible if we have two sets of key

one permanent which control a second key which is changeable.

this would also be beneficial in events where our second key is compromised.

9f
9fe72c76... 2y ago

I agree. However, I don't like using key pairs as identifiers, to be honest. I would rather prefer identifying yourself by doing something like keybase.io is doing.