Doesn't nostr use BIP340 keys? A private key that has a public key with odd parity is not invalid; you just use the corresponding even parity point in encoding. It's effectively using -x * G for specific algorithms (see the "Default Signing" algorithm in bip340), but it's not that x is an invalid private key.
Honestly the x-only encoding was a bad choice, it has led to a lot of confusion and complexity.
waxwing /
npub1va…knuu7
2024-08-01 00:12:32
in reply to nevent1q…lgh3
Author Public Key
npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7Published at
2024-08-01 00:12:32Event JSON
{
"id": "3ae3387848cb44e90ca22cf20fffdf523bfd29246e5dac0cd06d848a8c96fb2f",
"pubkey": "675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728",
"created_at": 1722463952,
"kind": 1,
"tags": [
[
"e",
"bb9461ab8342a60a97470f9e46ab502a2b26a2f17b4d8a102ab5be9bdefa1a4c",
"",
"reply"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
]
],
"content": "Doesn't nostr use BIP340 keys? A private key that has a public key with odd parity is not invalid; you just use the corresponding even parity point in encoding. It's effectively using -x * G for specific algorithms (see the \"Default Signing\" algorithm in bip340), but it's not that x is an invalid private key.\n\nHonestly the x-only encoding was a bad choice, it has led to a lot of confusion and complexity.",
"sig": "c7d4ad05f4953aab9f1be17177a85259ec47968272e6f5f97de4a52a105ff164a6276fbb8e1af0eb94ac4cc3966cc31e24fd0893fc768d49f99e4a28541809b7"
}