📅 Original date posted:2017-01-28
📝 Original message: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, 2017 at 7:58 PM, Peter Todd via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> 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 limitations on
> nSequence. My implementation (for v0.13.2) is here:
>
> https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.13.2
>
> and is identical to Bitcoin Core modulo the nSequence stuff being removed, and
> a special service bit added to allow full-rbf nodes to preferentially peer with
> each other to make sure replacement transactions get propagated.
>
> In practice full-RBF works fairly well, so while it's even faster to use the
> nSequence signalling specified in BIP-125, doing so is not mandatory so long as
> you can et your replacement transaction to a full-RBF node.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647
Andrew [ARCHIVE] /
npub1l8…hm88x
2023-06-07 17:55:32
in reply to nevent1q…uhsv
Author Public Key
npub1l899vmy2zhg9zr96jvnxt85ayddd26qu36m02k22759e9djqldnqrhm88xPublished at
2023-06-07 17:55:32Event JSON
{
"id": "98f5cb23b230a3eae679c43168247057168f4593bfe9cbb753c6537fd18e6688",
"pubkey": "f9ca566c8a15d0510cba9326659e9d235ad5681c8eb6f5594af50b92b640fb66",
"created_at": 1686160532,
"kind": 1,
"tags": [
[
"e",
"9500affc1d70d507762ec90535492732302f598e9dd922cc4d8e989696627145",
"",
"root"
],
[
"e",
"da689aac978a241b2596beac4b12b42696eb29c750795eacae21850d78afe4f8",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2017-01-28\n📝 Original message:Hi, recently been trying to get RBF working on a multisig input. I set\nthe nSequence to 0, but script didn't verify (used python-bitcoinlib).\nShould it work for this type of transaction? I am using the\nSignatureHash(...) method of signing, not rpc.signrawtransaction(...).\n\nThanks\n\nOn Thu, Jan 12, 2017 at 7:58 PM, Peter Todd via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e On Thu, Jan 12, 2017 at 09:13:23AM -0500, Greg Sanders via bitcoin-dev wrote:\n\u003e\u003e BIP125 is the standard way to signal:\n\u003e\u003e https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki\n\u003e\u003e\n\u003e\u003e Should explain everything you need.\n\u003e\n\u003e Additionally some miners mine full replace-by-fee, which has no limitations on\n\u003e nSequence. My implementation (for v0.13.2) is here:\n\u003e\n\u003e https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.13.2\n\u003e\n\u003e and is identical to Bitcoin Core modulo the nSequence stuff being removed, and\n\u003e a special service bit added to allow full-rbf nodes to preferentially peer with\n\u003e each other to make sure replacement transactions get propagated.\n\u003e\n\u003e In practice full-RBF works fairly well, so while it's even faster to use the\n\u003e nSequence signalling specified in BIP-125, doing so is not mandatory so long as\n\u003e you can et your replacement transaction to a full-RBF node.\n\u003e\n\u003e --\n\u003e https://petertodd.org 'peter'[:-1]@petertodd.org\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\n\n\n-- \nPGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647",
"sig": "3d275fc712cdbb5d9b6846c44e41178bf2bc5001892b335e299de7b5ec5b320b521731d06784d665179fce4d7b29bc7f714078720273fc833c355a8321ad2a36"
}