libsecp256k1

This commit changes a GitHub Actions CI setting to stop Docker from printing extra build summary messages. It is a cosmetic/workflow cleanup change with no security relevance.

This commit is a straightforward code cleanup: it removes unnecessary type casts in front of memory allocation calls like malloc. In modern C, casting the result of malloc is not needed and is generally discouraged. The change does not alter program behavior, fix a bug, or address a security issue. It touches mostly test and benchmark code, with only two small changes in production functions that create or clone a cryptographic context.

This commit adds a new compiler warning flag that alerts developers when source code lines begin with spaces instead of tabs. It is a code-style/build-hygiene change only and does not alter any runtime behavior, fix any vulnerability, or change how the library processes cryptographic data.

This commit only adds a new compiler warning flag that flags trailing whitespace in source code. It is a code-quality/build-hygiene change, not a security fix. The only functional code change is a pragma to suppress that warning around a system header (Valgrind's memcheck.h) that may contain trailing whitespace. There is no vulnerability being patched.

This commit only removes invisible trailing spaces at the ends of three lines across three source files. It does not change any program logic, function behavior, or security properties. There is no security relevance.

This commit adds a weekly timer to the project's GitHub Actions CI workflow so tests run automatically every Monday morning. It is purely an infrastructure/maintenance change and does not modify any cryptographic code, build scripts, or user-facing behavior.

This commit changes how Bitcoin Core's libsecp256k1 project manages its automated build cache for Docker images. It makes the cache key include the current week number divided by 4, so the cache is effectively thrown away and rebuilt about once a month. This is a routine maintenance improvement to avoid relying on stale cached build layers forever. It is not a security fix and does not change any cryptographic or network code.

This commit changes a CI Docker build script so that an older SHA-1-based PGP signature from the LLVM apt repository is still accepted. It is a build-infrastructure workaround, not a change to the secp256k1 cryptographic code, and it does not introduce a vulnerability in the library itself.

This commit is a one-line update to the project's internal release-process documentation. It reminds maintainers to add a matching '[Unreleased]' hyperlink at the bottom of the changelog, not just the section header. There is no code change, no cryptographic change, and no security relevance.

This commit is a routine post-release housekeeping change. It bumps the project's version number from 0.7.1 to 0.7.2, marks the current code as an unreleased development snapshot, and updates the changelog accordingly. There are no code behavior changes, no bug fixes, and no security implications.

This commit is purely a release bookkeeping change. It renames the 'Unreleased' section in the changelog to version 0.7.1, adds an ABI compatibility note, and flips a build flag from 'not a release' to 'is a release'. No code behavior changes and no security fix is introduced here.

This commit only updates the project's CHANGELOG.md file in preparation for a release. It documents two prior fixes: one that tries harder to scrub cryptographic secrets from memory, and one that fixes a build configuration issue where strict compiler flags could accidentally disable optimized assembly code. The commit itself does not change any source code, so it cannot introduce or fix a vulnerability directly.

This commit improves error handling in the benchmark programs only. It makes the benchmark tools reject invalid or non-positive values for the SECP256K1_BENCH_ITERS environment variable instead of silently using a bad value. This is a hardening/robustness fix for developer tooling, not a security fix for the cryptographic library itself.

This commit only changes the wording of an error/help message in a test program. It tells users how to run a test under valgrind for both CMake and Autotools builds. There is no security issue here.

This commit only adds descriptive labels to test cases in the project's CMake build configuration. It does not change any cryptographic code, runtime behavior, or security-sensitive logic. There is no security issue here.

This commit is a routine build-system cleanup. It changes how CMake names and discovers test cases, switching from underscores to dots in test names and using a helper module to automatically find individual tests inside test executables. There is no change to the cryptographic code, no bug fix, and no security relevance.

This commit adds mathematical self-checks (assertions) to a SageMath script used to generate internal constants for Bitcoin's secp256k1 library. It does not change any runtime code, cryptographic operations, or user-facing behavior. It only verifies that precomputed GLV constants correctly relate to a known algebraic factorization involving Eisenstein integers. There is no security vulnerability or fix here.

This commit adds a new CMake helper file used to automatically find and register test cases during the build process. It does not change any cryptographic code, wallet handling, network logic, or user-facing behavior. It is purely a build/test infrastructure addition.

This commit is a straightforward cleanup of the project's build instructions. It replaces two nearly identical blocks of CMake code with a single reusable function that creates test programs. There is no change to the actual cryptographic code, no change to what tests are run, and no indication of any security issue being fixed.

This commit only updates the help text and a printed message in a benchmark program. It does not change any cryptographic code, library behavior, or security-sensitive logic. There is no security issue here.

This commit changes two variable types from signed integers (int) to unsigned size types (size_t) inside a low-level elliptic-curve multiplication helper. It is a code-quality/correctness cleanup with no observable security effect: the values are always non-negative and small, and the change does not fix a bug that could be triggered by an attacker.

This commit changes several loop counters and a macro from signed 'int' or 'long' types to unsigned 'size_t' when indexing into precomputed elliptic-curve multiplication tables. The main practical effect is to avoid undefined behavior or incorrect results on platforms where the table size calculation could overflow a signed type, and to make the code's intent clearer. There is no direct evidence in the commit that this fixes an exploitable vulnerability in normal Bitcoin Core usage, but it is a defensive correctness improvement in low-level cryptographic code.

This is a one-line documentation update in a header file comment. It adds the CMake equivalent of an existing Autotools build option so developers know how to enable external default callbacks when building with CMake. No code behavior changes.

This commit is a pure test-code refactoring. It takes one large ElligatorSwift test function and splits it into eight smaller, independent test functions so the test runner can execute them in parallel. The commit message explicitly says 'No behavior changes,' and the diff only moves existing loops and checks into separate functions without altering the test logic, constants, or production code. There is no security issue here.

This commit adds safety checks and documentation to ensure that 'flag' values used in secret-handling code are exactly 0 or 1, not just any 'true' value. These flags control constant-time selection and memory wiping. If a caller passed a different non-zero value, the masking math could behave incorrectly and potentially leak secret information through timing or produce wrong results. The new checks only fire in special VERIFY builds, so they are a defensive hardening measure rather than a fix for an active bug.