BC
← All projectsBitcoin Core

libsecp256k1

High-assurance secp256k1 elliptic-curve library used throughout the Bitcoin ecosystem.

BitcoinCryptographic librariesNormal
Repository coverage

257 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

85security candidates7second-pass queue215AI analyses
27commits · 30 days
53commits · 60 days
152commits · 180 days
206commits · 365 days
Backfill bands
Aug 5 → Feb 682 seen1 candidatesComplete
Feb 6 → Jun 625 seen2 candidatesComplete
Jun 6 → Jul 619 seen1 candidatesComplete
Jul 6 → Aug 548 seen1 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

72/100 average clarity
100Strong · 80–100
89Adequate · 60–79
64Thin · 40–59
4Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
merge-script482426193
Sebastian Falbesoner502145068
Hennadii Stepanov51746064
Tim Ruffing22622055
furszy13413087
josibake949066
Lőrinc13313077
kevkevinpal626064
Ferdinando Ametrano522074
John Moffett424069
copilot-swe-agent[bot]323074
Bruno Garcia322090
Analysis record

Published AI watches

Last scanned 25 minutes ago

Informational 21 AI analysisMessage 81 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1980: examples: randomize the context in musig, erase the keypair in schnorr

This change improves two example programs in the secp256k1 cryptographic library. It adds a recommended side-channel protection step to the multi-signature example (musig.c) and ensures the single-signature example (schnorr.c) also wipes a…

Context randomization added to protect against side-channel leakageSecret key material explicitly erased from keypair object after useChanges are confined to example code, not the core library
5959bed6by merge-script+14−12 files
No security note in commit
Low 36 AI analysisMessage 98 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1998: Avoid unsequenced accesses to volatile variables

This change fixes a subtle compiler-warning/undefined-behavior issue in the code that performs secret math inside Bitcoin's cryptographic library. The code uses 'volatile' variables to prevent the compiler from turning certain operations i…

Touches constant-time arithmetic paths (modular inversion normalization)Fixes undefined behavior involving volatile-qualified variablesCompiler warning (-Wunsequenced) treated as a correctness defect
a0e2e23aby merge-script+42−362 files
Vendor flagged security relevance
Low 32 AI analysisMessage 80 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Avoid unsequenced accesses to volatile variables

This commit fixes a subtle C language rule violation in Bitcoin Core's libsecp256k1 cryptographic library. The code was reading a special 'volatile' variable multiple times within the same expression, which modern C standards treat as unde…

Undefined behavior in cryptographic constant-time codeCompiler warning (-Wunsequenced) in security-critical pathVolatile variable used as constant-time execution barrier
e7a34ba3by Hennadii Stepanov+20−142 files
No security note in commit
Informational 16 AI analysisMessage 100 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1898: tests: Silent Payments ctime test never reaches a match or label lookup

This commit fixes a flawed test in the libsecp256k1 cryptographic library. The test was supposed to exercise the Silent Payments constant-time scanning code, but due to a bug in how the test was written, it never actually verified that the…

Test-only change in ctime_tests.cFixes incorrect test key mutation that prevented matching outputAdds label callback to exercise label-candidate serialization/batching path
5d2ff536by merge-script+27−131 file
No security note in commit
Informational 15 AI analysisMessage 98 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

ci: Run the Wine jobs on ubuntu-24.04

This is a routine continuous-integration (CI) maintenance change. It pins a Windows cross-compilation test job to an older Ubuntu version because the newer GitHub-hosted runner image breaks Wine's networking syscalls. There is no change to…

ecfe7ab8by Ferdinando Ametrano+2−11 file
No security note in commit
Informational 23 AI analysisMessage 96 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1986: examples: exit with failure if signature verification fails

This change fixes two example programs so they return a failure code when a signature check fails. Previously, the examples always reported success even if verification failed, which meant automated tests would pass even when the underlyin…

Incorrect return status masked verification failures in example/test programsAutomated tests would pass despite cryptographic verification failingFix aligns ECDSA and Schnorr examples with existing MuSig example behavior
b97f7f5fby merge-script+2−22 files
No security note in commit
Informational 18 AI analysisMessage 88 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

examples: exit with failure if signature verification fails

This is a small hardening fix to two example programs. Previously, the example programs for ECDSA and Schnorr signatures would print whether a signature was valid but always report success to the operating system. Because the project's bui…

Test/example code silently succeeded on verification failureRegression-test gap for signature verification behaviorFix hardens CI/test signal without changing cryptographic logic
900613a7by Amartya Singh+2−22 files
No security note in commit
Low 35 AI analysisMessage 96 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1974: silentpayments: reject label tweaks that overflow the group order

This change fixes a silent handling problem in Bitcoin's silent payments feature. When a user-supplied label tweak value was larger than the cryptographic group order, the code previously reduced it silently, which could lead to incorrect …

silent modular reduction of attacker/caller-controlled scalarAPI misuse now rejected via ARG_CHECKsensitive scalar clearing before early return to avoid leaking transaction indistinguishability data
1c088b64by merge-script+13−22 files
Vendor flagged security relevance
High 76 AI analysisMessage 86 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1983: silentpayments: return 0 instead of `ARG_CHECK`ing for empty inputs/outputs

This update fixes a crash risk in Bitcoin's silent payments scanning code. Before the change, if a transaction had no suitable inputs or no taproot outputs, the library treated that as an illegal argument and could call abort(), killing th…

Denial-of-service vector: maliciously crafted transaction could trigger abort() in a scanning/indexing processAPI contract violation: documented return-0 behavior was not implemented for empty inputs/outputsARG_CHECK removal in two public silentpayments functions
a3a5cd45by merge-script+46−334 files
Vendor flagged security relevance
Low 30 AI analysisMessage 73 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: allow NULL arrays in scan_outputs if n_tx_outputs is 0

This commit fixes a minor API usability issue in the experimental silent payments module. Previously, a function that scans transaction outputs for silent payments would crash if given empty arrays represented as NULL pointers, even though…

NULL pointer argument check relaxed for empty arraysSECP256K1_ARG_NONNULL attributes removed for two parametersNew API test verifying NULL-with-zero-length behavior
e7bb0112by Sebastian Falbesoner+18−113 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: return 0 instead of `ARG_CHECK`ing for empty inputs/outputs

This change fixes two functions in the Silent Payments module so they return a normal failure value (0) instead of triggering an internal abort when given a transaction with no eligible inputs or no taproot outputs. Previously, callers sca…

ARG_CHECK default behavior is abort(), turning an expected non-Silent-Payments transaction into a potential DoS crashAPI contract promised return 0 for non-Silent-Payments transactions, but implementation violated it for empty input/output edge casesCallers scanning blocks would need special-case handling before the fix to avoid crashes
d7821f4aby Sebastian Falbesoner+27−223 files
Vendor flagged security relevance
Low 31 AI analysisMessage 100 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: reject label tweaks that overflow the group order

This change tightens error handling in the silent payments scanning code. Previously, if a caller-supplied label tweak was as large as or larger than the elliptic curve group order, it was silently wrapped around (reduced modulo the order)…

silent reduction modulo group order replaced with explicit overflow rejectionsensitive scalars and shared secret explicitly cleared before aborting on invalid inputoutput assignment reordered to avoid partial state update on failure path
95552e16by Sebastian Falbesoner+13−22 files
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

remove unused SECP256K1_GE_CONST_INFINITY

This commit simply deletes an unused macro named SECP256K1_GE_CONST_INFINITY from a header file. A macro is a shorthand definition for code, and this one was no longer referenced anywhere in the project. Removing dead code has no functiona…

7b59e1fcby fanquake+0−11 file
No security note in commit
Low 26 AI analysisMessage 100 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1929: silentpayments: perform tweak addition with actual scalars

This change simplifies how Silent Payments scanning adds a small tweak value to a secret-derived value. It replaces a function meant for secret-key tweaking with plain scalar (modular number) addition. The old code had a special case that …

Behavior change: zero-result tweak addition is no longer forced to zero; scalar addition allows zeroBehavior change: label tweaks >= group order N are no longer rejected by the secret-key APIRemoval of defensive comment explaining failure modes of secret-key tweak addition
04b91ce2by merge-script+7−161 file
No security note in commit
Informational 15 AI analysisMessage 86 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1963: doc: say the sha256 compression callback processes secrets

This commit only adds a documentation comment to a public header file. It reminds developers that a special callback function used for SHA256 hashing may receive secret data such as private keys, so any custom implementation must be consta…

31716e4bby merge-script+3−01 file
No security note in commit
Informational 18 AI analysisMessage 81 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

doc: say the sha256 compression callback processes secrets

This is a documentation-only change. It adds a warning to the public header file telling developers that the optional SHA256 compression callback may receive secret key material, and therefore any custom implementation must run in constant…

Documentation clarifies that a pluggable cryptographic callback receives secret materialDocumentation imposes constant-time and no-logging requirements on callback implementersReferences RFC 6979 nonce derivation as an example of secret-key processing
494d3053by Ferdinando Ametrano+3−01 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 96 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1946: doc: clean up lingering ECMULT_WINDOW_SIZE comment

This is a documentation-only cleanup. It moves a comment about the ECMULT_WINDOW_SIZE setting to a better location and fixes an outdated formula in the comment. No code behavior changes.

6f065e9aby merge-script+10−112 files
No security note in commit
Low 37 AI analysisMessage 100 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1933: refactor: introduce `ecmult_const_ge` helper (preventing accidential gej leaks)

This commit is a defensive code cleanup in Bitcoin Core's secp256k1 cryptography library. It introduces a helper function that automatically clears temporary secret data after a constant-time elliptic curve multiplication, and switches exi…

Defensive refactoring to prevent accidental leakage of secret scalar information from Jacobian coordinatesNew helper enforces memory clearing of intermediate group element after constant-time scalar multiplicationAdoption in ECDH and silentpayments modules, which process secret keys
2365dc64by merge-script+35−427 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 93 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1949: ecdsa: Clarify derivation of the r check in `_sig_verify`

This commit only rewrites comments in the source code to make the mathematical explanation clearer. It does not change any actual code instructions, function behavior, or security properties. There is no vulnerability or fix here.

4a264a93by merge-script+21−151 file
No security note in commit
Informational 12 AI analysisMessage 100 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1948: tests: add ECDSA verify case where r + n overflows p

This commit only adds a new test case to the project's test suite. It does not change any production cryptographic code. The new test verifies that the ECDSA signature verification function correctly rejects a crafted invalid signature in …

Adds test coverage for ECDSA verification edge case involving r + n overflow against field order pReferences a surviving mutant where the early-rejection check in secp256k1_ecdsa_sig_verify is removedDoes not modify production code; purely a test-suite enhancement
e23e9201by merge-script+28−01 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityci: Drop workaround for Valgrind older than 3.20.0by Hennadii Stepanov · c09519f0 · Oct 15, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Drop workaround for Valgrind older than 3.20.0

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

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.

Lower-priorityci: Drop default for `inputs.command` in `run-in-docker-action`by Hennadii Stepanov · 15d01480 · Oct 14, 2025 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Drop default for `inputs.command` in `run-in-docker-action`

This change decreases coupling.

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci: Use YAML anchor and aliases for repeated "CI script" stepsby Hennadii Stepanov · 1decc49a · Oct 14, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Use YAML anchor and aliases for repeated "CI script" steps

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci, refactor: Generalize use of `matrix.configuration.env_vars`by Hennadii Stepanov · dff1bc10 · Oct 14, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Hennadii Stepanov

ci, refactor: Generalize use of `matrix.configuration.env_vars`

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci: Use YAML anchor and aliases for repeated "Print logs" stepsby Hennadii Stepanov · 4b644da1 · Oct 14, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Use YAML anchor and aliases for repeated "Print logs" steps

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci: Bump `actions/checkout` versionby Hennadii Stepanov · a889cd93 · Oct 14, 2025 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · Hennadii Stepanov

ci: Bump `actions/checkout` version

See https://github.com/actions/checkout/releases.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci: Use YAML anchor and aliases for repeated "Checkout" stepsby Hennadii Stepanov · 574c2f30 · Oct 14, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Use YAML anchor and aliases for repeated "Checkout" steps

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

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.

Lower-priorityci: Use clang-snapshot in "MSan" jobby Hennadii Stepanov · 53585f93 · Oct 14, 2025 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Hennadii Stepanov

ci: Use clang-snapshot in "MSan" job

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

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.

Lower-priorityFix Clang 21+ `-Wuninitialized-const-pointer` warning when using MSanby Hennadii Stepanov · 6894c964 · Oct 14, 2025 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

Fix Clang 21+ `-Wuninitialized-const-pointer` warning when using MSan

Co-authored-by: Tim Ruffing <me@real-or-random.org>

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
AI analysis · Informational 15/100

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.

Lower-priorityci: Set `DEBIAN_FRONTEND=noninteractive`by Hennadii Stepanov · f163c358 · Oct 13, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Set `DEBIAN_FRONTEND=noninteractive`

This suppresses `debconf: unable to initialize frontend: ...` warnings.

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI analysis · Informational 15/100

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.

Lower-priorityci: Bump `docker/build-push-action` versionby Hennadii Stepanov · 70ae177c · Oct 13, 2025 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · Hennadii Stepanov

ci: Bump `docker/build-push-action` version

See https://github.com/docker/build-push-action/releases.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates a GitHub Actions helper used to build Docker containers from version 5 to version 6. It is a routine maintenance change to the project's continuous integration (CI) configuration and does not alter the cryptographic library code, build scripts, or any software that end users run.

Lower-priorityci: Drop `tags` input for `docker/build-push-action`by Hennadii Stepanov · b2a95a42 · Oct 13, 2025 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Drop `tags` input for `docker/build-push-action`

The `tags` input is unused for caching.

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This is a routine cleanup of the project's automated CI (Continuous Integration) configuration. It removes an unused 'tag' input from GitHub Actions Docker build steps and switches to referencing the most recently built Docker image by ID instead of by tag. There is no security issue here.

Lower-priorityci: Add `scope` parameter to `cache-{to,from}` optionsby Hennadii Stepanov · 122014ed · Oct 13, 2025 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

ci: Add `scope` parameter to `cache-{to,from}` options

This change fixes an issue where only the latest image cache was
available.

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit changes how Bitcoin Core's libsecp256k1 project caches Docker images in its automated testing system. It adds a 'scope' label to GitHub Actions cache settings so that separate caches are kept for different CPU architectures (like x86_64 vs ARM). Previously, all architectures shared one cache, meaning only the most recently used image was kept. This is a CI infrastructure improvement, not a security fix.

Lower-prioritytest: add --log option to display tests executionby furszy · 2f4546ce · Oct 1, 2025 · 2 filesMessage 82 · StrongInformational 15Details
Commit message · furszy

test: add --log option to display tests execution

When enabled (--log=1), shows test start, completion, and execution time.

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit adds a new optional '--log=1' command-line flag to the project's internal test runner so users can see when each test starts, finishes, and how long it took. It also adds a small safety check to make sure the test framework is initialized before tests are run. There is no change to cryptographic code, no network code, and no behavior that affects normal users of the library.

Lower-prioritytest: support running specific tests/modules targetsby furszy · 953f7b00 · Oct 1, 2025 · 2 filesMessage 95 · StrongInformational 15Details
Commit message · furszy

test: support running specific tests/modules targets

Add support for specifying single tests or modules to run via the
"--target" or "-t" command-line option. Multiple targets can be
provided; only the specified tests or all tests in the specified
module/s will run instead of the full suite.

Examples:
-t=<test name> runs an specific test.
-t=<module name> runs all tests within the specified module.

Both options can be provided multiple times.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit adds a new command-line option (-t or --target) to the project's internal test runner so developers can run a single test or a whole module instead of the entire test suite. It is a testing convenience feature with no apparent security relevance.

Lower-prioritytest: Add option to display all available testsby furszy · 95b9953e · Oct 1, 2025 · 2 filesMessage 94 · StrongInformational 15Details
Commit message · furszy

test: Add option to display all available tests

Useful option to avoid opening the large tests.c file just to find
the test case you want to run.

94/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit adds a simple command-line option to the project's test runner that prints a list of all available tests and modules. It is a pure test-infrastructure convenience feature with no effect on the cryptographic library or any production code paths.

Lower-prioritytest: add --help for command-line optionsby furszy · 0302c1a3 · Oct 1, 2025 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · furszy

test: add --help for command-line options

Add a help message for the test suite, documenting available options,
defaults, and backward-compatible positional arguments.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit adds a --help / -h command-line option to the project's internal test suite. It simply prints usage instructions and exits. There is no security-relevant change to any cryptographic code, network handling, or production library behavior.

Lower-prioritytest: adapt modules to the new test infrastructureby furszy · 9ec3bfe2 · Oct 1, 2025 · 8 filesMessage 95 · StrongInformational 15Details
Commit message · furszy

test: adapt modules to the new test infrastructure

This not only provides a structural improvement but also
allows us to (1) specify individual tests to run and (2)
execute each of them concurrently.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit is purely a test-code refactoring. It reorganizes how the project's test cases are registered and run, allowing individual tests to be selected and run in parallel. No production cryptographic code is changed, and there is no indication this fixes or introduces a security vulnerability.

Security candidatetest: introduce (mini) unit test frameworkby furszy · 48789daf · Oct 1, 2025 · 6 filesMessage 95 · StrongInformational 15Details
Commit message · furszy

test: introduce (mini) unit test framework

Lightweight unit testing framework, providing a structured way to define,
execute, and report tests. It includes a central test registry, a flexible
command-line argument parser of the form "--key=value" / "-k=value" /
"-key=value" (facilitating future framework extensions), ability to run
tests in parallel and accumulated test time logging reports.

So far the supported command-line args are:
- "--jobs=<num>" or "-j=<num>" to specify the number of parallel workers.
- "--seed=<hex>" to specify the RNG seed (random if not set).
- "--iterations=<num>" or "-i=<num>" to specify the number of iterations.

Compatibility Note:
To stay compatible with previous versions, the framework also supports
the two original positional arguments: the iterations count and the
RNG seed (in that order).

95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Informational 15/100

This commit is a pure test-infrastructure change. It introduces a small internal unit-test framework for the secp256k1 cryptographic library, replacing a long hand-written main() function with a registry of test cases and adding optional parallel test execution. It does not change any cryptographic code, public API, or production behavior, and it does not fix or introduce any security vulnerability.

Security candidatedocs: Improve API docs of _context_set_illegal_callbackby Tim Ruffing · 4d90585f · Sep 22, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Tim Ruffing

docs: Improve API docs of _context_set_illegal_callback

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only changes documentation comments in a header file. It rewords descriptions of error and illegal-argument callbacks, fixes typos, and clarifies wording. No executable code, build system, or API behavior was changed, so it has no security impact on its own.

Security candidatedocs: Clarify that callback can be called more than onceby Tim Ruffing · 895f53d1 · Sep 22, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Tim Ruffing

docs: Clarify that callback can be called more than once

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only changes a documentation comment in a header file. It clarifies that if a user-supplied error callback returns instead of aborting, the API call's results are undefined and the callback may be triggered more than once. No code behavior was changed.

Security candidatebuild: Fix warnings in x86_64 assembly checkby Hennadii Stepanov · ab560078 · Sep 18, 2025 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Hennadii Stepanov

build: Fix warnings in x86_64 assembly check

This change fixes:
- `-Wuninitialized` in both Autotools and CMake;
- `-Wreturn-type` in CMake only.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit fixes compiler warnings in build-system tests that detect whether x86_64 assembly can be used. It initializes a variable and adds a return statement to a small test program. These changes do not affect the actual cryptographic code, runtime behavior, or security of the library.

Lower-prioritybench: improve context creation in ECDH benchmarkby Sebastian Falbesoner · dfe284ed · Sep 16, 2025 · 1 fileMessage 68 · AdequateInformational 17Details
Commit message · Sebastian Falbesoner

bench: improve context creation in ECDH benchmark

Calling `secp256k1_context_create` with `SECP256K1_FLAGS_TYPE_CONTEXT`
seems to be not strictly API-compliant, as the only allowed
(non-deprecated) value is `SECP256K1_CONTEXT_NONE`, even if the
former happens to map to the latter currently.

Fix this by not dynamically creating a context in the first place and
switch to using the static context, as it is sufficient for this
benchmark and presumably matches what the "no capabilities" comment
intended back then.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 17/100

This is a small cleanup in a benchmark test file for the ECDH module. It replaces a dynamically created cryptographic context with a pre-built static one and removes the matching cleanup call. The change is about making the benchmark follow the intended API more cleanly; it does not fix an exploitable vulnerability in production code.

Security candidatedoc: clarify API doc of `secp256k1_ecdsa_recover` return valueby Jonas Nick · 7321bdf2 · Sep 16, 2025 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Jonas Nick

doc: clarify API doc of `secp256k1_ecdsa_recover` return value

Co-authored-by: Tim Ruffing <me@real-or-random.org>

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only updates the documentation comments for a function in a header file. It clarifies what the return value of secp256k1_ecdsa_recover means and explains a subtle detail about signature normalization after converting a recoverable signature. No code logic was changed, so there is no security vulnerability or fix here.

Lower-priorityrefactor: move 'gettime_i64()' to tests_common.hby furszy · 9cce7038 · Sep 13, 2025 · 3 filesMessage 100 · StrongInformational 15Details
Commit message · furszy

refactor: move 'gettime_i64()' to tests_common.h

Relocate the clock time getter to tests_common.h to
make it easily reusable across test programs. This
will be useful for the upcoming unit test framework.

Context - why not placing it inside testutil.h?:
The bench program links against the production-compiled library,
not its own compiled version. Therefore, `gettime_i64()` cannot
be moved to testutil.h, because testutil.h calls
`secp256k1_pubkey_save()`, which exists only in the internal
secp256k1.c and not in the public API.

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit is a simple code cleanup: it moves a small helper function that reads the system clock from one internal test/benchmark header file to a new shared test header file. There is no change to the cryptographic library, no change to how Bitcoin transactions or keys are handled, and no security fix or vulnerability introduced.