Date: Sat, 17 Apr 2021 11:50:08 -0400
From: Peter Todd <pete@petertodd.org>
To: Christopher Gilliard <christopher.gilliard@gmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20210417155008.GA3373@petertodd.org>
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>
 <CAK=nyAxJ_XYDhTE6pNHqWOQ-cLgqc_f-fbQ+EHTkxyiYOhOPUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V"
Content-Disposition: inline
In-Reply-To: <CAK=nyAxJ_XYDhTE6pNHqWOQ-cLgqc_f-fbQ+EHTkxyiYOhOPUQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
Precedence: list


--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 17, 2021 at 03:57:55AM +0000, Christopher Gilliard via bitcoin-=
dev wrote:
> 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.

Note that an aggregated timestamping service already exists:

https://petertodd.org/2016/opentimestamps-announcement

But timestamping is useless for most things people want to do, as it can't
commit to a unique history. It merely proves something existed in the past.=
 For
uniqueness, you need something like:

https://petertodd.org/2017/scalable-single-use-seal-asset-transfer


Anyway, at current fees being what they are there's no compelling reason to=
 try
to prevent people from embedding data in the Bitcoin block chain with conse=
nsus
changes. Economics is preventing that just fine.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--xHFwDpU9dbj6ez1V
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEFcyURjhyM68BBPYTJIFAPaXwkfsFAmB7A6sACgkQJIFAPaXw
kftgzAf6Ar/Gh8KX4szq3/Pz2QM6N4SrFVOT9ZwPsZhq28a6/HCBvhpP6kfnFrlT
xXz0LJ9GEiVkshDcqIM1ZrLqQ57zCAjkUxvvRuy/3OenHT4BLf6YGkYLhOB2+807
bv2wJJ+8x6jinjP450I99vjo2yss7cVCoYyvI2YUA4IQL7chjFEZDr5glqlV2teo
aA8XlRZ6JSbbRQ4hYtNiFZ73gzleP452nLjwg/SCIPCE6bjPGYDuH1RTj1TARaRK
lTMFfI2tBm27Uh+kYwauFdJtvuMvJWbymDffcsehyDzpNr3O3+ybLEeaMR+ERn2X
r03SSn4AwNLLxtpxJ6YR07CSu4Q02w==
=ugST
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--