Add changelog entry for silentpayments module
What changed, and why it matters
This commit only adds a changelog entry describing a new 'silentpayments' feature that was already added to the project. It changes no code, no build files, and no configuration. There is no security issue in this commit itself.
No action required; this is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to CHANGELOG.md announcing the silentpayments module, its API header, an example file, and a note that full transaction data access is currently required. No source code, build system, or tests are modified.
Changed components
CHANGELOG.mdInspect captured patch +6 / −0
diff --git a/CHANGELOG.md b/CHANGELOG.md
index d4beb9c..c73d5ff 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
+#### Added
+ - New module `silentpayments` implements sending and receiving of Silent Payments according to [BIP 352](https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki). See:
+ - Header file `include/secp256k1_silentpayments.h` which defines the new API.
+ - Usage example `examples/silentpayments.c`.
+ - The `silentpayments` API currently requires full access to the transaction data (light client scanning is not implemented).
+
## [0.7.1] - 2026-01-26
#### Changed
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.