MIME-Version: 1.0
References: <CABHetKwan91zqm=0y=_84vG7ffveWTPYONZP_hLQx5o40iAnuQ@mail.gmail.com>
 <CAKaEYhJ_8tph3v9n139Ta+3sBaL-TmeOBNr-cCtti9dbdYuhCQ@mail.gmail.com>
 <CABE6yHvRihAbP3NYOiAiXmRFQu-28Rnz6QBn17bHxBwM-V4wdw@mail.gmail.com>
In-Reply-To: <CABE6yHvRihAbP3NYOiAiXmRFQu-28Rnz6QBn17bHxBwM-V4wdw@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Mon, 6 Feb 2023 11:39:14 -0500
Message-ID: <CAJowKgJ8wm8GgPYXMdfYyzyPZksedCR=cQ7v_ADum=aOzR5r3Q@mail.gmail.com>
To: Kostas Karasavvas <kkarasavvas@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000092bd0c05f40aac06"
Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits
Precedence: list

--00000000000092bd0c05f40aac06
Content-Type: text/plain; charset="UTF-8"

its trivial to store images in such a way that they look like legit
transactions.

this was done, in the past, using large numbers of multisig output
addresses that encode the images.

given the goals of the project, introducing this sort of censorship into
bitcoin seems fundamentally undesirable

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

<div dir=3D"ltr">its trivial to store images in such a way that they look l=
ike legit transactions. =C2=A0 <br><br>this was done, in the past, using la=
rge numbers of multisig output addresses that encode the images.=C2=A0<div>=
<br></div><div>given the goals of the project, introducing this sort of cen=
sorship into bitcoin seems fundamentally undesirable<br></div><div><div>=C2=
=A0</div></div></div>

--00000000000092bd0c05f40aac06--