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

Merge bitcoin/bitcoin#36297: rpc: Correct invalid OpenRPC defaults

Public commit record

What the developer wrote

Authored by merge-script

81/100 · Strong
Merge bitcoin/bitcoin#36297: rpc: Correct invalid OpenRPC defaults

b7f740c594ba1482344a7906b799fb62c533464f rpc: Correct OpenRPC default metadata (will)

Pull request description:

`getopenrpcinfo` emits two defaults that do not satisfy their schemas.

This changes `getdeploymentinfo.blockhash` to a default hint, since its fallback describes the current chain tip, and makes `send.options.include_watching` default to boolean `false`.

ACKs for top commit:
nervana21:
ACK b7f740c594ba1482344a7906b799fb62c533464f
sedited:
ACK b7f740c594ba1482344a7906b799fb62c533464f

Tree-SHA512: fd99c3642ff39ef13116f7f18e2a93b398e347330ea24e5bfd01744528744e5c6fbff12a56213961f8703218a6100f0ea74a10fe3b1d9a221ba8b1fa307a907a
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a documentation-only fix for Bitcoin Core's machine-readable RPC help data. It changes several default values from literal strings to 'hint' labels (because the real default depends on context) and corrects one boolean default from the string "false" to the actual value false. It does not change how Bitcoin Core processes transactions, validates blocks, or handles money. The only risk is that tools reading the OpenRPC metadata could previously receive invalid schema examples; this patch makes those examples valid.

Recommended action

No urgent action required. Treat as a normal documentation/schema correctness fix. Reviewers may verify that getopenrpcinfo now validates against the OpenRPC schema and that no functional RPC behavior changed.

Security signals we found

01

OpenRPC schema/default mismatch correction

02

RPC help metadata type correction (string 'false' to boolean false)

03

No executable code path changes

Risk score

Why this scored 21/100

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