libsecp256k1

This is a tiny internal code cleanup in a Bitcoin cryptography library. It removes an unnecessary intermediate variable and replaces it with direct 'return 1' and 'return 0' statements. The function's behavior is unchanged, and there is no security issue.

This commit only adds new test cases to the project's test suite. It checks that several public-key and signature functions correctly reject arrays that contain a NULL pointer. There are no changes to the actual library code, so this does not fix or introduce a security issue by itself. It is a hardening of the test coverage for existing API behavior.

This commit adds safety checks to several Bitcoin libsecp256k1 functions that accept arrays of pointers. Previously, if a caller passed an array containing a NULL (empty) pointer, the code might read from or process an invalid memory location, potentially causing a crash or unpredictable behavior. The new checks reject such inputs cleanly before any processing begins. It is a defensive hardening fix rather than a confirmed exploitable vulnerability.

This commit only changes the text of error messages in the benchmark program. It replaces specific outdated build instructions (referencing the old Autotools ./configure command) with a generic pointer to README.md, because the project now uses CMake. There is no change to cryptographic code, no security fix, and no vulnerability.

This commit only updates the `.gitignore` file, which tells Git which files and folders to ignore. It broadens the pattern for CMake build directories so more variations (like `build`, `build-release`, etc.) are ignored. There is no code change and no security impact.

This commit simply renames the Autotools helper directory from 'build-aux' to 'autotools-aux' and updates the related references in build files and .gitignore. It is a build-system housekeeping change with no effect on the cryptographic code or runtime security.

This commit removes an unused internal helper function for serializing public keys and updates the test code to use two newer, more specific helper functions instead. There is no indication of a security bug being fixed; it appears to be a routine code cleanup.

This commit is a small internal cleanup in the Bitcoin Core secp256k1 cryptography library. It replaces several verbose public-key serialization calls with simpler, purpose-built helper functions that always produce 33-byte compressed public keys. There is no indication this fixes a security bug; it appears to be a code-quality refactor that removes redundant error checks and boilerplate.

This is a small internal code cleanup in the Bitcoin Core secp256k1 library. It changes how public keys are converted to bytes in one public function, replacing a single flexible helper with two fixed-size helpers. There is no indication of a security bug being fixed.

This commit adds two new internal helper functions for converting elliptic-curve points into the standard 33-byte compressed and 65-byte uncompressed public-key formats. It is a straightforward code-organization change with no visible security relevance.

This change is a routine cleanup of the project's automated macOS testing configuration. It makes the 'symbol check' step use a Python virtual environment consistently across two similar jobs and removes a duplicate copy of the same script. There is no security-relevant change to the actual Bitcoin/libsecp256k1 code, no fix for a vulnerability, and no indication of a security issue.

This commit is a code-cleanup change in Bitcoin Core's libsecp256k1 cryptographic library. It replaces direct reads and writes of an internal 'infinity' flag on elliptic-curve points with calls to dedicated helper functions. The stated goal is to hide the internal field from other modules, making future mistakes less likely. There is no direct evidence in the commit that this fixes an exploitable vulnerability, but it is a defensive hardening change in security-critical code.

This is a tiny code cleanup in a benchmark program. It replaces a hardcoded number (16) with a named constant (ALIGNMENT) when calculating memory size. There is no security issue here.

This commit is a straightforward memory optimization for a cryptographic calculation routine. It reduces the amount of temporary memory used during batch elliptic-curve multiplications by storing intermediate values in smaller integer types. There is no indication of a security bug being fixed.

This commit only changes the version of the macOS virtual machine used by the project's automated testing system. It replaces an older, soon-to-be-retired macOS test image with a newer one. There is no change to the actual cryptographic code, no bug fix, and no security-relevant behavior change.

This commit simply removes a workaround in the continuous integration (CI) script that added a compiler flag for older versions of Valgrind. It does not change any cryptographic code, wallet logic, or network behavior, and has no direct security impact on the library itself.

This is a minor GitHub Actions CI cleanup. It removes a default shell command from a reusable workflow action and instead makes callers explicitly provide the command. There is no security-relevant change to the actual Bitcoin cryptography code or to how containers are built or executed.

This change is a routine cleanup of the project's automated testing configuration file. It replaces repeated copies of the same CI step with YAML anchors and aliases, which is purely a maintainability improvement. There is no change to the actual commands run, the software code, or any security-sensitive behavior.

This is a routine cleanup of the project's automated testing configuration. It renames and restructures how environment variables are grouped in GitHub Actions workflow files so the setup is more consistent across different test jobs. There is no change to the actual cryptographic code, no new capability for an attacker, and no security fix.

This commit is a routine cleanup of the project's automated testing configuration file. It replaces several copy-pasted 'Print logs' steps with a single reusable template reference, making the file shorter and easier to maintain. There is no change to the actual software code, no change to how tests run, and no security relevance.

This commit simply updates the version of a GitHub-provided action used to check out source code during automated testing. There is no indication of a security vulnerability or code change affecting the secp256k1 library itself.

This commit is a routine cleanup of the project's automated testing configuration file. It replaces many repeated copies of the same 'checkout the code' step with a single shared template reference. There is no change to the actual software code, no change to security settings, and no security relevance.

This change updates the project's automated testing setup. It adds a second compiler ('clang-snapshot', a preview version of the next Clang release) to the MemorySanitizer (MSan) CI job and installs an extra compiler support package needed by that snapshot compiler. There is no change to the cryptographic library code itself, no bug fix, and no security patch.

This is a build-system hygiene patch that suppresses a compiler warning in test-only sanitizer code. It does not change runtime behavior, fix a vulnerability, or affect how Bitcoin/crypto operations work. The change only tells Clang 21+ to ignore a new warning when using MemorySanitizer during tests.

This change only adjusts how a Docker container used for automated testing installs Debian packages. It sets an environment variable that tells Debian's package installer not to prompt for user input, which simply removes harmless warning messages during automated builds. There is no security issue here.