Dr. Hax on Nostr: If you want to use bip32 to solve this problem, see this fork of this thread: ...
If you want to use bip32 to solve this problem, see this fork of this thread:
You would get a unique key for each client and could rotate keys anytime you want. For a proof of concept, the only things that should need implemented in the client are:
1. Cryptographically verifying a sub-account's identity, and
2. Auto-following new identities that pop up
That would demo the concept and then, if it gains traction, you could make the key generation more user friendly.
quoting nevent1q…pr7eFirst, that's circular logic. Saying we're not going to implement it because other people might not implement it is just silly.
Second, using a seed and xpub does not require all clients to change their code. In fact, you could do this today with standalone tools and absolutely no code changes (example below).
Third, using an xpub would provide all the features with **less complexity**, backward compatibility, and you get a seed phrase for your identity.
Example that you could do today: Using standalone tools, generate an identity keypair and then generate sub-keys for each client. Each client gets its own unique key. Put the xpub, path, and a link to the identity npub in the profile for each client. Those who support programatically verifying the link can do so and all other clients can verify the link in the same way they do now: post a note with each authorized key on the identity account.
Imposters can claim they're sub-accounts of someone else, but the xpub won't check out and there won't be any note on the identity account saying that's a legit sub-account.
While this doesn't require any code changes, obviously it would be a better UX to have the software verify the link, auto-follow sub-accounts, and so on.
You can also choose to have multiple personalities that are linked. Maybe you use one sub-account to talk politics, one to talk about your mad ping pong skills, and another to talk about gardening. There could even be an indicator in the profile to indicate that following this sub account should not follow all the others automatically. The possibilities are only limited by our imagination.
You would get a unique key for each client and could rotate keys anytime you want. For a proof of concept, the only things that should need implemented in the client are:
1. Cryptographically verifying a sub-account's identity, and
2. Auto-following new identities that pop up
That would demo the concept and then, if it gains traction, you could make the key generation more user friendly.