MIME-Version: 1.0
References: <157744394-3dec42994f1798ce65b00e23b21ea656@pmq2v.m5r2.onet>
In-Reply-To: <157744394-3dec42994f1798ce65b00e23b21ea656@pmq2v.m5r2.onet>
From: Zac Greenwood <zachgrw@gmail.com>
Date: Thu, 24 Feb 2022 22:40:57 +0100
Message-ID: <CAJ4-pEBnprd-SdXMZeDsJ37=SiGbQEnaFfpvBzryR21Wbqc1Ew@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 vjudeu@gazeta.pl
Content-Type: multipart/alternative; boundary="00000000000099470205d8ca7059"
Subject: Re: [bitcoin-dev] OP_RETURN inside TapScript
Precedence: list

--00000000000099470205d8ca7059
Content-Type: text/plain; charset="UTF-8"

Reducing the footprint of storing data on-chain might better be achieved by
*supporting* it.

Currently storing data is wasteful because it is embedded inside an
OP_RETURN within a transaction structure. As an alternative, by supporting
storing of raw data without creating a transaction, waste can be reduced.

Storing data in this way must only be marginally cheaper per on-chain byte
than the current method  using OP_RETURN by applying the appropriate
weight-per-byte for on-chain data.

The intended result is a smaller footprint for on-chain data without making
it cheaper (except marginally in order to disincentivize the use of
OP_RETURN).

Zac


On Thu, 24 Feb 2022 at 10:19, vjudeu via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Since Taproot was activated, we no longer need separate OP_RETURN outputs
> to be pushed on-chain. If we want to attach any data to a transaction, we
> can create "OP_RETURN <anything>" as a branch in the TapScript. In this
> way, we can store that data off-chain and we can always prove that they are
> connected with some taproot address, that was pushed on-chain. Also, we can
> store more than 80 bytes for "free", because no such taproot branch will be
> ever pushed on-chain and used as an input. That means we can use "OP_RETURN
> <1.5 GB of data>", create some address having that taproot branch, and
> later prove to anyone that such "1.5 GB of data" is connected with our
> taproot address.
>
> Currently in Bitcoin Core we have "data" field in "createrawtransaction".
> Should the implementation be changed to place that data in a TapScript
> instead of creating separate OP_RETURN output? What do you think?
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"auto">Reducing the footprint of storing data on-chain might bet=
ter be achieved by *supporting* it.</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Currently storing data is wasteful because it is embedded insid=
e an OP_RETURN within a transaction structure. As an alternative, by suppor=
ting storing of raw data without creating a transaction, waste can be reduc=
ed.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Storing data in this=
 way must only be marginally cheaper per on-chain byte than the current met=
hod =C2=A0using OP_RETURN by applying the appropriate weight-per-byte for o=
n-chain data.</div><div dir=3D"auto"><br></div><div dir=3D"auto">The intend=
ed result is a smaller footprint for on-chain data without making it cheape=
r (except marginally in order to disincentivize the use of OP_RETURN).=C2=
=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Zac</div><div dir=3D=
"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">On Thu, 24 F=
eb 2022 at 10:19, vjudeu via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@=
lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wr=
ote:</div><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:=
solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div>Since Tapro=
ot was activated, we no longer need separate OP_RETURN outputs to be pushed=
 on-chain. If we want to attach any data to a transaction, we can create &q=
uot;OP_RETURN &lt;anything&gt;&quot; as a branch in the TapScript. In this =
way, we can store that data off-chain and we can always prove that they are=
 connected with some taproot address, that was pushed on-chain. Also, we ca=
n store more than 80 bytes for &quot;free&quot;, because no such taproot br=
anch will be ever pushed on-chain and used as an input. That means we can u=
se &quot;OP_RETURN &lt;1.5 GB of data&gt;&quot;, create some address having=
 that taproot branch, and later prove to anyone that such &quot;1.5 GB of d=
ata&quot; is connected with our taproot address.</div>
<div>=C2=A0</div>
<div>Currently in Bitcoin Core we have &quot;data&quot; field in &quot;crea=
terawtransaction&quot;. Should the implementation be changed to place that =
data in a TapScript instead of creating separate OP_RETURN output? What do =
you think?</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>

--00000000000099470205d8ca7059--