-
Notifications
You must be signed in to change notification settings - Fork 545
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
proto: completely remove cometbft.crypto.v1.PublicKey
#2878
Milestone
Comments
melekes
added
enhancement
New feature or request
crypto
Cryptography-related
needs-triage
This issue/PR has not yet been triaged by the team.
labels
Apr 23, 2024
4 tasks
melekes
added a commit
that referenced
this issue
Apr 25, 2024
and `pub_key_bytes` in `privval.PubKeyResponse`, `types.Validator` and `types.SimpleValidator`. Closes #2878
4 tasks
melekes
added a commit
that referenced
this issue
Apr 25, 2024
and `pub_key_bytes` in `privval.PubKeyResponse`, `types.Validator` and `types.SimpleValidator`. Closes #2878
melekes
added
protobuf
Protocol buffers-related
and removed
enhancement
New feature or request
needs-triage
This issue/PR has not yet been triaged by the team.
labels
Apr 25, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 29, 2024
and `pub_key_bytes` in `privval.PubKeyResponse`, `types.Validator` and `types.SimpleValidator`. Closes #2878 Follow-up to #2843 <!-- Please add a reference to the issue that this PR addresses and indicate which files are most critical to review. If it fully addresses a particular issue, please include "Closes #XXX" (where "XXX" is the issue number). If this PR is non-trivial/large/complex, please ensure that you have either created an issue that the team's had a chance to respond to, or had some discussion with the team prior to submitting substantial pull requests. The team can be reached via GitHub Discussions or the Cosmos Network Discord server in the #cometbft channel. GitHub Discussions is preferred over Discord as it allows us to keep track of conversations topically. https://github.com/cometbft/cometbft/discussions If the work in this PR is not aligned with the team's current priorities, please be advised that it may take some time before it is merged - especially if it has not yet been discussed with the team. See the project board for the team's current priorities: https://github.com/orgs/cometbft/projects/1 --> --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec --------- Co-authored-by: Sergio Mena <sergio@informal.systems>
mergify bot
pushed a commit
that referenced
this issue
Apr 29, 2024
and `pub_key_bytes` in `privval.PubKeyResponse`, `types.Validator` and `types.SimpleValidator`. Closes #2878 Follow-up to #2843 <!-- Please add a reference to the issue that this PR addresses and indicate which files are most critical to review. If it fully addresses a particular issue, please include "Closes #XXX" (where "XXX" is the issue number). If this PR is non-trivial/large/complex, please ensure that you have either created an issue that the team's had a chance to respond to, or had some discussion with the team prior to submitting substantial pull requests. The team can be reached via GitHub Discussions or the Cosmos Network Discord server in the #cometbft channel. GitHub Discussions is preferred over Discord as it allows us to keep track of conversations topically. https://github.com/cometbft/cometbft/discussions If the work in this PR is not aligned with the team's current priorities, please be advised that it may take some time before it is merged - especially if it has not yet been discussed with the team. See the project board for the team's current priorities: https://github.com/orgs/cometbft/projects/1 --> --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec --------- Co-authored-by: Sergio Mena <sergio@informal.systems> (cherry picked from commit d342b3a)
4 tasks
melekes
added a commit
that referenced
this issue
Apr 29, 2024
…2922) and `pub_key_bytes` in `privval.PubKeyResponse`, `types.Validator` and `types.SimpleValidator`. Closes #2878 Follow-up to #2843 --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec <hr>This is an automatic backport of pull request #2890 done by [Mergify](https://mergify.com). Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com>
|
Blocked on #122 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we're still using it inValidator
and remote signer, but we need to replace it withType
andBytes
too if we want to support modular crypto.Refs #2843 (comment)
The text was updated successfully, but these errors were encountered: