MIME-Version: 1.0
References: <46175970-d2ab-a58e-7010-f29820849604@gmail.com>
 <CAO3Pvs9t0H_TpqihPLeknHX30dmtzUgoA+-7uV4UOnrmacsAtQ@mail.gmail.com>
In-Reply-To: <CAO3Pvs9t0H_TpqihPLeknHX30dmtzUgoA+-7uV4UOnrmacsAtQ@mail.gmail.com>
From: Olaoluwa Osuntokun <laolu32@gmail.com>
Date: Wed, 27 Apr 2022 20:53:59 -0700
Message-ID: <CAO3Pvs9sCU+zV9UPdrQ4xcF08vLy5zoA_4PUC6F5QjaHNo8uYA@mail.gmail.com>
To: Jonas Nick <jonasdnick@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000e2706b05ddaee028"
Subject: Re: [bitcoin-dev] MuSig2 BIP
Precedence: list

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

Stating the taproot interaction more plainly: the taproot tweak is defined
as a function of the internal key itself h_tapTeak(internalKey || rootHash),
which means that the full tweak can't be known ahead of time. Instead, one
must aggregate the keys to obtain the internal key _then_ apply the tweaks
as normal.

-- Laolu

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

<div dir=3D"ltr">Stating the taproot interaction more plainly: the taproot =
tweak is defined<br>as a function of the internal key itself h_tapTeak(inte=
rnalKey || rootHash),<br>which means that the full tweak can&#39;t be known=
 ahead of time. Instead, one<br>must aggregate=C2=A0the keys to obtain the =
internal key _then_ apply the tweaks<br>as normal.=C2=A0<br><br>-- Laolu<br=
></div>

--000000000000e2706b05ddaee028--