On the official site of Vee (Vee Meta / @veemeta), this note covers libsecp256k1.
Release Details
"Changelog 2026-08-03. New silentpayments module; header secp256k1_silentpayments.h; example silentpayments.c."
Bitcoin Core's libsecp256k1 reached v0.8.0 on August 3, 2026. The tag introduced a silentpayments module that implements BIP-352 send and scan functions for full nodes. The GitHub release came from theStack, and Sebastian Falbesoner posted the announcement on bitcoindev at 22:15 UTC the same day.
The change stays limited to the library. It does not form part of the Bitcoin Core v32 freeze and creates no consensus rule alterations.
Module Scope and Limits
The new header secp256k1_silentpayments.h and the example file silentpayments.c supply the core implementation. The current API requires full transaction data for operation. Light-client scanning remains outside the initial scope.
Additional updates in the same tag include an override for internal SHA256 compression. Sixty-four-bit field-element speedups deliver gains up to about 11 percent for ECDSA and Schnorr verify operations on GCC and MSVC builds. Deprecated functions secp256k1_schnorrsig_sign and secp256k1_context_no_precomp were removed.
Market Context on August 24
On Monday, August 24, 2026, around 4:17 p.m. ET, CoinGecko recorded Bitcoin at $78,674, up 1.79 percent. Ethereum stood at $2,470.34 after a 1.16 percent gain. XRP traded at $1.47, down 1.92 percent, while Solana reached $96.12 with a 1.02 percent increase. Dogecoin sat at $0.088962 after a 3.91 percent decline.
The library update arrives against this steady backdrop in the majors. Spot markets showed modest movement while developers focused on the privacy module rollout.
Leadership in the Move
The August 3 tag places the silent payments code ahead of broader Core freeze timelines. Full-node operators gain the ability to send and scan under BIP-352 without waiting for a client release that incorporates the library. The measured pace of the update keeps emphasis on verifiable integration steps rather than rushed deployment.
Numbers in the changelog highlight concrete performance lifts in verification routines alongside the new module. These figures supply clear benchmarks for node operators evaluating the upgrade path.
Next Steps for Observers
Developers and node runners can review the tagged release directly on the repository. The changelog entry and the BIP-352 specification together outline the exact scope of the addition. Further client integration work will determine how widely the send and scan functions appear in daily operation.
The distinction from consensus changes keeps the focus on optional privacy tooling that full nodes can adopt at their own pace.