Thank you guys!
It's working!
Topic: Replace-By-Fee with createrawtransaction is not working (Bitcoin Core v. 0.14.1) (Read 530 times)
July 04, 2017, 07:07:41 PM
July 04, 2017, 06:13:09 PM
The walletrbf=1 option sets RBF for transactions made by the wallet. Createrawtransaction is not part of the wallet, so this option doesn't affect it. In createrawtransaction, there's an optional sequence field that you can set when specifying the inputs. To set a transaction to Opt into RBF, you need to set the sequence for at least one input to be 4294967293 or lower.
July 04, 2017, 05:59:12 PM
When you create the raw transaction, try and set the sequence number to something less than "4294967295"... ie. less than the MAX_UINT32 value. (0xFFFFFFFF)
Looking at the RBF transactions that my wallet has automatically created via the GUI, they had a "sequence" value of : 4294967293
This seems to be the only requirement to mark your transaction as being "RBF".
Looking at the RBF transactions that my wallet has automatically created via the GUI, they had a "sequence" value of : 4294967293
This seems to be the only requirement to mark your transaction as being "RBF".
July 04, 2017, 04:45:02 PM
I'm use walletrbf=1 in config for my Bitcoin Core v. 0.14.1 client.
When I try to send transaction with "bitcoin-cli sendfrom" the flag bip125-replaceable (Replace By Fee) is setting to "yes" correctly.
But if I try to make transaction with
"bitcoin-cli createrawtransaction"
"bitcoin-cli signrawtransaction"
Replace By Fee is not setting (bip125-replaceable=no).
What should I do for making transaction with Replace By Fee by createrawtransaction?
Or this is a Bitcoin Core bug?
When I try to send transaction with "bitcoin-cli sendfrom" the flag bip125-replaceable (Replace By Fee) is setting to "yes" correctly.
But if I try to make transaction with
"bitcoin-cli createrawtransaction"
"bitcoin-cli signrawtransaction"
Replace By Fee is not setting (bip125-replaceable=no).
What should I do for making transaction with Replace By Fee by createrawtransaction?
Or this is a Bitcoin Core bug?
Jump to: