Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Johnson Lau <jl2012@xbt.hk>
In-Reply-To: <sujR-1TPC3DI-bNyQD2U5c5E0qkkfi6WezKQOfB9YgP7UbLj3x-maV0ooIqvJ4C2V_yjkrq78F7QqIZ5LyoZuSKcpC08RFWapH2k-FF3_zc=@protonmail.com>
Date: Fri, 10 May 2019 00:56:57 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBADD452-6DAE-46D4-9511-69F8EAA02FFB@xbt.hk>
References: <CAPg+sBg6Gg8b7hPogC==fehY3ZTHHpQReqym2fb4XXWFpMM-pQ@mail.gmail.com>
	<201905062017.11396.luke@dashjr.org>
	<sujR-1TPC3DI-bNyQD2U5c5E0qkkfi6WezKQOfB9YgP7UbLj3x-maV0ooIqvJ4C2V_yjkrq78F7QqIZ5LyoZuSKcpC08RFWapH2k-FF3_zc=@protonmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
	bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Cc: Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [bitcoin-dev] Taproot proposal
Precedence: list


>=20
>>=20
>> Some way to sign an additional script (not committed to by the =
witness
>> program) seems like it could be a trivial addition.
>=20
> It seems to me the annex can be used for this, by having it contain =
both the script and the signature somehow concatenated.

This is not possible since the whole annex is signed. It is possible if =
the signed =E2=80=9Cscript=E2=80=9D does not require further input, like =
per-input lock-time, relative lock-time, check block hash


>=20
> Regards,
> ZmnSCPxj
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev