This guide explains Bitcoin Core prioritisetransaction 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 0.16.0 prioritisetransaction changed how the local mining algorithm treated one transaction by adding or subtracting a fee delta in satoshis. The dummy compatibility argument had to be zero or null and was deprecated.
- Why it matters: prioritisetransaction is a local mining-policy adjustment, not a fee payment or network command. Safe use requires exact satoshi units, package-aware template comparison and auditable expiry.
- Current position: Bitcoin Core 0.16.0 prioritisetransaction changed how the local mining algorithm treated one transaction by adding or subtracting a fee delta in satoshis.
Bitcoin Core prioritisetransaction RPC in simple English
Bitcoin Core prioritisetransaction RPC: Validate txid and inspect current mempool or known transaction state. A correct identifier does not mean the transaction is valid, non-conflicting or still available.
Simple example
A miner is checking Bitcoin Core prioritisetransaction RPC. Record package ancestry and current template before mutation. Compare whole-template fees, weight and dependencies before and after, not just the target’s position.
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.
- 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.
Transaction identity
Validate txid and inspect current mempool or known transaction state. A correct identifier does not mean the transaction is valid, non-conflicting or still available. Record package ancestry and current template before mutation.
Deprecated dummy
The second positional argument exists only for prior API compatibility and must be zero or null. Prefer named arguments and omit it where supported. Never place an old priority delta in that slot.
Fee-delta units
fee_delta is an integer satoshi adjustment and can be positive or negative. It changes selection scoring, not the actual fee. Keep it separate from BTC/kB, sat/vB and customer fee accounting.
Local policy only
The effect applies to templates built by this node or connected mining workflow. Other miners and nodes do not inherit it. A true result means the local adjustment was accepted, not that the transaction will confirm.
Package interactions
Changing one transaction’s effective fee can affect ancestor or descendant package selection and displace other revenue. Compare whole-template fees, weight and dependencies before and after, not just the target’s position.
Governance and expiry
Require an approved reason, bounded delta, owner and end condition. Verify how the running version retains or clears the adjustment across mempool removal and restart. Reconcile template and payout reporting so artificial deltas are not booked as revenue.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core prioritisetransaction RPC?
Bitcoin Core prioritisetransaction RPC: Validate txid and inspect current mempool or known transaction state. A correct identifier does not mean the transaction is valid, non-conflicting or still available.
For Bitcoin Core prioritisetransaction RPC, what should a beginner know about transaction identity?
Validate txid and inspect current mempool or known transaction state. A correct identifier does not mean the transaction is valid, non-conflicting or still available.
For Bitcoin Core prioritisetransaction RPC, what should a beginner know about deprecated dummy?
The second positional argument exists only for prior API compatibility and must be zero or null.
For Bitcoin Core prioritisetransaction RPC, what should a beginner know about fee-delta units?
fee_delta is an integer satoshi adjustment and can be positive or negative.
Conclusion
prioritisetransaction is a local mining-policy adjustment, not a fee payment or network command. Safe use requires exact satoshi units, package-aware template comparison and auditable expiry.
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.