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

bitcoin-cli: Add -ipcconnect option

Public commit record

What the developer wrote

Authored by Ryan Ofsky

86/100 · Strong
bitcoin-cli: Add -ipcconnect option

This implements an idea from Pieter Wuille <pieter@wuille.net>
https://github.com/bitcoin/bitcoin/issues/28722#issuecomment-2807026958 to
allow `bitcoin-cli` to connect to the node via IPC instead of TCP, if the
`ENABLE_IPC` cmake option is enabled and the node has been started with
`-ipcbind`.

The feature can be tested with:

build/bin/bitcoin-node -regtest -ipcbind=unix -debug=ipc
build/bin/bitcoin-cli -regtest -ipcconnect=unix -getinfo

The `-ipconnect` parameter can also be omitted, since this change also makes
`bitcoin-cli` prefer IPC over HTTP by default, and falling back to HTTP if an
IPC connection can't be established.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds a new command-line option to bitcoin-cli that lets it talk to a local Bitcoin node over a local inter-process communication (IPC) socket instead of the usual network HTTP connection. It is a feature addition, not a fix for a known bug or vulnerability. The change is opt-in at build time and runtime, and it does not appear to introduce an obvious security flaw, but it does add new code paths for authentication and transport that need careful review.

Recommended action

Review the IPC implementation (not shown in this diff) for proper access control on the Unix socket, ensure file permissions and path handling prevent unauthorized local clients, and verify that fallback from IPC to HTTP cannot be abused to downgrade connections or bypass authentication. Treat as a normal feature addition rather than an emergency patch.

Security signals we found

01

New IPC transport path added to bitcoin-cli with fallback behavior

02

Default preference for IPC over HTTP when both may be available

03

Authentication and endpoint handling refactored and passed through new CallIPC path

04

Stub IPC factory added for builds without ENABLE_IPC to maintain linking

05

No explicit security bug or vulnerability described in commit message

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 3/25
Stealth signal 2/15
Affected reach 3/15
Confidence 7/10
Evidence quality 3/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.