Skip to content

add entries for BIP-340: public/private key and varsig#398

Open
MichaelMure wants to merge 1 commit intomultiformats:masterfrom
MichaelMure:bip340
Open

add entries for BIP-340: public/private key and varsig#398
MichaelMure wants to merge 1 commit intomultiformats:masterfrom
MichaelMure:bip340

Conversation

@MichaelMure
Copy link
Copy Markdown

While bip340 operates on secp256k1, it makes sense to have separate values:

  • public keys have a different format: 32-byte x-only (bip340) vs 33-byte prefix+x (secp256k1)
  • private keys have the same format but different usage expectation
  • algorithm are different: schnorr (bip340) vs ECDSA (secp256k1)
  • signatures have a different format: 64-byte [R.x, s] (bip340) vs 64-byte [r, s] (secp256k1)

That is, they can't reasonable mix or interoperate.

I tried to pick values that makes sense, let me know if I should change them.

While bip340 operates on secp256k1, it makes sense to have separate values:
- public keys have a different format: 32-byte x-only (bip340) vs 33-byte prefix+x (secp256k1)
- private keys have the same format but different usage expectation
- algorithm are different: schnorr (bip340) vs ECDSA (secp256k1)
- signatures have a different format: 64-byte [R.x, s] (bip340) vs 64-byte [r, s] (secp256k1)

That is, they can't reasonable mix or interoperate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants