Hi, recently been trying to get RBF working on a multisig input. I set
the nSequence to 0, but script didn't verify (used python-bitcoinlib).
Should it work for this type of transaction? I am using the
SignatureHash(...) method of signing, not rpc.signrawtransaction(...).
Thanks
On Thu, Jan 12, 2
On Thu, Jan 12, 2017 at 09:13:23AM -0500, Greg Sanders via bitcoin-dev wrote:
> BIP125 is the standard way to signal:
> https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
>
> Should explain everything you need.
Additionally some miners mine full replace-by-fee, which has no limitation
BIP125 is the standard way to signal:
https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
Should explain everything you need.
On Thu, Jan 12, 2017 at 9:02 AM, Police Terror via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> Where can I find the rules on trans
Hello,
Where can I find the rules on transaction replacement?
For instance what are the valid ranges for the sequence values in
transaction inputs? Normally I set this value to MAX_UINT32, and the
locktime to 0.
Can I change the outputs? Can I add more inputs to pay a higher fee?
Just looking f
