I used to be testing Bitcoin Core 31.0 to see if I may make chains of unconfirmed transactions longer than 25. Launch notes say:
The mempool not enforces ancestor or descendant measurement/depend limits. As a substitute, two new default coverage limits are launched governing related parts, or clusters, within the mempool, limiting clusters to 64 transactions and as much as 101 kB in digital measurement. Transactions are thought of to be in the identical cluster if they’re related to one another by way of any mixture of father or mother/baby relationships within the mempool. These limits will be overridden utilizing command-line arguments; see the prolonged assist (-help-debug) for extra info.
Does this solely maintain for transactions being relayed to my node, and never for transactions my pockets creates? Does the pockets nonetheless implement the 25 txn restrict throughout a transition interval till the brand new mempool coverage is extra widespread?
The next script on a newly began Bitocoin Core 31.0 regtest node fails on the final command:
bitcoin-cli getnetworkinfo
bitcoin-cli createwallet miner
ADDR=`bitcoin-cli getnewaddress`
bitcoin-cli generatetoaddress 101 $ADDR
# 1 confirmed UTXO
for i in `seq 0 24`; do
bitcoin-cli sendtoaddress $ADDR 1
performed
# We now have a series of 25 unconfirmed txs
# I anticipated including yet another would work on bitcoin core 31.0
bitcoin-cli sendtoaddress $ADDR 1
Output seems to be one thing like this:
{
"model": 310000,
"subversion": "/Satoshi:31.0.0/",
...
61000fa3b63cba73ed407258ec8b814c07dd4b5c32e2f89c34ca32716f6338c1
69644eea749b113a97d0b140511486e2d4acf63cc713078f7180d637849f883c
8b282b62858ae5fa75983739e4981db77734ff873a7cc759bd51e7ddee93d6c6
error code: -6
error message:
Unconfirmed UTXOs can be found, however spending them creates a series of transactions that will probably be rejected by the mempool
I used to be testing Bitcoin Core 31.0 to see if I may make chains of unconfirmed transactions longer than 25. Launch notes say:
The mempool not enforces ancestor or descendant measurement/depend limits. As a substitute, two new default coverage limits are launched governing related parts, or clusters, within the mempool, limiting clusters to 64 transactions and as much as 101 kB in digital measurement. Transactions are thought of to be in the identical cluster if they’re related to one another by way of any mixture of father or mother/baby relationships within the mempool. These limits will be overridden utilizing command-line arguments; see the prolonged assist (-help-debug) for extra info.
Does this solely maintain for transactions being relayed to my node, and never for transactions my pockets creates? Does the pockets nonetheless implement the 25 txn restrict throughout a transition interval till the brand new mempool coverage is extra widespread?
The next script on a newly began Bitocoin Core 31.0 regtest node fails on the final command:
bitcoin-cli getnetworkinfo
bitcoin-cli createwallet miner
ADDR=`bitcoin-cli getnewaddress`
bitcoin-cli generatetoaddress 101 $ADDR
# 1 confirmed UTXO
for i in `seq 0 24`; do
bitcoin-cli sendtoaddress $ADDR 1
performed
# We now have a series of 25 unconfirmed txs
# I anticipated including yet another would work on bitcoin core 31.0
bitcoin-cli sendtoaddress $ADDR 1
Output seems to be one thing like this:
{
"model": 310000,
"subversion": "/Satoshi:31.0.0/",
...
61000fa3b63cba73ed407258ec8b814c07dd4b5c32e2f89c34ca32716f6338c1
69644eea749b113a97d0b140511486e2d4acf63cc713078f7180d637849f883c
8b282b62858ae5fa75983739e4981db77734ff873a7cc759bd51e7ddee93d6c6
error code: -6
error message:
Unconfirmed UTXOs can be found, however spending them creates a series of transactions that will probably be rejected by the mempool
