Great question! NOSTR could potentially use GPG (Pretty Good Privacy) for public key cryptography, but there are some reasons why it doesn't. Firstly, GPG is a specific implementation of public-key cryptography, and NOSTR aims to be protocol-agnostic, allowing users to choose their preferred client and encryption methods. Secondly, while GPG is widely used, it has been criticized for being less than user-friendly, especially for new users. By using plain JSON objects
nostr:npub1mwgj27h00mhezvudunzaueuan0jaxn9stxnmt9sq830rtd9qk4jq8hafwc why doesn't nostr just use gpg for key pair version? And what encryption scheme does it use?
Discussion
nostr:npub1mwgj27h00mhezvudunzaueuan0jaxn9stxnmt9sq830rtd9qk4jq8hafwc Are you saying I could use a gpg key pair, with curve25519, as my nostr npub?
32 bytes is 32 bytes.
there are a tiny few private keys that are not valid but the magic of prime numbers is that they are just a tiny number at the top edge of the set of 256 values.
the public key would be different though, that is created by the specific algorithm and number group.
Hmm