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

rpc: Always return per-wtxid entries in submitpackage tx-results

Public commit record

What the developer wrote

Authored by John Moffett

83/100 · Strong
rpc: Always return per-wtxid entries in submitpackage tx-results

When submitpackage produced no per-transaction result for a member,
the RPC previously set "error": "unevaluated" but then continued
without inserting the entry into tx-results, making it impossible for
callers to know which wtxids were unevaluated.

Insert the placeholder result before continuing, update help text, and
adjust functional tests to expect entries for all submitted wtxids.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit fixes a minor bug in Bitcoin Core's submitpackage RPC. Previously, when a package of transactions failed early, the RPC would label the failure as 'unevaluated' but wouldn't actually include each transaction's result in the response, making it hard for callers to know which transactions were affected. Now it always returns a per-transaction entry with a clearer 'package-not-validated' message. This is a usability/API correctness fix, not a security vulnerability.

Recommended action

No security action required; treat as a normal bugfix/behavioral improvement. Callers using submitpackage should be aware that tx-results now always contains all submitted wtxids and that the error string for early-abort packages is now 'package-not-validated' rather than 'unevaluated'.

Security signals we found

01

No memory safety, cryptographic, consensus, or authorization issues evident

02

Change is an API response completeness/correctness fix

03

Adds a non-fatal assertion (CHECK_NONFATAL) to enforce an internal invariant

04

No attacker-controlled input is trusted beyond existing RPC transaction hex handling

Risk score

Why this scored 19/100

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