MIME-Version: 1.0
From: Joost Jager <joost.jager@gmail.com>
Date: Fri, 2 Jun 2023 17:00:37 +0200
Message-ID: <CAJBJmV-L4FusaMNV=_7L39QFDKnPKK_Z1QE6YU-wp2ZLjc=RrQ@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000f6fe9305fd26d2d3"
Subject: [bitcoin-dev] Standardisation of an unstructured taproot annex
Precedence: list

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

Hi,

As it stands, the taproot annex is consensus valid but non-standard. The
conversations around standardization seem to be leaning towards the
adoption of a flexible Type-Length-Value (TLV) format [1]. There's no doubt
that this approach has considerable potential. However, settling on an
exact format may require a significant amount of time.

In the interim, the benefits of making the annex available in a
non-structured form are both evident and immediate. By allowing developers
to utilize the taproot annex without delay, we can take advantage of its
features today, without the need to wait for the finalization of a more
lengthy standardization process.

With this in view, I am proposing that we define any annex that begins with
'0' as free-form, without any additional constraints. This strategy offers
several distinct benefits:

Immediate utilization: This opens the door for developers to make use of
the taproot annex for a variety of applications straight away, thus
eliminating the need to wait for the implementation of TLV or any other
structured format.

Future flexibility: Assigning '0'-beginning annexes as free-form keeps our
options open for future developments and structure improvements. As we
forge ahead in determining the best way to standardize the annex, this
strategy ensures we do not limit ourselves by setting its structure in
stone prematurely.

Chainspace efficiency: Non-structured data may require fewer bytes compared
to a probable TLV format, which would necessitate the encoding of length
even when there's only a single field.

In conclusion, adopting this approach will immediately broaden the
utilization scope of the taproot annex while preserving the possibility of
transitioning to a more structured format in the future. I believe this is
a pragmatic and efficient route, one that can yield substantial benefits in
both the short and long term.

Joost

[1] https://github.com/bitcoin/bips/pull/1381

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

<div dir=3D"ltr">Hi,<br><br>As it stands, the taproot annex is consensus va=
lid but non-standard. The conversations around standardization seem to be l=
eaning towards the adoption of a flexible Type-Length-Value (TLV) format [1=
]. There&#39;s no doubt that this approach has considerable potential. Howe=
ver, settling on an exact format may require a significant amount of time.<=
br><br>In the interim, the benefits of making the annex available in a non-=
structured form are both evident and immediate. By allowing developers to u=
tilize the taproot annex without delay, we can take advantage of its featur=
es today, without the need to wait for the finalization of a more lengthy s=
tandardization process.<br><br>With this in view, I am proposing that we de=
fine any annex that begins with &#39;0&#39; as free-form, without any addit=
ional constraints. This strategy offers several distinct benefits:<br><br>I=
mmediate utilization: This opens the door for developers to make use of the=
 taproot annex for a variety of applications straight away, thus eliminatin=
g the need to wait for the implementation of TLV or any other structured fo=
rmat.<br><br>Future flexibility: Assigning &#39;0&#39;-beginning annexes as=
 free-form keeps our options open for future developments and structure imp=
rovements. As we forge ahead in determining the best way to standardize the=
 annex, this strategy ensures we do not limit ourselves by setting its stru=
cture in stone prematurely.<br><br>Chainspace efficiency: Non-structured da=
ta may require fewer bytes compared to a probable TLV format, which would n=
ecessitate the encoding of length even when there&#39;s only a single field=
. <br><br>In conclusion, adopting this approach will immediately broaden th=
e utilization scope of the taproot annex while preserving the possibility o=
f transitioning to a more structured format in the future. I believe this i=
s a pragmatic and efficient route, one that can yield substantial benefits =
in both the short and long term.<br><br>Joost<br><br>[1] <a href=3D"https:/=
/github.com/bitcoin/bips/pull/1381">https://github.com/bitcoin/bips/pull/13=
81</a></div>

--000000000000f6fe9305fd26d2d3--