MIME-Version: 1.0
References: <bf96c2fb-2e2e-a47f-e59f-87e56d83eca3@mattcorallo.com>
In-Reply-To: <bf96c2fb-2e2e-a47f-e59f-87e56d83eca3@mattcorallo.com>
From: "Russell O'Connor" <roconnor@blockstream.io>
Date: Thu, 7 Mar 2019 10:16:43 -0500
Message-ID: <CAMZUoKneArC+YZ36YFwxNTKsDtJhEz5P2cosXKxJS8Rf_3Nyuw@mail.gmail.com>
To: Matt Corallo <lf-lists@mattcorallo.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000b489f0058382983e"
Subject: [bitcoin-dev] Sighash Type Byte;
	Re: BIP Proposal: The Great Consensus Cleanup
Precedence: list

--000000000000b489f0058382983e
Content-Type: text/plain; charset="UTF-8"

> * If the sighash type byte (ie last byte in a signature being evaluated
> during the execution of OP_CHECKSIG[VERIFY] or OP_CHECKMULTISIG[VERIFY])
> is anything other than 1, 2, 3, 0x81, 0x82, or 0x83, the script
> execution fails. This does not apply to 0-length signature stack elements.
>

The sighash type byte is a "great" place to store a few bits of ancillary
data when making signatures.  Okay it isn't great, but it is good enough
that some misguided users may have been using it and have unbroadcast
transactions in cold storage (think sweeps) for UTXOs whose private keys
may have been lost.  I don't think that one's hunch that there isn't much
risk in disabling these sighashes is good enough to put people funds at
risk, especially given the alternative proposal of caching the
just-before-the-last-byte sighash midstate that is available.

-- 
Russell O'Connor

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

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
* If the sighash type byte (ie last byte in a signature being evaluated <br=
>
during the execution of OP_CHECKSIG[VERIFY] or OP_CHECKMULTISIG[VERIFY]) <b=
r>
is anything other than 1, 2, 3, 0x81, 0x82, or 0x83, the script <br>
execution fails. This does not apply to 0-length signature stack elements.<=
br></blockquote><div><br></div><div>The sighash type byte is a &quot;great&=
quot; place to store a few bits of ancillary data when making signatures.=
=C2=A0 Okay it isn&#39;t great, but it is good enough that some misguided u=
sers may have been using it and have unbroadcast transactions in cold stora=
ge (think sweeps) for UTXOs whose private keys may have been lost.=C2=A0 I =
don&#39;t think that one&#39;s hunch that there isn&#39;t much risk in disa=
bling these sighashes is good enough to put people funds at risk, especiall=
y given the alternative proposal of caching the just-before-the-last-byte s=
ighash midstate that is available.</div><div><br></div><div>-- <br></div><d=
iv>Russell O&#39;Connor<br></div></div></div>

--000000000000b489f0058382983e--