libsecp256k1

This commit adds new public API functions to the silentpayments module of libsecp256k1 to support recipient-side labels for BIP352 silent payments. It is a feature addition, not a security fix or vulnerability patch. There is no evidence in the commit or supplied references of any security defect, exploit, or incident.

This commit is a clean-up rewrite of how internal numeric values are converted into 32-byte output inside the secp256k1 cryptography library. It replaces many byte-by-byte shift-and-mask operations with a smaller number of whole-word writes using existing helper functions. The commit message explicitly states the output is unchanged, and the diff shows a direct mechanical refactoring with no change to inputs, preconditions, or callers.

This commit is purely cosmetic: it adjusts the spacing in a markdown table inside the SECURITY.md file so the columns line up visually. No code, keys, fingerprints, instructions, or security policy content were changed.

This commit simply adds a new person's PGP key to the project's SECURITY.md file. It is an administrative documentation change with no code modifications and no security vulnerability.

This commit updates documentation to remove one person's cryptographic key from the project's list of trusted security contacts, and updates the README's example release tag and signature to reflect a newer release signed by a different trusted developer. It is a policy/documentation change, not a code fix for a software vulnerability.

This commit only fixes two mistakes in the documentation comments above two internal helper functions. It changes the stated allowed ranges for the number of bits that can be read and the allowed sum of offset plus count. No actual code logic is modified, so there is no security-relevant behavior change in the program itself.

This commit fixes an off-by-one error in the documented and runtime-checked input limit for a low-level math helper called secp256k1_fe_equal. The function compares two finite-field values for equality. It first negates one input (which temporarily raises its internal 'magnitude' by 1) and then adds the other input. Because the addition can only safely accept inputs whose magnitudes sum to 32, the second input's magnitude must be at most 30, not 31. The previous bound of 31 was therefore one too high and could have allowed an internal overflow in the magnitude bookkeeping. The patch lowers the documented bound and the VERIFY_MAGNITUDE check from 31 to 30, and adds a focused test exercising the corrected boundary. This is a correctness/reliability fix in cryptographic arithmetic, not a directly exploitable remote vulnerability.

This is a test-only cleanup. The commit removes a unit test pattern that passed a stack-allocated (non-malloc) scratch-space object to a destroy function that could call free(), which is undefined behavior. The test logic is reimplemented using a heap-allocated object instead. It does not change the production library code that Bitcoin or other applications use.

This commit is a routine fix to the project's automated macOS testing setup. Homebrew (a package manager for macOS) recently started refusing to load formulas from third-party sources unless explicitly trusted. The change simply tells Homebrew to trust the third-party tap that provides the Valgrind testing tool, so CI builds can continue. It does not change any cryptographic code, wallet handling, or network behavior in Bitcoin Core or libsecp256k1.

This commit is a routine cleanup of compiler feature checks in the secp256k1 cryptographic library. It replaces a custom version-check macro with a simpler check for whether the compiler is GCC (or claims to be GCC, like Clang). The change does not fix a security bug and does not introduce a clear vulnerability; it removes support for very old GCC versions that are no longer targeted.

This commit is a simple code cleanup: it moves an #include directive from one internal file to another so that each file only imports what it actually uses. There is no functional change, no bug fix, and no security relevance.

This commit removes an unused internal compiler-version-checking helper macro from the public header file. It is a cleanup change with no security implications. The commit message notes it is technically a breaking change for any external code that might have relied on this macro, but the authors do not expect such usage.

This commit is a performance optimization for Bitcoin's secp256k1 cryptographic library. It tells the compiler to always inline (embed directly into calling code) certain low-level multiplication and squaring routines used heavily in elliptic-curve operations. The stated goal is faster signature verification and key agreement, at the cost of slightly larger compiled binaries. There is no security fix or vulnerability indicated in the commit itself.

This commit only changes compiler warning settings inside the project's test code. It turns on a warning for unused functions so the test suite catches dead code. It does not change any actual security logic, cryptography, or runtime behavior of the library.

This commit adds a new unit test to verify that two internal math functions in the secp256k1 library produce matching results. It does not change any production code, cryptographic logic, or fix a bug. It is purely a test addition.

This is a one-line fix in a test file. The original code called a function that checks whether a point is infinity but threw away the result, so the check did nothing. The fix wraps it in a CHECK() macro so the test actually verifies the result. It does not change any production code and has no security impact on real users.

This commit fixes how the shared library version number is set when building on OpenBSD. It adds an OpenBSD-specific branch in the CMake build logic so the library gets a proper version suffix. There is no direct security vulnerability here; it is a portability/build correctness fix. A wrong version could theoretically cause runtime linker confusion or load an unintended library, but the commit itself is defensive and small.

This commit fixes how version numbers are assigned to the shared library when building on NetBSD. It is a build-system portability fix with no apparent security relevance.

This commit only improves comments and documentation inside a CMake build script. It does not change any actual build behavior or code that runs in the library. There is no security issue here.

This commit is a straightforward cleanup of the build system. It moves existing logic for setting shared-library version numbers into a reusable CMake helper module, without changing the actual version-numbering behavior. There is no security-relevant change.

This commit is a minor cleanup in the project's internal test code. It replaces a two-step pattern (compute a point in one coordinate format, then convert it to another) with a single helper function that does the same thing. The author explicitly calls it a refactor and notes the only behavioral difference is that an intermediate variable is now cleared, which has no effect on test logic. There is no indication this changes any production cryptography or introduces a security issue.

This commit is a simple rename of an internal function from `secp256k1_ecmult_gen` to `secp256k1_ecmult_gen_gej` across six files. The change is purely cosmetic and intended to make the function name consistent with a newly added variant. No behavior, logic, or security properties of the code are changed.

This is a defensive code cleanup in a Bitcoin cryptography library. It introduces a helper function that wraps a common three-step pattern when multiplying by the generator point, ensuring that temporary sensitive Jacobian coordinate data is always wiped from memory. The change reduces the chance that a future developer forgets to clear that temporary data, which could theoretically leak tiny fragments of secret key information through memory side channels. It does not fix a known active bug or reported vulnerability.

This commit only adds a new internal performance benchmark for a low-level math helper function (secp256k1_fe_normalize_var). It does not change any cryptographic logic, library behavior, or user-facing code. There is no security issue here.

This commit only adds a new test file that exhaustively checks the ECDH (Elliptic Curve Diffie-Hellman) module. It does not change any production code, cryptographic logic, or build behavior for end users. There is no security vulnerability here; it is purely a test-suite improvement.