Non-API breaking introduction of Schnorr keys#589
Merged
apoelstra merged 3 commits intorust-bitcoin:masterfrom Apr 29, 2021
BP-WG:taproot/key-1
Merged
Non-API breaking introduction of Schnorr keys#589apoelstra merged 3 commits intorust-bitcoin:masterfrom BP-WG:taproot/key-1
apoelstra merged 3 commits intorust-bitcoin:masterfrom
BP-WG:taproot/key-1
Conversation
This was referenced Apr 12, 2021
4 tasks
Comment on lines
+90
to
+91
| pub use util::ecdsa; | ||
| pub use util::schnorr; |
Contributor
There was a problem hiding this comment.
👍
This is a tiny step towards #525 where the util module was made private.
apoelstra
approved these changes
Apr 26, 2021
Collaborator
|
utACK 230813b ! |
stevenroose
approved these changes
Apr 28, 2021
sgeisler
approved these changes
Apr 28, 2021
20 tasks
sanket1729
added a commit
that referenced
this pull request
Jan 9, 2022
… of bitcoin ECDSA cf0c48c Improve Debug for PrivateKey (Dr Maxim Orlovsky) b65a6ae Test for extended private key keypair generation f5875a (Dr Maxim Orlovsky) e6a3d60 BIP32 extended key `to_ecdsa()` and `to_schnorr()` methods (Dr Maxim Orlovsky) b72f56c BIP32 extended keys are using Scep256k1 keys instead of bitcoin ECDSA (Dr Maxim Orlovsky) Pull request description: This is third step required to introduce Schnorr key support according to #588. This PR starts API-breaking changes and is follow-up to non-API breaking #589, which is already merged. PR rationale: BIP32 does not support uncompressed keys and using type with compression flag was a mistake ACKs for top commit: apoelstra: ACK cf0c48c sanket1729: ACK cf0c48c. #757 might need rework after this Tree-SHA512: 6356a65004e7517256bacbf9aaeb69a22fd8536b341e567c5c4e819288e1105d083fe12ac0641404c407c97acf039bdc525f8e02b1b594a6cdda90106f3b1bdc
sanket1729
added a commit
that referenced
this pull request
Jan 11, 2022
…n ECDSA a6e8f58 PSBT BIP32 keys moved to Secp256k1 from bitcoin ECDSA (Dr Maxim Orlovsky) Pull request description: Fourth step in implementation of Schnorr key support after #588. This PR is a follow-up to non-API breaking #589 and API-breaking #590, which must be reviewed and merged first. ~~(The current PR includes all commits from #589 and #590, which should be reviewed there. The only commit specific to this PR is b8105e9)~~ UPDATE: All related PRs are merged now and this PR is ready for the review PR description: While PSBT BIP174 does not specify whether uncompressed keys are supported in BIP32-related fields, from BIP32 it follows that it is impossible to use uncompressed keys within the extended keys. This PR fixes this situation and is a companion to BIP174 PR clarifying key serialization: bitcoin/bips#1100 ACKs for top commit: apoelstra: ACK a6e8f58 sanket1729: ACK a6e8f58. Not sure which order to merge since there are many ready PRs which that would break each other. Tree-SHA512: 198ba646bbce1949b255a54a97957d952acdad8b7f9580be123116c0f44d773e6d90e0cac0d5993ec9a6b3328aa43aced0908522817861585877c50008fec835
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First two steps of #588, which are non-API breaking and can get into
0.26.1:util::ecdsa, while still re-exporting them asutil::keysuch that downstream dependencies will not breakutil::ecdsautil::schnorrmod re-exporting Secp256k1 Schnorr key typesutil::keyECDSA keys deprecated