Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core getprioritisedtransactions RPC: Fee-Delta Audit Guide
Bitcoin Core 26 getprioritisedtransactions guide covering fee deltas, mempool presence, persistence, mining policy, reconciliation and safe operator use.
This guide explains Bitcoin Core getprioritisedtransactions 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 getprioritisedtransactions to list every fee delta created by prioritisetransaction. The result is keyed by transaction ID and reports the delta in satoshis plus whether that transaction is currently in the local mempool.
- Why it matters: getprioritisedtransactions gives operators the missing inventory for local fee policy. Safe use treats each delta as a controlled, reversible intervention and never confuses local prioritisation with propagation or confirmation.
- 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.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.
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.
No arguments
The command accepts no parameters and returns the full map. Pin the Core version and restrict access because the output exposes local mining-policy interventions.
Fee delta
fee_delta is denominated in satoshis and modifies local fee treatment. It does not change the transaction’s serialized fee, recipient amounts or consensus validity.
Mempool flag
in_mempool states whether the transaction is present now. False can mean it was never accepted, was evicted, replaced, confirmed or otherwise left the mempool.
Persistence
Prioritisation state may outlive mempool presence and can be persisted. Reconcile entries after restart and remove obsolete deltas deliberately using prioritisetransaction.
Mining boundary
A positive delta can influence local template selection; a negative one can lower effective priority. Other miners and relays do not inherit the node’s local adjustment.
Audit trail
Record requester, reason, txid, before and after delta, time, expiry condition and current mempool state without copying unrelated transaction data.
Monitoring
Alert on unexpected entries, large deltas, stale absent transactions and divergence between policy records and RPC output. Cross-check with getmempoolentry and templates where relevant. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is Bitcoin Core getprioritisedtransactions RPC?
Bitcoin Core 26.0 introduced getprioritisedtransactions to list every fee delta created by prioritisetransaction. The result is keyed by transaction ID and reports the delta in satoshis plus whether that transaction is currently in the local mempool.
Is Bitcoin Core getprioritisedtransactions RPC active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core getprioritisedtransactions RPC matter?
getprioritisedtransactions gives operators the missing inventory for local fee policy. Safe use treats each delta as a controlled, reversible intervention and never confuses local prioritisation with propagation or confirmation.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
getprioritisedtransactions gives operators the missing inventory for local fee policy. Safe use treats each delta as a controlled, reversible intervention and never confuses local prioritisation with propagation or confirmation.
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.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.