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

bcli: remove unused async code after sync refactor

Public commit record

What the developer wrote

Authored by dovgopoly

73/100 · Adequate
bcli: remove unused async code after sync refactor

Remove the asynchronous execution infrastructure no longer needed after converting all bcli commands to synchronous execution. This includes removing the async callbacks, the pending request queue, etc.

Fix missing `close(from)` file descriptor leak in `run_bitcoin_cliv`.

Changelog-Changed: bcli plugin now uses synchronous execution, simplifying bitcoin backend communication and improving error handling reliability.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit is mostly a cleanup: it removes old asynchronous code from the bitcoin-cli plugin after it was converted to run commands one at a time (synchronously). The only functional bug fix is adding a missing `close(from)` call, which stops a file descriptor leak when running bitcoin-cli. There is no obvious new security vulnerability introduced by the change.

Recommended action

No immediate action required beyond normal review and testing. The cleanup reduces attack surface; verify the synchronous refactor did not introduce regressions in error handling or retry behavior.

Security signals we found

01

File descriptor leak fixed in `run_bitcoin_cliv` and `wait_and_check_bitcoind` by adding `close(from)`

02

Removal of async I/O and concurrency control reduces complexity and potential race conditions

03

`waitpid` error handling improved: non-EINTR failures now call `plugin_err` instead of looping silently

04

No new input parsing, network exposure, or cryptographic operations introduced

Risk score

Why this scored 21/100

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