1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Return-Path: <akaramaoun@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0A9E788A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 28 Jan 2017 18:35:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4EE87196
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 28 Jan 2017 18:35:00 +0000 (UTC)
Received: by mail-wm0-f47.google.com with SMTP id c85so159721953wmi.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 28 Jan 2017 10:35:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to; bh=FKIwHoVN5PG5c/GYGrknIROA2q24XMcC9PTF498qs4M=;
b=D2xJgwovFVWciYsHc4jaJ/g+xP5C02NFCa75tZVd3mlljSCmBxCFWxRytzqyI/e7Em
agCk5zd+0Fd8cKKA1//RLmPW6W5Q89KDNpcriQsBKRYujSPFJ9z1qYPeTmGRZzvvHaJI
786zmYQA0AIAoeddIosh0IIM1eRuKT+DfdruzVVnWc4bRbXgCfNVPGaUHtQsbXs4RW0h
MInBHTbbtU8dGm3PucyutS/SvXoal2m7wc97Q6XOqzn+73l+r3swsfF9lc0LbYooiXxJ
82xqj55L7EdoY3hpjXPvRKya1jeyRgtsDMSTTHAhXE0jrK5HVSpxLeB8DYql1JJzZqix
N1DQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to;
bh=FKIwHoVN5PG5c/GYGrknIROA2q24XMcC9PTF498qs4M=;
b=SGRk4ud2hniGnMGQhe/AE8WPXjOqAQFxYIy8qgUs5f3RWGhxb7CBicmFqVfeN/6Po3
OA4JPK0m+jzgTGakOnPsIGvCsqzqFiBWa4siaLAmHf0YbbHcM/bmtpxQXsJ1C6B/SItZ
9rWl56jbURFfJyZWoSk7ccKzvzzRheBJtJwgaprqxeLbNQRuOdaEGhOoKQyijySyRtqH
I9h//3SGqBGcuhTAa62KuwqFhgGMCgz8vzPKRcQj/f5WpnKbjfq30Sy8oCeZiTUb92D1
UdemJ7TopVRMvLu2RMiq/vUJSpOZPtB6q5L6lIOjxKaS2rHZiczdKhUYvtcvHA9rfpL/
0Sag==
X-Gm-Message-State: AIkVDXIeG+N/PQRhYQLtZJRCbohXmqYTlecG3e4RPPQKaKdCxQZvKBpGu2DDrgtWbICxfcgLkQ5aK8H9IJhoqQ==
X-Received: by 10.28.132.9 with SMTP id g9mr8593361wmd.28.1485628498823; Sat,
28 Jan 2017 10:34:58 -0800 (PST)
MIME-Version: 1.0
Sender: akaramaoun@gmail.com
Received: by 10.28.226.134 with HTTP; Sat, 28 Jan 2017 10:34:58 -0800 (PST)
In-Reply-To: <20170112195830.GA5663@savin.petertodd.org>
References: <2ac49fb0-ff79-5cb9-7b92-14ec791ecc45@dyne.org>
<CAB3F3DtJ3Hq5saz7fVd95bhi+Y84m6U1GuduHOGyXuhVwRaWeg@mail.gmail.com>
<20170112195830.GA5663@savin.petertodd.org>
From: Andrew <onelineproof@gmail.com>
Date: Sat, 28 Jan 2017 18:34:58 +0000
X-Google-Sender-Auth: DSBzLS-0pEIpgTKoEYcM3oGVoGw
Message-ID: <CAL8tG==tQ7N98FNDcWCSRqe87pBkS3pc3dO3tzioSAtyXSWqLA@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Transaction Replacement by Fee
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jan 2017 18:35:01 -0000
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@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@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647
|
