Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schnorr Futures #6

Open
kimdhamilton opened this issue Jul 15, 2017 · 1 comment
Open

Schnorr Futures #6

kimdhamilton opened this issue Jul 15, 2017 · 1 comment
Labels

Comments

@kimdhamilton
Copy link
Contributor

From @ChristopherA on June 30, 2017 21:58

At some point we'll want to move from koblitz ECDSA signatures to koblitz Schnorr signatures. This will offer some huge advantages long term.

Note however, unlike ECDSA you can't recover a Schnorr public key from a Schnorr signature. This means you have to get the public key from either the data structure, or from some other source.

We need to be sure that our data structures support both current ECDSA and Schnorr signatures. This means we may want to always publish the koblitz public key (used by both) in the signature even though in the ECDSA case it may be redundant (or not, as there may be multiple valid public keys, see #9)

Copied from original issue: WebOfTrustInfo/btcr-hackathon-2017#18

@kimdhamilton
Copy link
Contributor Author

move to RWoT

@kimdhamilton kimdhamilton self-assigned this Jul 15, 2017
@kimdhamilton kimdhamilton removed their assignment Jul 15, 2017
shannona pushed a commit that referenced this issue Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant