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
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A4B14910
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 24 Nov 2018 08:14:07 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sender-of-o53.zoho.com (sender-of-o53.zoho.com [135.84.80.218])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 25CC019B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 24 Nov 2018 08:14:06 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; t=1543047237; cv=none; d=zoho.com; s=zohoarc;
b=IPtKPDcwQRTaCwAv76FwY/PYdOcC11EuUdvVWD9NEz0dHekmZ03igP7s27/RWIijhiGOouMQGmjmtVNzuraCqCcOWcTe457nWdWw7t8TEI0iIxiuGmLRUtU+HpO3NQuIjCMrU9WBVE5p8uq3gy7AqYihJkZ0xI9Mcz6hKEJl/dA=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com;
s=zohoarc; t=1543047237;
h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To:ARC-Authentication-Results;
bh=B3FkV38L1kEli1oKELrHWh/YwIen4hGO3JtLEtFCayo=;
b=aOc/80LWcdDK1n4Y3tnUNVid7djJpYYdwaPTfFdDgvMsLjLDuTKVAq/9ddB7uBJK3NuiV66WVhMeAb0j+S1Yhe6Mc9sR0zaSQTto55kA66lpp+xvP6sf9sBVcEaZmWUZcHP5iKl5j7DbdTMBadtbSpjFGSBz6H1VenTXtSGX31A=
ARC-Authentication-Results: i=1; mx.zoho.com; dkim=pass header.i=xbt.hk;
spf=pass smtp.mailfrom=jl2012@xbt.hk;
dmarc=pass header.from=<jl2012@xbt.hk> header.from=<jl2012@xbt.hk>
Received: from [10.8.0.105] (n218103234118.netvigator.com [218.103.234.118])
by mx.zohomail.com with SMTPS id 1543047234996206.2456985917088;
Sat, 24 Nov 2018 00:13:54 -0800 (PST)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: Johnson Lau <jl2012@xbt.hk>
In-Reply-To: <878t1kcet7.fsf@gmail.com>
Date: Sat, 24 Nov 2018 16:13:46 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A562EB2-7041-48E5-9D77-4337B24C3C84@xbt.hk>
References: <CAPg+sBhuPG-2GXc+Bp0yv5ywry2fk56LPLT4AY0Kcs+YEoz4FA@mail.gmail.com>
<87k1l6d6lb.fsf@gmail.com>
<20181123060404.fu4eyzcynbppmjcy@erisian.com.au>
<878t1kcet7.fsf@gmail.com>
To: Christian Decker <decker.christian@gmail.com>,
bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: Apple Mail (2.3445.100.39)
X-ZohoMailClient: External
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 26 Nov 2018 13:52:32 +0000
Subject: Re: [bitcoin-dev] Safer sighashes and more granular SIGHASH_NOINPUT
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, 24 Nov 2018 08:14:07 -0000
> On 23 Nov 2018, at 5:40 PM, Christian Decker via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> Anthony Towns <aj@erisian.com.au> writes:
>> Commiting to just the sequence numbers seems really weird to me; it
>> only really prevents you from adding inputs, since you could still
>> replace any input that was meant to be there by almost any arbitrary
>> other transaction...
>=20
> It's a really roundabout way of committing to the inputs, I
> agree. I'm actually wondering if it makes sense to correct that
> additional blanked field in BIP118 at all since it seems there is no
> real use-case for NOINPUT that doesn't involve blanking the
> `hashSequence` as well.
I think we just make it as simple as this: Always commit to sequence of =
the same input. Commit to hashSequence if and only if all inputs and all =
outputs are signed.
The next-generation SIGHASH will introduce not only NOINPUT, but also =
signing of fees, previous scriptPubKey, and all input values, etc. So it =
won=E2=80=99t be a simple hack over BIP143. BIP118 might be better =
changed to be an informational BIP, focus on the rationale and examples =
of NOINPUT, and be cross-referenced with the consensus BIP.=
|
