summaryrefslogtreecommitdiff
path: root/4a/95bf3c0f3ef971400190fcedb1a98465f88bd8
blob: 5a221c3ecf1974e80201c4737929d67b6c3eff47 (plain)
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
113
114
115
116
117
118
119
120
121
Return-Path: <jim.posen@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 79F42F4E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 15 Mar 2018 20:53:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com
	[209.85.223.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2B4172C4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 15 Mar 2018 20:53:36 +0000 (UTC)
Received: by mail-io0-f175.google.com with SMTP id m83so10139031ioi.8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 15 Mar 2018 13:53:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=qyShQzynIDibJYlZg6UBl2BqTMihJzwOtUfSzx8SYQs=;
	b=PuLwHX64uHcgXRy5wkspXeT5FTef7psa9EGRlkMB9Y9zSiKvMbgq1MZwO8YXYy9Hcw
	6DtObARfQJqT6rNUw+8Jfhu2QoXL/qhy3eugY9mIN4nri0OLh8aTj0Sv3X7Slyh40DtI
	5ufV3HG+MiDsC6t+SlxrGLdZfy3TnmGlHHlU+WMdfP2gY0smB/vtlwBg0AD5qy+A0Imn
	Zf2vjfwkeb3YXgykqGzv8FbXOw8AaryFt0pcdVLiJ+aYhrvh4fRSggJqn3aRjdTZ3/za
	lDQVYuCssa76+4TRGIsPOccg7dYS8PAYi+1pjT1/fa9q4wy8o/K1K+qdTqodZWCnKzN8
	8J+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=qyShQzynIDibJYlZg6UBl2BqTMihJzwOtUfSzx8SYQs=;
	b=IL7Ersu8qJh6dGAMaVlocHio2ZFDlLpl6UmiNebkRewMVa5GFzLauFYY1SthQTnKVG
	IyJjdsCeyIhhCSrthKBLPrRc1Odik4gE8c5LU8sXO8K0rVKNXAMwBDS7XumLjTWlHJ2P
	SaLkqrUY+uIO0pwbO7hm1no08L2FqDC1IdbOZOAzwjTtecD83OfnEtxDu38ssM4pJmUs
	Lo9HueQetJy/Cuof9s+ts69t/qtuIAzK3yryeygkNA2dbIBRVDYXMFLWAHkTvOrEFsLp
	PXbWj7y1ohNSE+Ynw425LADcy0wvpgkGPaMmu2sJ2EJ7cY4IBhkB+JwabGBMWWB10Nod
	rKGw==
X-Gm-Message-State: AElRT7FGVsWy11FlQnsfKLaJGmEmWAbSOqYGKUb9FTFfh/Q9Z787fedB
	q4QCXXK7GNuabK7ffNE6hC5AW4lxs8ashuf489c41A==
X-Google-Smtp-Source: AG47ELu1KSD1e1EBJY2sfaDUzOfLytPEHEYgPte9MH6TpFDqwBg0fhDWd5EVFCGsxViRgeVbJdF9AFaD4xBIvYA11fY=
X-Received: by 10.107.135.157 with SMTP id r29mr10473087ioi.248.1521147215303; 
	Thu, 15 Mar 2018 13:53:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.90.16 with HTTP; Thu, 15 Mar 2018 13:53:34 -0700 (PDT)
In-Reply-To: <CALJw2w7LAUB+7FpLSGz=+pL7y_t5sy0yGuhYML7yJjuKc8Uw_w@mail.gmail.com>
References: <CALJw2w5=g-FL+MZ08DEoLxVzOKbSXeKu50drE1b4P0JZJpdTyA@mail.gmail.com>
	<CAPswA9xuVT74L87QO9TXGc6=O6Gd2kbQMBdmn=7zUm5OHXcfOA@mail.gmail.com>
	<CALJw2w719qQnyvaJbe1wc39+4ERDST+zXCOjt0DiJpktD74QCA@mail.gmail.com>
	<CADZtCSiSCDb1dzLCgr24jCNzzmcfsXuPyNVh+YJJ6rNqdsQh2Q@mail.gmail.com>
	<CALJw2w7LAUB+7FpLSGz=+pL7y_t5sy0yGuhYML7yJjuKc8Uw_w@mail.gmail.com>
From: Jim Posen <jim.posen@gmail.com>
Date: Thu, 15 Mar 2018 13:53:34 -0700
Message-ID: <CADZtCSj8HJm+7DswrPXPibSGGSAb4xE4S=AT9ur_v0HDmCp1Nw@mail.gmail.com>
To: Karl Johan Alm <karljohan-alm@garage.co.jp>
Content-Type: multipart/alternative; boundary="001a113fbf206b5899056779afd5"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	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: Thu, 15 Mar 2018 21:02:40 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] {sign|verify}message replacement
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: Thu, 15 Mar 2018 20:53:36 -0000

--001a113fbf206b5899056779afd5
Content-Type: text/plain; charset="UTF-8"

>
> Good question.. Since you don't really have the input(s), I think it's
> fine to always assume sufficient time/height on CLTV/CSV checks.
>

In this general signing-a-script context, I think a verifier might want to
see the time conditions under which it may be spent. The proof container
could include an optional nLockTime which defaults to 0 and nSequence which
defaults to 0xFFFF...


> I think it would just use the default (SIGHASH_ALL?) for simplicity.
> Is there a good reason to tweak it?
>

I took another look and there should definitely be a byte appended to the
end of the sig so that the encoding checks pass, but I think it might as
well be a 0x00 byte since it's not actually a sighash flag.

--001a113fbf206b5899056779afd5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Good question.. Since you don&#39;t really have =
the input(s), I think it&#39;s<br>
fine to always assume sufficient time/height on CLTV/CSV checks.<span class=
=3D""><br></span></blockquote><div><br></div><div>In this general signing-a=
-script context, I think a verifier might want to see the time conditions u=
nder which it may be spent. The proof container could include an optional n=
LockTime which defaults to 0 and nSequence which defaults to 0xFFFF...</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
</span>I think it would just use the default (SIGHASH_ALL?) for simplicity.=
<br>
Is there a good reason to tweak it?<br></blockquote><div><br></div><div>I t=
ook another look and there should definitely be a byte appended to the end =
of the sig so that the encoding checks pass, but I think it might as well b=
e a 0x00 byte since it&#39;s not actually a sighash flag.</div><div><br></d=
iv></div></div></div>

--001a113fbf206b5899056779afd5--