AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 18 Bitcoin

build: depends makes libmultiprocess by default

Public commit record

What the developer wrote

Authored by Sjors Provoost

90/100 · Strong
build: depends makes libmultiprocess by default

This causes IPC binaries (bitcoin-node, bitcoin-gui) to be included
in releases.

The effect on CI is that this causes more depends builds to build IPC
binaries, but still the only build running functional tests with them
is the i686_multiprocess one.

Except for Windows.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit changes Bitcoin Core's build system so that multiprocess/IPC support is built by default in the depends system, rather than requiring an explicit option. It renames the option from MULTIPROCESS=1 to NO_IPC=1 (to opt out), adds IPC binaries to maintenance targets, and disables IPC only on Windows. There is no direct security fix or vulnerability being patched in the code itself; it is a build configuration change that increases the default attack surface by including more binaries and dependencies in releases.

Recommended action

Treat as a build-hardening/configuration review item rather than a vulnerability. Review the security posture of the newly default-included IPC binaries (bitcoin-node, bitcoin-gui), the Cap'n Proto dependency, and the multiprocess interface surface. Ensure release signing, sandboxing, and fuzzing coverage account for these binaries. No immediate patch or incident response is indicated by this commit alone.

Security signals we found

01

Build system change increases default compiled attack surface (IPC binaries and Cap'n Proto dependency included by default)

02

New IPC binaries (bitcoin-node, bitcoin-gui) added to maintenance/installed release targets

03

Windows explicitly excluded from default IPC builds

04

No direct code-level vulnerability, bug fix, or security patch present in diff

Risk score

Why this scored 18/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 9/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.