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

mining: add submitBlock IPC method to Mining interface

Public commit record

What the developer wrote

Authored by woltx

73/100 · Adequate
mining: add submitBlock IPC method to Mining interface

Add a submitBlock method to the Mining IPC interface, similar to the
submitblock RPC. This accepts a fully assembled block, validates it, and
if accepted as new, processes it into chainstate.

This is needed for Stratum v2 Job Declarator Server (JDS), where accepted
solutions may correspond to jobs not tied to a Bitcoin Core BlockTemplate.
JDS receives PushSolution fields and reconstructs full blocks; without an
IPC submitBlock method, final submission requires the submitblock RPC.

The method returns detailed status (reason/debug strings) matching the
checkBlock pattern, giving callers enough information to handle
validation failures.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new internal 'submitBlock' method to Bitcoin Core's Mining interface, used by external mining software (like Stratum v2 servers) to submit fully assembled blocks for validation. It is a feature addition that mirrors the existing submitblock RPC. There is no direct evidence in the commit of a security vulnerability, but it exposes block submission over the IPC interface, which carries the same general risks as any block-submission path: a compromised or buggy caller could submit invalid or duplicate blocks. The implementation explicitly rejects duplicates and requires a complete block, including coinbase witness data when needed.

Recommended action

Review the IPC access controls for the Mining interface to ensure only authorized mining clients can call submitBlock. Verify that SubmitBlock and ProcessNewBlock handle untrusted block data safely (DoS limits, memory usage, validation cost). Consider fuzzing the new IPC method with malformed blocks. No immediate patch is indicated by the diff alone.

Security signals we found

01

New IPC-exposed block submission surface added

02

Implementation reuses existing SubmitBlock/ProcessNewBlock logic rather than introducing novel validation

03

Explicit duplicate rejection and requirement for complete coinbase witness

04

No mention of authentication, authorization, or sandboxing changes in the commit

05

No direct diff evidence of memory corruption, injection, or consensus bug

Risk score

Why this scored 23/100

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