What changed, and why it matters
This is a one-line build-system change for Bitcoin Core. Previously, when developers built the fuzzing test suite, the code automatically disabled a feature called IPC (inter-process communication). This change removes that automatic disable so the IPC fuzz target gets compiled along with the rest of the fuzzing surface. It is a build/test-coverage fix, not a fix for a runtime vulnerability in the Bitcoin node software itself.
No security action required. Treat as a normal build-system improvement. If reviewing, verify that CI fuzz builds with Cap'n Proto available now include the IPC target as expected.
Security signals we found
Build-system change only
Expands fuzzing coverage surface rather than restricting it
No runtime code changes
No mention of vulnerability, CVE, bug, or exploit in commit message
Evidence from the diff
The commit removes set(ENABLE_IPC OFF) from the BUILD_FOR_FUZZING block in CMakeLists.txt. The intent is to include the IPC fuzz target in standard fuzz builds rather than silently skipping it. IPC compilation still depends on the top-level ENABLE_IPC option and will fail at build time if Cap’n Proto dependencies are missing. There is no change to consensus, networking, wallet, or mempool code.
Changed components
CMakeLists.txt build configurationFuzz build presetIPC fuzz target build inclusionInspect captured patch +0 / −1
diff --git a/CMakeLists.txt b/CMakeLists.txt
index eda934cc..5bc86efd 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -231,7 +231,6 @@ 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 16/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.