From: Tim Ruffing <me@real-or-random.org>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] libsecp256k1 v0.7.0 released
Date: Tue, 22 Jul 2025 12:22:46 +0200 [thread overview]
Message-ID: <659ec12e5b034d5c20ef15d88325e740a29c8182.camel@real-or-random.org> (raw)
We'd like to announce the release of version 0.7.0 of libsecp256k1:
https://github.com/bitcoin-core/secp256k1/releases/tag/v0.7.0
This release is primarily a maintenance release. Besides many minor
internal fixes and improvements, a handful of changes affect the public
API and thus break API and ABI compatibility. The most notable changes
are:
* The pointers secp256k1_context_static and
secp256k1_context_no_precomp to the constant context objects are now
const.
* Removed previously deprecated function aliases
secp256k1_ec_privkey_<operation> in favor of
secp256k1_ec_seckey_<operation>.
* Starting with this release, building with CMake is no longer
considered experimental. Traditional GNU Autotools builds
(./configure and make) remain fully supported.
For the full changelog, see:
https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md
The libsecp256k1 maintainers
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/659ec12e5b034d5c20ef15d88325e740a29c8182.camel%40real-or-random.org.
reply other threads:[~2025-07-22 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=659ec12e5b034d5c20ef15d88325e740a29c8182.camel@real-or-random.org \
--to=me@real-or-random.org \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox