Correct. Just restart without -reindex
Than you for your replay!
I will restart bitcoind without -reindex, and then try to sendrawtransaction agan.
Topic: 64: too-long-mempool-chain (Read 251 times)
Than you for your replay!
I will restart bitcoind without -reindex, and then try to sendrawtransaction agan.
No need to do that. This has nothing to do with the databases.
Does this means that there is no need for adding reindex options ?2. Restart bitcoind (← without adding -reindex options)
Sure, you can do that, but that does not mean that your transactions will actually be relayed across the network. Just because you have this in your config does not mean that your peers will so they likely won't accept any transactions once you reach the default limit. Your local config only applies to your node. Changing this just means the transactions will sit in your node's mempool (and not be relayed across the network). They won't even be rebroadcast by your node because nodes don't do that.
Tank you for the explanation. I understand.If I override the default limit , this applies only to my node.
Instead of trying to get long unconfirmed transaction chains to be relayed, you should be rethinking why you are generating long unconfirmed transaction chains and thinking of ways that you can avoid making long unconfirmed transaction chains instead.
Thank you for your advice. I will try to improve it.No need to do that. This has nothing to do with the databases.
Does this means that there is no need for adding reindex options ?2. Restart bitcoind (← without adding -reindex options)
Can I override the default limit of 25 unconfirmed transactions by adding to cofiguration file as below.
1. Additionally write to configuration file.
bitcoin.conf-----------------------
limitancestorcount=1000 ← e.g. 1000
limitdescedantcount=1000 ← e.g. 1000
----------------------------------
Sure, you can do that, but that does not mean that your transactions will actually be relayed across the network. Just because you have this in your config does not mean that your peers will so they likely won't accept any transactions once you reach the default limit. Your local config only applies to your node. Changing this just means the transactions will sit in your node's mempool (and not be relayed across the network). They won't even be rebroadcast by your node because nodes don't do that.1. Additionally write to configuration file.
bitcoin.conf-----------------------
limitancestorcount=1000 ← e.g. 1000
limitdescedantcount=1000 ← e.g. 1000
----------------------------------
Instead of trying to get long unconfirmed transaction chains to be relayed, you should be rethinking why you are generating long unconfirmed transaction chains and thinking of ways that you can avoid making long unconfirmed transaction chains instead.
2. Restart bitcoind with -reindex options.
No need to do that. This has nothing to do with the databases. I believe that means there are too many "unconfirmed" parent transactions... You can try using the suggestion here: https://bitcoin.stackexchange.com/questions/59178/64-too-long-mempool-chain
By using the -limitancestorcount and/or -limitdescedantcount commandline arguments, you can override the default limit of 25 unconfirmed transactions.
Thank you for your answer.By using the -limitancestorcount and/or -limitdescedantcount commandline arguments, you can override the default limit of 25 unconfirmed transactions.
Surely you are right.
There are too many "unconfirmed" parent transactions.
Can I override the default limit of 25 unconfirmed transactions by adding to cofiguration file as below.
1. Additionally write to configuration file.
bitcoin.conf-----------------------
limitancestorcount=1000 ← e.g. 1000
limitdescedantcount=1000 ← e.g. 1000
----------------------------------
2. Restart bitcoind with -reindex options.
Then try to sendrawtransaction again.
How about this ?
I believe that means there are too many "unconfirmed" parent transactions... You can try using the suggestion here: https://bitcoin.stackexchange.com/questions/59178/64-too-long-mempool-chain
By using the -limitancestorcount and/or -limitdescedantcount commandline arguments, you can override the default limit of 25 unconfirmed transactions.
By using the -limitancestorcount and/or -limitdescedantcount commandline arguments, you can override the default limit of 25 unconfirmed transactions.
I'm running full node bitcoin server and use bitcoin-core RPC library.
I sent transaction by using rpc command 'sendrawtransaction'
but the result returned err as below.
「64: too-long-mempool-chain」
So I checked memopool by using rpc command 'getmempoolinfo', then returned as follows.
{
"size": 0,
"bytes": 0,
"usage": 96,
"maxmempool": 300000000,
"mempoolminfee": 0.00000000
}
What should I do for sending transaction successfully ?
Additinal information.
I use Bitcoin Core : version 0.13
I sent transaction by using rpc command 'sendrawtransaction'
but the result returned err as below.
「64: too-long-mempool-chain」
So I checked memopool by using rpc command 'getmempoolinfo', then returned as follows.
{
"size": 0,
"bytes": 0,
"usage": 96,
"maxmempool": 300000000,
"mempoolminfee": 0.00000000
}
What should I do for sending transaction successfully ?
Additinal information.
I use Bitcoin Core : version 0.13
Jump to: