121 Commits

Author	SHA1	Message	Date
Kgothatso Ngako	7a35fde10f	frost_enrollment: correct the zeroing contract and harden the CI guard ... The two findings from the second review round, plus the coverage gap and comment error it noted. Finding 8: the zeroing exception was narrower in the docs than in the code. The previous commit's fix leaves shares32_out untouched on EVERY params_are_valid rejection -- duplicate ids, threshold < 2, new_id among the helpers, an id >= n, the mode bounds -- but the header scoped the exception to "when n_ids itself is out of range", and frost_enrollment.md still said flatly that outputs are zeroed on every failure path. A caller who inspects the buffer after a failed call would, on a duplicate-id or t = 1 rejection, read whatever was there before. In this protocol that can be additive shares of a secret from an earlier call. Both now state the actual invariant: not written when the parameter tuple is rejected, because its extent is only known to be u*32 once n_ids has been validated against the rest of the tuple; zeroed on every failure found after that point (an unusable thresh_pk, my_id not among the helpers, an invalid secret share). The .md adds the sentence a defensive caller needs: treat a rejected tuple as leaving the buffer unmodified, not as leaving it zeroed. Documentation only -- the implementation and the tests already agreed with this reading. Finding 9: the new CMake CI step never checked that the modules landed. It configured, built and installed with all five module flags, then ran `ls -RlAh` -- which prints and does not assert -- and linked examples/ecdsa.c, which uses core symbols only. Deleting the add_compile_definitions or PUBLIC_HEADER line for a module during an upstream sync would keep the step green: no module code means no undefined references, and the install simply omits the header. The guard added one commit ago caught a MISORDERED block but not a MISSING one. The step now asserts both halves. `ls` of all five module headers fails the step under bash -e if any is absent, and examples/frost_enrollment.c is compiled and run against the installed library, which no header-only check would cover -- it needs the symbols to actually be in the library. Verified by running the step's exact command sequence under bash -e: it exits 0 as written, and against an install configured WITHOUT the modules the header assertion exits 2 and the example fails to compile on the missing include. Coverage: the params-hash attribution path was still only tested where identifier equals index. The previous commit pinned identifier semantics for the scalar-overflow path on helper set {0, 2}, but share_agg's other `*mismatch_id = ids[i]` -- the parameters-hash disagreement -- was exercised only on {0, 1}. It is now pinned on {1, 3}, corrupting each slot in turn so the mapping is fixed at both ends: index 0 must report 1, index 1 must report 3. Verified load-bearing by changing the assignment to `(uint32_t)i`, which fails the new case. Comment error: the {0, 2} overflow case carried the claim that it would catch an implementation returning array indices. It would not -- it corrupts slot 0, whose identifier is also 0. The discrimination comes from the paired own-slot case at slot 1 (identifier 2), and the comment now says so. Correcting the record rather than rewriting it: commit 69766dd3's message says the suite goes "from 12 cases to 16" with "six new tests". Both counts are wrong. The contract test landed in 266c6a7c, so the table went 13 -> 17, and that commit added four cases (api, infinity, no_side_effects, max_size) alongside the x = 0 addition to an existing test and the two de-confoundings. The commits are unpushed and could be amended, but the review cites them by hash, so the numbers are corrected here instead. With this commit the module has 17 tests. Verification: warning-free build; 17/17 at -i=16, -i=200 and -i=1000; ./tests, ./noverify_tests and ./exhaustive_tests exit 0; `make check` 12/12; the module clean under valgrind (0 errors from 0 contexts); ctime_tests clean under valgrind; CMake ctest 542/542; vectors.h still regenerates byte for byte, so nothing here touched a frozen encoding. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-04 11:35:59 +02:00
Kgothatso Ngako	98aadc121f	build: give the experimental modules CMake coverage in CI ... Closes the last gap the review listed, and the one the plan left as optional: no CI job built any experimental module through CMake, so the src/CMakeLists.txt wiring for frost, chilldkg, iceberg, prefractal and frost_enrollment was guarded only by developers running it locally. The plan suggested "adding the experimental modules to one existing CMake job". There are two candidates and they are not equivalent: - win64-native is the only job that RUNS CMake tests, but it builds with MSVC and clang-cl under CFLAGS="/WX". None of the five modules has ever been compiled by MSVC. Turning them on there would be a porting exercise whose first result is a wall of warnings-as-errors from code unrelated to any regression -- and it would land that on four modules this branch does not otherwise touch. - The release job's "Check installation with CMake" step is gcc on Linux, the same compiler and platform where all five are known to build. It configures, builds and installs. The second is where the flags go. It does not run ctest, which is fine: the tests already run under autotools in 45 job contexts. What was unguarded was the WIRING, and this step exercises exactly that -- the SECP256K1_EXPERIMENTAL gate, the dependent-module block ordering, and the PUBLIC_HEADER appends, which the install step then confirms landed by listing the installed tree. Verified that the guard is not decorative. Moving the frost_enrollment block in src/CMakeLists.txt from before the FROST block to after it -- the exact trap the module's commit message describes, where a block that force-enables a dependency runs too late for the block that emits its compile definition -- makes this step fail with undefined references to secp256k1_frost_derive_pubshare_at and friends. Before this change, that mistake reached main with nothing complaining. Also verified the command as written: configure, build and install with all five modules on succeeds on gcc/Linux, the installed include directory carries secp256k1_frost.h, secp256k1_chilldkg.h, secp256k1_iceberg.h, secp256k1_prefractal.h and secp256k1_frost_enrollment.h, and the step's follow-up compile of examples/ecdsa.c against the installed library still links and runs. The workflow parses, and the step really does carry all five module flags plus the experimental gate. This deliberately changes CI coverage for four modules beyond the one this branch adds. It only adds coverage -- no existing job loses anything -- but it is a one-line revert if the wider scope is unwanted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-04 10:30:21 +02:00
Kgothatso Ngako	a7d4337778	build: wire the frost_enrollment module into both build systems ... Second of six commits adding the frost_enrollment module. This one is scaffolding only: the five entry points are stubs that validate their pointer arguments, zero their outputs and return 0. What is being verified here is that the module configures, compiles, links, exports its symbols and registers its test module in both build systems -- so that the next commit changes nothing but arithmetic. Ordering is the one thing in this commit that can go silently wrong, and it goes wrong in opposite directions in the two build systems: - configure.ac executes its `if` blocks in file order, and enable_module_frost defaults to no (configure.ac:243). A block placed after the frost block at :601 that sets enable_module_frost=yes flips the variable too late: AM_CONDITIONAL goes true, so the header is installed and the Makefile fragment is pulled in, but -DENABLE_MODULE_FROST=1 is never appended, so src/secp256k1.c never includes frost's implementation and every secp256k1_frost_* symbol fails to link. The new block therefore goes ahead of both the frost block and prefractal's, which documents the same trap. - src/CMakeLists.txt processes dependents FIRST, so the same block goes above the FROST block there, beside prefractal's. Verified rather than assumed: configuring with ONLY --enable-module-frost-enrollment emits -DENABLE_MODULE_FROST=1 alongside -DENABLE_MODULE_FROST_ENROLLMENT=1, and the CMake summary prints "frost ON" for the same configuration -- the latter is what the PARENT_SCOPE lift buys, since the summary runs after add_subdirectory(src) and would otherwise report a module it is compiling in as OFF. The dependency guard is prefractal's implies-frost idiom, copied verbatim along with its reasoning. frost is default-OFF, so the `test x"$enable_module_frost" = x"no"` / `DEFINED X AND NOT X` guard every other module uses -- which reads as "the user disabled it explicitly" for a default-ON dependency -- is true by default here and cannot tell an explicit --disable-module-frost from the default once both are in the cache. Enabling frost-enrollment simply implies frost, with no error. The one frost-module change in the whole series is in this commit: src/modules/frost/session.h gains a declaration for secp256k1_frost_sort_ids, which is defined at session_impl.h:517 and declared nowhere. The params hash needs it to canonicalize identifier order. Prefractal reaches frost's statics through translation-unit ordering alone; rather than inherit reuse-by-link-order, this declares the function where keygen.h:48 already declares derive_pubshare_at, so the reuse goes through an interface. No behavior change: it is a declaration for an existing static definition in the same TU. CI wiring is two files, and skipping either half fails quietly: - ci/ci.sh gets FROST_ENROLLMENT in the reproduction header's variable list and --enable-module-frost-enrollment="$FROST_ENROLLMENT" after the prefractal line. - .github/workflows/ci.yml gets FROST_ENROLLMENT at every PREFRACTAL site: the global default, 11 inline matrix entries and 10 job-level env blocks. Without the default, ci.sh runs under set -eux with an empty $FROST_ENROLLMENT, passes --enable-module-frost-enrollment="", `test x"" = x"yes"` is false, and the module is off in all of CI while ci.sh visibly has the plumbing. Verified programmatically over the parsed workflow: across the 106 effective job contexts, PREFRACTAL and FROST_ENROLLMENT now agree in every single one (45 set to yes, no mismatches), no context sets FROST_ENROLLMENT without FROST or without EXPERIMENTAL, and no context leaves it undefined. ci.sh passes sh -n. The stub test is not a placeholder that has to be deleted later: every entry point must reject an empty helper set and leave its output zeroed, which is true of the stubs and stays true of the finished implementation, so it doubles as the check that all five symbols are reachable from the test binary. Verification. Autotools: ./autogen.sh, then a frost-enrollment-only configure and a full configure with frost, chilldkg, iceberg, prefractal and frost-enrollment all on -- both build with zero warnings under the project's -Werror-grade flag set, ./tests and ./exhaustive_tests exit 0, and `./tests -l` lists the frost_enrollment module. CMake: configure with -DSECP256K1_EXPERIMENTAL=ON -DSECP256K1_ENABLE_MODULE_FROST_ENROLLMENT=ON builds clean and ctest passes 391 tests. nm shows the five new symbols exported from libsecp256k1.so; tools/symbol-check.py could not be run here because python3-lief is not installed in this environment, but all five carry the required secp256k1_ prefix. make dist succeeds and the tarball carries src/modules/frost_enrollment/frost_enrollment.md alongside the other module documents. One unrelated observation from this build: a stale src/ctime_tests-ctime_tests.o left over from an earlier configure with a different module set will fail to link, because automake does not track CPPFLAGS changes across reconfigures. make clean between configurations with different module sets, not a fault in this change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-04 03:53:03 +02:00
Kgothatso Ngako	0e5369de7a	build: wire prefractal into CI and the README feature list ... The prefractal module landed on main in parallel with the branches that established the current module conventions, so it never picked up the integration points every other experimental module has. 01379624 covered the CMake experimental gate and EXTRA_DIST; these two are what remained. The CI gap is the more consequential of the pair. ci/ci.sh had no PREFRACTAL plumbing at all, so no CI job has ever passed --enable-module-prefractal -- the flag was reachable only by configuring by hand, and the module has been built and tested exclusively outside CI since it landed. - ci/ci.sh: PREFRACTAL joins FROST, CHILLDKG and ICEBERG in the reproduction header's variable list, and configure gains --enable-module-prefractal="$PREFRACTAL" after the iceberg line. Unlike 2473c768 there is no bench-step counterpart: prefractal ships neither a bench binary nor an example program, so the BENCH block needs nothing. - .github/workflows/ci.yml: a PREFRACTAL: 'no' default alongside the other module defaults, then PREFRACTAL: 'yes' in the 21 places that already enable FROST (11 inline matrix entries and 10 job-level env blocks). The default is not cosmetic -- ci.sh runs under set -eux, so an undefined PREFRACTAL would abort every job at the configure step, including the ones that build no modules at all. FROST-enabled jobs are the right target because enabling prefractal implies frost (configure.ac:539, mirrored in src/CMakeLists.txt:90): adding PREFRACTAL to a job that sets FROST: 'no' would silently turn frost on and change what that job covers. Every job that already builds frost also enables musig, schnorrsig, extrakeys and experimental, which is the remainder of prefractal's dependency chain, so no job needed any other variable adjusted. This is a slightly wider set than CHILLDKG and ICEBERG cover. The x86_64-debian matrix entry at line 117 sets FROST: 'yes' without CHILLDKG or ICEBERG, and 2473c768 deliberately left it alone; it gets PREFRACTAL here, on the rule above. The consequence is that no job now builds frost without prefractal. If that standalone-frost combination is worth preserving, that one entry is the place to drop it. README.md gains the doc/prefractal.md link beside the frost, chilldkg and iceberg entries. This is the exact inverse of the bug 42f827a7 fixed: there the documents were linked from README.md but missing from EXTRA_DIST, so the tarball's README pointed at files it did not carry. Here doc/prefractal.md has been in EXTRA_DIST since 01379624 but nothing referenced it, so it shipped unreferenced. All four module documents this fork adds are now both linked and distributed. Verified with ./autogen.sh, ./configure --enable-experimental --enable-module-prefractal and make -j: all exit 0 with no warnings, and the configure summary shows the implication chain resolving, with prefractal = yes pulling in frost = yes and musig = yes. nm confirms run_prefractal_api_test is linked into ./tests, and the suite passes. make dist succeeds and the tarball carries doc/prefractal.md next to doc/iceberg.md, src/modules/frost/frost.md and src/modules/chilldkg/chilldkg.md. ci/ci.sh passes sh -n. Verified programmatically for the workflow, as in 2473c768: the YAML parses, 33 effective job contexts set FROST: 'yes', all 33 of them now also set PREFRACTAL: 'yes', every one has MUSIG, SCHNORRSIG, EXTRAKEYS and EXPERIMENTAL set to 'yes', and no context sets PREFRACTAL without FROST. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-04 03:28:22 +02:00
Kgothatso Ngako	2473c76871	iceberg: wire the module into CI ... - ci/ci.sh: new ICEBERG environment variable, printed in the reproduction header and passed to configure as --enable-module-iceberg (mirroring CHILLDKG); bench_iceberg runs in the bench step when the module is enabled, as in the source tree's CI. - .github/workflows/ci.yml: ICEBERG: 'no' default; ICEBERG: 'yes' in the 20 jobs that enable musig + schnorrsig + experimental (the same jobs that build chilldkg). Jobs that deliberately build without musig or its dependencies are left at 'no'. Verified programmatically: the YAML parses and every ICEBERG: 'yes' context also has MUSIG, SCHNORRSIG and EXPERIMENTAL set to 'yes'.	2026-08-31 12:25:55 +02:00
Kgothatso Ngako	3b68633f59	chilldkg: CI wiring, ctime_tests coverage, declassify fixes ... CI: - ci/ci.sh: new CHILLDKG environment variable, passed to configure as --enable-module-chilldkg (mirroring FROST). - .github/workflows/ci.yml: default CHILLDKG: 'no' and CHILLDKG: 'yes' in every job that enables FROST, except the x86_64 matrix entry that deliberately builds without the ecdh module (chilldkg requires schnorrsig + ecdh; the configure-time dependency error would fire there). YAML validity and per-job dependency presence checked programmatically. ctime_tests: - src/ctime_tests.c: run a full ChillDKG session (n = 2, t = 2) through the public API under the memory checker: hostpubkey_gen, params_hash, participant_step1, coordinator_step1, participant_step2, coordinator_finalize, participant_finalize, participant_recover and recovery_ack_sign. Host secret keys, session randomness, aux randomness and the resulting secret shares are undefined (secret); all protocol messages, the certificate, threshold public key, public shares, recovery data, ack signature and the secret-free state1 objects are defined (public). state2 stays secret (contains the secret share). Constant-time fixes found by running the new block under MemorySanitizer (valgrind unavailable locally; MSan build via clang + CMake). All are missing declassifications of secret-derived but public (or public-outcome) values, following the frost module's secp256k1_declassify pattern with justification comments; no real constant-time bugs were found: - hostpubkey_gen: declassify the computed host public key before serialization (public output). - participant_step1: declassify the zero-randomness check result (only reveals "the RNG returned 32 zero bytes", which aborts the session). - encpedpop participant_step1: declassify the pubnonce point before serialization (public, part of pmsg1). - chilldkg_schnorrsig_sign: declassify the signer public key before normalization/parity branch, and declassify the return value (a failure only reveals a zero derived nonce, negligible probability). - vss_commit: declassify the VSS commitments before serialization (public, part of pmsg1). - vss_verify_secshare: declassify secshare*G before the infinity/eq checks (equals the public pubshare in honest runs; the discrete log is not revealed). - simplpedpop_participant_investigate (proactive audit; not reached by ctime_tests): declassify the secshare-sum comparison result (the public fault code reveals it anyway). Verified: MSan ctime_tests exits 0; autotools make check 10/10 (the local tree is configured without --enable-ctime-tests because neither valgrind nor an MSan-instrumented gcc build is available; CI runs ctime_tests under valgrind as before); CMake ctest 428/428; ./tests --target=chilldkg and ./chilldkg_example pass.	2026-08-31 10:25:14 +02:00
Kgothatso Ngako	2d97cc2242	Frost Module logic.	2026-08-31 00:05:16 +02:00
merge-script	8099999ff2	Merge BlockstreamResearch/secp256k1-zkp#360: sync-upstream: Simplify ... c5be752e2e gha: Simplify sync.yml according to sync-upstream.sh changes (Tim Ruffing) 260fad30aa sync-upstream: Optionally switch to sync branch (Tim Ruffing) f0ff45f3ab sync-upstream: Simplify (Tim Ruffing) Pull request description: This is a half-rewrite of the sync-upstream script because I still wasn't happy with it. Looking for early feedback on this. Advantages: - The script does not hardcode any repo URLs, branches, etc. - Nicer separation of responsibilities between the script and the GHA workflow. This brings back the usefulness of the script when used locally outside GHA. - Much simpler code, and we could simplify also the GHA workflow. Still to do: - Rewrite the "Tips" section in the generated PR description, e.g., add how to resolve merge conflicts. - Change the GHA workflow accordingly. ACKs for top commit: mllwchrry: ACK c5be752 Tree-SHA512: 7335b4690642c07965366da952a74065ec404f750e0c6c7e735a9a48285cbe6b9c7db27ff4bdeba1d5ce59717d77be1ecb2334200b56a1a0a2c0fcddc7530d0b	2026-06-02 09:20:18 +02:00
Tim Ruffing	c5be752e2e	gha: Simplify sync.yml according to sync-upstream.sh changes	2026-06-01 11:11:12 +02:00
merge-script	45f6f0f158	Merge BlockstreamResearch/secp256k1-zkp#363: Upstream PRs 1846, 1848, 1849 ... 8479eafa57 musig: always clear out secret key in `secp256k1_musig_nonce_gen_counter` (Sebastian Falbesoner) 3cca6451a2 ci: Bump GCC snapshot major version to 17 (Hennadii Stepanov) 285cb788e9 ci: Replace `ilammy/msvc-dev-cmd` with manual MSVC setup (Hennadii Stepanov) Pull request description: This PR has been created by a GitHub Actions workflow without human involvement. [bitcoin-core/secp256k1#1846]: ci: Replace `ilammy/msvc-dev-cmd` with manual MSVC setup [bitcoin-core/secp256k1#1848]: ci: Bump GCC snapshot major version to 17 [bitcoin-core/secp256k1#1849]: musig: always clear out secret key in `secp256k1_musig_nonce_gen_counter` Tips: * Use `git show --remerge-diff <pr-branch>` to show the conflict resolution in the merge commit. * Use `git read-tree --reset -u <pr-branch>` to replay these resolutions during the conflict resolution stage when recreating the PR branch locally. Be aware that this may discard your index as well as the uncommitted changes and untracked files in your worktree. ACKs for top commit: mllwchrry: ACK b11340b. This sync PR can be merged as-is. DarkWindman: ACK b11340b3ce Tree-SHA512: 4b311e9bfa21f00b4780202c08af9d00380f5b3df40704641764d706cfc3408615b6206c7c82ca915b56c27a354bdf24680674269a28eefe7d4e93adc06cbaa5	2026-05-05 16:23:21 +03:00
Hennadii Stepanov	285cb788e9	ci: Replace ilammy/msvc-dev-cmd with manual MSVC setup ... The `ilammy/msvc-dev-cmd` repository seems abandoned and should be considered unsafe. This updates the workflow to load the MSVC environment variables directly via `vcvars64.bat`. See https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line.	2026-04-13 11:54:22 +01:00
DarkWindman	f7e7e6bb15	Merge branch 'master' into sync-7262adb4	2026-04-01 17:29:57 +03:00
DarkWindman	e371ab5df0	sync-upstream: Restore SYNC_PAT for gh commands	2026-03-30 11:50:08 +03:00
Tim Ruffing	c5cd9d6d9a	gha: Bump deprecated GHA workflow dependencies ... Deprecation notice: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ Changelogs (no entries relevant to us): * https://github.com/docker/setup-buildx-action/releases/tag/v4.0.0 * https://github.com/docker/build-push-action/releases/tag/v7.0.0 * https://github.com/actions/cache#v5	2026-03-26 09:46:13 +01:00
DarkWindman	efa4e11b65	sync-upstream: Use GITHUB_TOKEN for gh commands	2026-03-20 17:09:45 +02:00
DarkWindman	c9a623c362	sync-upstream: Pass token via checkout for git push operations	2026-03-19 15:20:46 +02:00
DarkWindman	3a18afd5ff	sync-upstream: Allow PAT for sync workflow	2026-03-18 11:58:18 +02:00
DarkWindman	bb736825c1	sync-upstream: Add automatic GitHub Actions sync script	2026-03-12 15:28:08 +02:00
copilot-swe-agent[bot]	c0a26a9c1b	ci: enable surjectionproof module in CI configs ... Co-authored-by: real-or-random <1071625+real-or-random@users.noreply.github.com>	2026-03-05 10:26:23 +01:00
mllwchrry	3b2ceb3e7a	Merge commits '14e56970 1605b02f cd49c57e 453949ab 57315a69 97de5120 c5da3bde 99ab4a10 d071aa56 1d146ac3 322d0a43 c7a7f732 ac561601 dfe042fe 3019186a 95e68158 10f546a2 c0a2aba0 ' into temp-merge-1811	2026-03-03 14:45:28 +02:00
mllwchrry	07d4de6433	Merge commits '115b135f c8206b1c b6c2a3cd e7f7083b be5e4f02 5c751833 540fec8a aa2a39c1 8d445730 f9a944ff 2d9137ce 4721e077 471e3a13 ebb35882 1a53f496 c7a52400 ' into temp-merge-1809	2026-03-02 15:56:43 +02:00
DarkWindman	f1e52fac20	Merge commits '88be4e8d b4756543 10dab907 58178851 de6af6ae baa26542 2b7337f6 a44a3393 f44c1ebd d543c0d9 43e7b115 7a2fff85 ' into temp-merge-1758	2026-02-27 14:47:34 +02:00
DarkWindman	38284aa008	Merge commits '2c076d90 20e3b447 74b8068c e523e4f9 d5997141 d2dcf520 f36afb8b 8113671f d93380fb 03fb60ad 4985ac0f 36e76952 ' into temp-merge-1738	2026-02-25 10:44:34 +02:00
Tim Ruffing	79e9f25237	ci: Fix leftover use of old ECMULTGENPRECISION	2026-02-25 08:42:29 +01:00
mllwchrry	9dcd857d54	Merge commits '29e73f4b 89096c23 c4987790 ad60ef7e 943479a7 cbbbf3bd 73a69595 7c338042 5e74086d 6037833c 020ee604 a660a497 b9313c6e ' into temp-merge-1708	2026-02-24 13:31:44 +02:00
mllwchrry	4dda31229e	ci: Use Python virtual environment in x86_64-macos-native job	2026-02-23 15:03:08 +02:00
Hennadii Stepanov	795f19af1f	ci: Switch to macOS 15 Sequoia Intel-based image ... The `macos-13` image has been deprecated and will be unavailable soon. See: https://github.com/actions/runner-images/issues/13045.	2026-02-23 15:00:53 +02:00
Tim Ruffing	2f057a145f	ci: Don't hardcode ABI version	2026-02-20 18:53:01 +02:00
mllwchrry	79953d074b	Merge commits '1b1fc093 6c2a39da 31860823 abd25054 4ba1ba2a 03bbe8c6 13ed6f65 a7a51171 2abb35b0 e56716a3 3f54ed8c d84bb83e ' into temp-merge-1661	2026-02-20 18:29:53 +02:00
mllwchrry	347d6adfd2	Merge commits 'a88aa935 01b58933 18f9b967 e59158b6 1fae76f5 f0868a9b 68b55209 9b7c59cb 1464f15c 9a8db52f 7d48f5ed a38d879a ' into temp-merge-1628	2026-02-16 16:04:51 +02:00
mllwchrry	248358f2bc	Merge commit '3660fe5e' into temp-merge-1479	2026-02-13 13:08:00 +02:00
DarkWindman	551b5dd415	Merge commits 'fded437c cdf08c1a 642c885b f8c1b0e0 3fdf146b b3076144 19888550 2f2ccc46 472faaa8 4c57c7a5 ' into temp-merge-1554	2026-02-11 13:56:17 +02:00
DarkWindman	d0dde4aa2a	Merge commits '35c0fdc 5dd637f 69b2192 d7ae25c d403eea f473c95 4af241b a526937 fcc5d73 ca06e58 ea2d5f0 0055b86 ' into temp-merge-1551	2026-02-10 13:06:38 +02:00
mllwchrry	91b2deab7b	ci: Add zkp modules to arm64-macos-native job	2026-02-06 14:37:11 +02:00
merge-script	99ab4a105e	Merge bitcoin-core/secp256k1#1817: ci: Disable Docker build summary generation ... 3ae72e7867 ci: Disable Docker build summary generation (Hennadii Stepanov) Pull request description: The generated Docker build [summaries](https://github.com/bitcoin-core/secp256k1/actions/runs/21595861407) provide little practical value to the development workflow and clutter the CI output. This PR disables them. ACKs for top commit: real-or-random: utACK 3ae72e7867 Tree-SHA512: 0b28520765d5aa1c43ae7025c9be082742bc3784f743b4983947236bceb0255b2fa82cdf81d284470eeb83bda72b442019e051048319681bff09ac190d9b52f6	2026-02-03 15:25:43 +01:00
Hennadii Stepanov	4fb7ccf5d4	ci: Enforce base-10 evaluation	2026-02-03 11:24:14 +00:00
Hennadii Stepanov	3ae72e7867	ci: Disable Docker build summary generation ... These summaries provide little practical value to the development workflow and clutter the CI output.	2026-02-03 08:51:11 +00:00
Hennadii Stepanov	2ccff6eb73	ci: Add weekly schedule	2026-02-02 11:21:11 +00:00
Hennadii Stepanov	2f18567d24	ci: Rotate Docker cache keys every 4 weeks ... This forces a periodic clean build to ensure we do not rely on stale cache layers indefinitely.	2026-02-02 11:17:18 +00:00
Jonas Nick	9a57e3c650	Merge commits 'da515074 ' into temp-merge-1058	2026-01-30 21:18:06 +00:00
Hennadii Stepanov	f252da7e6e	ci: Use Python virtual environment in "x86_64-macos-native" job	2025-11-07 15:20:03 +00:00
Hennadii Stepanov	8bc50b72ff	ci: Switch to macOS 15 Sequoia Intel-based image ... The `macos-13` image has been deprecated and will be unavailable soon. See: https://github.com/actions/runner-images/issues/13045.	2025-10-15 15:31:21 +01:00
merge-script	f44c1ebd96	Merge bitcoin-core/secp256k1#1719: ci: DRY workflow using anchors ... 15d014804e ci: Drop default for `inputs.command` in `run-in-docker-action` (Hennadii Stepanov) 1decc49a1f ci: Use YAML anchor and aliases for repeated "CI script" steps (Hennadii Stepanov) dff1bc107d ci, refactor: Generalize use of `matrix.configuration.env_vars` (Hennadii Stepanov) 4b644da199 ci: Use YAML anchor and aliases for repeated "Print logs" steps (Hennadii Stepanov) a889cd93df ci: Bump `actions/checkout` version (Hennadii Stepanov) 574c2f3080 ci: Use YAML anchor and aliases for repeated "Checkout" steps (Hennadii Stepanov) Pull request description: GHA YAML parser now [supports](https://github.com/actions/runner/issues/1182#issuecomment-3156285802) anchors. This PR makes use of that support to [DRY](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) the workflow code. ACKs for top commit: real-or-random: utACK 15d014804e Tree-SHA512: a25a226fec0053242bc46b8c9815067a35af632cfbffefcc5cd4c96a67c0535dde447753099cbc74ecc64072d36aef2aa78c105b66f43cb3134ffa1ae60dca1e	2025-10-14 21:21:26 +02:00
Hennadii Stepanov	15d014804e	ci: Drop default for inputs.command in run-in-docker-action ... This change decreases coupling.	2025-10-14 12:24:36 +01:00
Hennadii Stepanov	1decc49a1f	ci: Use YAML anchor and aliases for repeated "CI script" steps	2025-10-14 12:24:25 +01:00
Hennadii Stepanov	dff1bc107d	ci, refactor: Generalize use of matrix.configuration.env_vars	2025-10-14 12:23:54 +01:00
Hennadii Stepanov	4b644da199	ci: Use YAML anchor and aliases for repeated "Print logs" steps	2025-10-14 11:51:22 +01:00
Hennadii Stepanov	a889cd93df	ci: Bump actions/checkout version ... See https://github.com/actions/checkout/releases.	2025-10-14 11:49:05 +01:00
Hennadii Stepanov	574c2f3080	ci: Use YAML anchor and aliases for repeated "Checkout" steps	2025-10-14 11:47:23 +01:00
Hennadii Stepanov	53585f93b7	ci: Use clang-snapshot in "MSan" job	2025-10-14 11:19:45 +01:00