[Feature/Bug] Validate Nostr key input into extension, if it's actually Nostr private key

[itstomekk]

Feature description

Looks like now in private key field one can paste npub and it derives another npub out of it

it confuses users, example

Describe the solution

validate whether pasted key is correct (if it starts with nsec....) - not sure if that's more difficult with hex format though

Describe alternatives

No response

Additional context

No response

Are you working on this?

None

[rolznz]

I think it's impossible to know with hex, but most people will not use hex these days. We could possibly add a warning if you paste a hex key that it cannot be verified? @stackingsaunter

[stackingsaunter]

@rolznz no one uses HEX today. If there's a warning with only npubs then I think this will be more than enough

[itstomekk]

Now, if someone pastes his public key npub1myprivatekey into nsec field, it doesn't validate - the extension just changes it to nsec1myprivatekey and then derives a new public from this private one