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

rpc: add getopenrpcinfo command

Public commit record

What the developer wrote

Authored by will

68/100 · Adequate
rpc: add getopenrpcinfo command

Expose the generated OpenRPC document through RPC so clients can inspect the interface supported by the running node. The command can optionally include hidden RPC commands and arguments for complete code generation and regtest coverage.
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds a new read-only RPC command called getopenrpcinfo to Bitcoin Core. It lets users ask the running node for a machine-readable catalog of all available RPC commands, similar to an API documentation page. The command does not change wallet balances, network rules, or consensus behavior. It only exposes information that was already present in the node's source code and help system. There is no indication in the commit that this fixes a security bug or introduces a dangerous capability.

Recommended action

Treat as a routine feature addition. Reviewers should confirm that hidden RPC exposure via show_hidden is acceptable under the node's existing authentication model, and that the recursion depth in OpenRPCArgSchema/OpenRPCResultSchema cannot be driven to stack exhaustion by malformed metadata. No security patch or incident response is indicated by the supplied materials.

Security signals we found

01

New read-only RPC command added; no state mutation or consensus code touched

02

show_hidden parameter can expose hidden RPC names and argument metadata to authenticated callers

03

Existing RPC authentication and authorization layers still apply

04

No input parsing of untrusted network data beyond the existing JSON-RPC layer

05

No memory safety issues evident in the diff; uses standard containers and recursion with depth bounded by RPC metadata

Risk score

Why this scored 21/100

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