<p>The <code>prioritisetransaction</code> RPC was <a href="https://github.com/bitcoin/bitcoin/pull/1583" rel="nofollow noreferrer">introduced</a> back in 2014 to support miners who wanted to include a transaction in their mined block that perhaps was paying a lower fee rate than competing transactions. One possible use case that was speculated upon in that pull request (<a href="https://github.com/bitcoin/bitcoin/pull/1583" rel="nofollow noreferrer">#1583</a>) was &quot;captcha-solving as an alternative to fees&quot;. As with much of the Bitcoin Core code supporting mining I suspect it isn't used much today but Core generally has to be pretty conservative in removing features in case it breaks someone's software somewhere.</p>
<p>Regarding supporting out of band transactions this RPC doesn't provide any support for receiving transactions bypassing the P2P network and Bitcoin Core mempool rules. Merely support for prioritizing the mining of particular transactions received through normal channels.</p>

CC BY-SA 4.0
2024-01-08T14:50:39.370Z
gotcha, thanks Michael!
WhoIsNinja
CC BY-SA 4.0
2024-01-08T09:04:28.090Z
2024-01-08T09:04:28.090Z
Michael Folkson
<p>Why make it easy for miners/pools to prioritize transactions out of band when there's an option for RBF and CPFP where a miner/pool has to incur cost in sats? It seems to me that Bitcoin Core otherwise doesn't want to encourage out of band transactions but why provide an RPC method at the same time?</p>

<mining-pools><mempool>
Why does Bitcoin Core enable out of band txs with prioritisetransaction RPC
WhoIsNinja
# Why does Bitcoin Core enable out of band txs with prioritisetransaction RPC

(Asked by: username_0 on 2024-01-08)

Why make it easy for miners/pools to prioritize transactions out of band when there's an option for RBF and CPFP where a miner/pool has to incur cost in sats? It seems to me that Bitcoin Core otherwise doesn't want to encourage out of band transactions but why provide an RPC method at the same time?

**Tags:** mining-pools, mempool


---

## 1 answers

### Answer by username_1 on 2024-01-08. Score: 1 | Accepted answer

The `prioritisetransaction` RPC was [introduced](https://github.com/bitcoin/bitcoin/pull/1583) back in 2014 to support miners who wanted to include a transaction in their mined block that perhaps was paying a lower fee rate than competing transactions. One possible use case that was speculated upon in that pull request ([#1583](https://github.com/bitcoin/bitcoin/pull/1583)) was "captcha-solving as an alternative to fees". As with much of the Bitcoin Core code supporting mining I suspect it isn't used much today but Core generally has to be pretty conservative in removing features in case it breaks someone's software somewhere.

Regarding supporting out of band transactions this RPC doesn't provide any support for receiving transactions bypassing the P2P network and Bitcoin Core mempool rules. Merely support for prioritizing the mining of particular transactions received through normal channels.

> **Comments:**
> **username_0**: gotcha, thanks username_1!  

---

