Maybe if disposable keypairs were used this would be more viable.

Sharing your "main" identity with a service provider is dumb.

nostr:nevent1qqsq7qcgaafkr7g4ry5z5jj3wu4xewdntdunzmn9s6lkrfvyy0tat7sprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvvqzeh9

Reply to this note

Please Login to reply.

Discussion

I agree. Subkeys have been a thing for a while in asymmetric crypto. I don't think people value their nostr identity very much, and it shows.

nostr:nevent1qqs8wd8aja0kg30dmc3jq589dhys32y4zlq6glnpm0kdrhygmx2d22spzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygrqsqqqqqp3u9h27

Agree, there should be a child key that is derived using some public information from the service and has no visible tie to your main key.

This could be a signing service, so that you can grant and revoke access to signing in your behalf. Temporary child keys could be a way to implement this while securing your main private key.

Sounds similar to how the SQRL protocol was designed.

https://www.grc.com/sqrl/sqrl.htm