MIME-Version: 1.0
References: <CAK=nyAxOa8fsVfxucH7WTTMn25BCzgQ28h_sNsunedpCoRXjjQ@mail.gmail.com>
 <CAMZUoKmR6ZU6mAgEhKDD5cTMuja_OC0_Sz3x4UND=E-g1PkgsQ@mail.gmail.com>
 <CAK=nyAz5+yMUA=XDcunA1eeachSisaJoYE2_yzTLj=B0r4=w5A@mail.gmail.com>
 <iU2J5dWMIgqAf312ZCNmx38_hcYsKrcuqx84kniWeEdb0wP8jPZPvwHK3P-q1yvmQ5OtdMCwMFqPgwmsL7BUfE8PGUlrxW4rOM3slwHun3E=@protonmail.com>
In-Reply-To: <iU2J5dWMIgqAf312ZCNmx38_hcYsKrcuqx84kniWeEdb0wP8jPZPvwHK3P-q1yvmQ5OtdMCwMFqPgwmsL7BUfE8PGUlrxW4rOM3slwHun3E=@protonmail.com>
From: Christopher Gilliard <christopher.gilliard@gmail.com>
Date: Sat, 17 Apr 2021 03:57:55 +0000
Message-ID: <CAK=nyAxJ_XYDhTE6pNHqWOQ-cLgqc_f-fbQ+EHTkxyiYOhOPUQ@mail.gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Content-Type: multipart/alternative; boundary="000000000000a0cd3605c0231a2c"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
Precedence: list

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

Thanks ZmnSCPxj. Yes, I agree there are many ways to embed arbitrary data
in the blockchain and it's not feasible to block all of them. That is why
it's important to, at the same time as limiting the OP_RETURN to one per
block, also propose and implement a layer 2 solution for timestamping
so people have a clear and simple upgrade path. That is what I will be
discussing in one of the BIPs I intend to release early next week.

On Fri, Apr 16, 2021 at 11:52 PM ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote:

> Good morning Christopher,
>
> > >> But more importantly, adding limitations on OP_RETURN transactions is
> not helpful.  Users who want to embed arbitrary data in their transactions
> can always do so by encoding their data inside the values of legacy
> multi-signature scriptpubkeys (pubkeys can be generated without knowing the
> private key in order to encode non-key related data).  Not only can users
> do this, users have done this in the past.  However, this behaviour is
> problematic because such multi-signature "data" scriptpubkeys are
> indistinguishable from "real" multisignature scriptpubkeys, and thus must
> be kept in the UTXO set.  This differs from outputs using OP_RETURN which
> are provably unspendable, and therefore can be safely omitted from the UTXO
> set.
> >
> > This sounds like a good justification to remove the legacy
> multi-signature capabilities as well.
>
> The same technique can be used on P2PKH as well --- the "pubkey hash" need
> not be a hash of a public key, it can be a 20-byte commitment, or even an
> ASCII message like "ZmnSCPxj is the best" (20 characters, I counted).
> There is nothing that *can* check if the hash of a public key is indeed
> the hash of a public key unless you actually reveal the public key.
>
> If you need a 32-byte commitment, a P2WSH would work --- again the "script
> hash" need not be a hash of a script, it can be any 32-byte commitment.
>
> In all these cases you have to waste 547 satoshi, but that tends to be
> small compared to tx fees currently.
>
> Regards,
> ZmnSCPxj
>

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

<div dir=3D"ltr">Thanks ZmnSCPxj. Yes, I agree there are many ways to embed=
 arbitrary data in the blockchain and it&#39;s not feasible to block all of=
 them. That is why it&#39;s important to, at the same time as limiting the =
OP_RETURN to one per block, also propose and implement a layer 2 solution f=
or timestamping so=C2=A0people have a clear=C2=A0and simple upgrade path. T=
hat is what I will be discussing in one of the BIPs I=C2=A0intend to releas=
e early next week.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Apr 16, 2021 at 11:52 PM ZmnSCPxj &lt;<a href=3D"=
mailto:ZmnSCPxj@protonmail.com">ZmnSCPxj@protonmail.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">Good morning Christo=
pher,<br>
<br>
&gt; &gt;&gt; But more importantly, adding limitations on OP_RETURN transac=
tions is not helpful.=C2=A0 Users who want to embed arbitrary data in their=
 transactions can always do so by encoding their data inside the values of =
legacy multi-signature scriptpubkeys (pubkeys can be generated without know=
ing the private key in order to encode non-key related data).=C2=A0 Not onl=
y can users do this, users have done this in the past.=C2=A0 However, this =
behaviour is problematic because such multi-signature &quot;data&quot; scri=
ptpubkeys are indistinguishable from &quot;real&quot; multisignature script=
pubkeys, and thus must be kept in the UTXO set.=C2=A0 This differs from out=
puts using OP_RETURN which are provably unspendable, and therefore can be s=
afely omitted from the UTXO set.<br>
&gt;<br>
&gt; This sounds like a good justification to remove the legacy multi-signa=
ture capabilities as well.<br>
<br>
The same technique can be used on P2PKH as well --- the &quot;pubkey hash&q=
uot; need not be a hash of a public key, it can be a 20-byte commitment, or=
 even an ASCII message like &quot;ZmnSCPxj is the best&quot; (20 characters=
, I counted).<br>
There is nothing that *can* check if the hash of a public key is indeed the=
 hash of a public key unless you actually reveal the public key.<br>
<br>
If you need a 32-byte commitment, a P2WSH would work --- again the &quot;sc=
ript hash&quot; need not be a hash of a script, it can be any 32-byte commi=
tment.<br>
<br>
In all these cases you have to waste 547 satoshi, but that tends to be smal=
l compared to tx fees currently.<br>
<br>
Regards,<br>
ZmnSCPxj<br>
</blockquote></div>

--000000000000a0cd3605c0231a2c--