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

Bump libsecp256k1 #216

Closed
wants to merge 5 commits into from
Closed

Conversation

elichai
Copy link
Member

@elichai elichai commented May 13, 2020

This is built on top of #215
bumped via the vendor script(./vendor-libsecp.sh depend 0_1_2)
and added new seckey functions while deprecating the old (see last point in notable changes)

Notable changes:

FYI this means that we decided that changing the symbol names is not a breaking change, right? (I think it's a fair decision, we support only what we export in our public rust API, not hidden C symbols)

real-or-random and others added 5 commits May 13, 2020 10:40
This is configurable in upstream now.

Fixes rust-bitcoin#214.

So far, this just sets it to `4`. It's tempting to set it to `2` when `lowmemory` is enabled
but `lowmemory` is about RAM and not about binary size. This is better addressed by
a resolution of rust-bitcoin#193.
@apoelstra
Copy link
Member

Closing. Will make a new PR in the next couple hours.

@apoelstra apoelstra closed this Aug 26, 2020
@elichai elichai deleted the 2020-05-bump-libsecp branch August 31, 2020 16:31
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.

3 participants