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

..

ci.sh

build: wire prefractal into CI and the README feature list

2026-09-04 03:28:22 +02:00

linux-debian.Dockerfile

Merge BlockstreamResearch/secp256k1-zkp#363: Upstream PRs 1846, 1848, 1849

2026-05-05 16:23:21 +03:00