build: set ENABLE_IPC to OFF when fuzzing
What changed, and why it matters
This is a small build-system fix for Bitcoin Core's fuzzing configuration. When developers build the project specifically for fuzz testing, the build previously failed because it required a library called capnp that is not needed for fuzzing. The change simply turns off the optional IPC (inter-process communication) feature during fuzzing builds so configuration succeeds. There is no runtime security issue, no vulnerability, and no change to how Bitcoin nodes or wallets behave.
No security action required. Treat as a normal build-system fix.
Security signals we found
No security-relevant code change
Build-system-only change
No change to consensus, networking, wallet, or cryptography
No bug fix, vulnerability patch, or hardening measure evident
Evidence from the diff
The commit adds set(ENABLE_IPC OFF) inside the if(BUILD_FOR_FUZZING) block in CMakeLists.txt. ENABLE_IPC controls whether the multiprocess IPC framework (which depends on Cap’n Proto/capnp) is built. Fuzzing builds do not need IPC, and requiring capnp caused configuration to fail. The patch makes fuzzing builds explicitly disable IPC, aligning with other disabled components such as tests, GUI tests, and benchmarks. It is a build-configuration convenience change only.
Changed components
CMakeLists.txt build configurationBUILD_FOR_FUZZING build pathInspect captured patch +1 / −0
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 74ccdb02..5c972d87 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -217,6 +217,7 @@ if(BUILD_FOR_FUZZING)
set(BUILD_TESTS OFF)
set(BUILD_GUI_TESTS OFF)
set(BUILD_BENCH OFF)
+ set(ENABLE_IPC OFF)
set(BUILD_FUZZ_BINARY ON)
target_compile_definitions(core_interface INTERFACE
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.