From: Sebastian Falbesoner <sebastian.falbesoner@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] libsecp256k1 v0.8.0 released
Date: Mon, 3 Aug 2026 15:15:04 -0700 (PDT) [thread overview]
Message-ID: <9561e809-5fbe-4df6-9726-59ccaa00680bn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --]
We'd like to announce the release of version 0.8.0 of libsecp256k1:
https://github.com/bitcoin-core/secp256k1/releases/tag/v0.8.0
The most notable changes are:
* Addition of a new Silent Payments (BIP 352) module with support for
sending and scanning on full nodes.
* Addition of a function for overriding the internal SHA256 compression
function, useful for plugging in hardware-optimized SHA256 implementations.
* Performance improvements in the 64-bit field element implementation,
leading to significant speedups for many library functions on GCC and MSVC
builds (e.g., up to ~11% for ECDSA and Schnorr signature verification).
* Removal of the previously deprecated symbols
secp256k1_schnorrsig_sign (in favor of secp256k1_schnorrsig_sign32) and
secp256k1_context_no_precomp (in favor of secp256k1_context_static).
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/9561e809-5fbe-4df6-9726-59ccaa00680bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1710 bytes --]
reply other threads:[~2026-08-03 22:18 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=9561e809-5fbe-4df6-9726-59ccaa00680bn@googlegroups.com \
--to=sebastian.falbesoner@gmail.com \
--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