MIME-Version: 1.0
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"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] {sign|verify}message replacement
Precedence: list

--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--