-
Notifications
You must be signed in to change notification settings - Fork 127
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
Use correct encoding for public secp256k1 key #722
Merged
Merged
Conversation
This file contains 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
Sjors
reviewed
Jan 22, 2024
Don't forgot to update the branch to main. |
jakubtrnka
force-pushed
the
key-encoding
branch
from
February 6, 2024 17:46
40be044
to
d90bb98
Compare
I can test this against the Template Provider when #717 is fixed. But feel free to merge earlier. |
jakubtrnka
force-pushed
the
key-encoding
branch
from
February 6, 2024 18:28
f113a69
to
f3c06da
Compare
jakubtrnka
commented
Feb 6, 2024
jakubtrnka
commented
Feb 6, 2024
jakubtrnka
force-pushed
the
key-encoding
branch
5 times, most recently
from
February 6, 2024 19:04
f2764fc
to
669a5f1
Compare
LGTM only cargo fmt and tests to fix, I will open a PR with the fixes against @jakubtrnka branch |
jakubtrnka
force-pushed
the
key-encoding
branch
from
February 7, 2024 14:18
b6af360
to
537303e
Compare
Bencher
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
- Improve Display impl for key-util Error, add more error variants - Update format in key-util unit tests
- consequence of implementing Copy for secp256k1-keys types
jakubtrnka
force-pushed
the
key-encoding
branch
from
February 9, 2024 09:02
537303e
to
b8cf2db
Compare
@jakubtrnka some tests are failing with InvalidChecksum:
|
This was referenced Feb 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a suggested solution for #721