I’ve added minrelaytxfee=0.000001
to my bitcoin.conf
to permit for 0.1 sat/vbyte transactions to enter my node’s mempool.
I can see that is working when looking mempool transactions, and likewise when operating getmempoolinfo
:
{
...
"mempoolminfee": 0.00000100,
"minrelaytxfee": 0.00000100,
"incrementalrelayfee": 0.00001000,
...
}
Nonetheless, after I run getblocktemplate
, solely transactions with a minimal of 1 sat/vbyte are getting included within the candidate block. So even when there are sufficient transactions within the mempool to fill a candidate block, it isn’t really making a 1.00 vMB block of transactions until there are sufficient 1 sat/vbyte transactions within the mempool.
Is there a motive why getblocktemplate
is not choosing from all of the doable transactions within the mempool, and nonetheless solely together with transactions with a minimal of 1 sat/vbyte?
I’ve added minrelaytxfee=0.000001
to my bitcoin.conf
to permit for 0.1 sat/vbyte transactions to enter my node’s mempool.
I can see that is working when looking mempool transactions, and likewise when operating getmempoolinfo
:
{
...
"mempoolminfee": 0.00000100,
"minrelaytxfee": 0.00000100,
"incrementalrelayfee": 0.00001000,
...
}
Nonetheless, after I run getblocktemplate
, solely transactions with a minimal of 1 sat/vbyte are getting included within the candidate block. So even when there are sufficient transactions within the mempool to fill a candidate block, it isn’t really making a 1.00 vMB block of transactions until there are sufficient 1 sat/vbyte transactions within the mempool.
Is there a motive why getblocktemplate
is not choosing from all of the doable transactions within the mempool, and nonetheless solely together with transactions with a minimal of 1 sat/vbyte?