Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£884.60
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains Bitcoin Core submitpackage RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 26.0 introduced experimental submitpackage for submitting a child transaction together with its unconfirmed parents to the local mempool. No parent may depend on another parent.
- Why it matters: submitpackage gives a local package-policy interface, not guaranteed package relay. Reliable automation validates the graph and intent before submission, parses each transaction result and monitors propagation independently.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core submitpackage RPC in simple English
Bitcoin Core submitpackage RPC: Every transaction is checked against consensus and local mempool rules. Package CPFP can use a high-fee child to lift parents, but not below the minimum relay feerate boundary.
Simple example
A miner is checking Bitcoin Core submitpackage RPC. Reconcile wallet and service state before treating the new package as the intended candidate. The RPC and interface were experimental in 26.0.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Experimental boundary
The RPC and interface were experimental in 26.0. Pin the version, test exact result parsing and do not build an irreversible broadcast workflow around a provisional contract.
Package shape
Provide serialized hex transactions comprising one child and its parents. Parents must be independent of one another and package RBF was not available.
Validation
Every transaction is checked against consensus and local mempool rules. Package CPFP can use a high-fee child to lift parents, but not below the minimum relay feerate boundary.
Per-transaction results
tx-results is keyed by wtxid and reports txid, optional conflicting-witness information, vsize, base fee and conditional effective feerate and included wtxids.
Replacement evidence
replaced-transactions can list txids removed by acceptance. Reconcile wallet and service state before treating the new package as the intended candidate.
Propagation gap
Successful local acceptance does not guarantee network propagation. Observe peer relay, remote mempools and later confirmation without representing any one observation as universal.
Safe workflow
Decode and review all transactions, run testmempoolaccept, verify dependency graph and package feerate, submit once, parse every result and continue monitoring each wtxid. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of Bitcoin Core submitpackage RPC?
Bitcoin Core submitpackage RPC: Every transaction is checked against consensus and local mempool rules. Package CPFP can use a high-fee child to lift parents, but not below the minimum relay feerate boundary.
For Bitcoin Core submitpackage RPC, what should a beginner know about experimental boundary?
The RPC and interface were experimental in 26.0. Pin the version, test exact result parsing and do not build an irreversible broadcast workflow around a provisional contract.
For Bitcoin Core submitpackage RPC, what should a beginner know about package shape?
Provide serialized hex transactions comprising one child and its parents. Parents must be independent of one another and package RBF was not available.
For Bitcoin Core submitpackage RPC, what should a beginner know about validation?
Every transaction is checked against consensus and local mempool rules. Package CPFP can use a high-fee child to lift parents, but not below the minimum relay feerate boundary.
Conclusion
submitpackage gives a local package-policy interface, not guaranteed package relay. Reliable automation validates the graph and intent before submission, parses each transaction result and monitors propagation independently.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.