MIME-Version: 1.0
References: <CABHetKwan91zqm=0y=_84vG7ffveWTPYONZP_hLQx5o40iAnuQ@mail.gmail.com>
In-Reply-To: <CABHetKwan91zqm=0y=_84vG7ffveWTPYONZP_hLQx5o40iAnuQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Fri, 3 Feb 2023 20:56:16 +0100
Message-ID: <CAKaEYhJ_8tph3v9n139Ta+3sBaL-TmeOBNr-cCtti9dbdYuhCQ@mail.gmail.com>
To: Robert Dickinson <robert.lee.dickinson@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000c7688d05f3d1137a"
Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits
Precedence: list

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

p=C3=A1 27. 1. 2023 v 13:47 odes=C3=ADlatel Robert Dickinson via bitcoin-de=
v <
bitcoin-dev@lists.linuxfoundation.org> napsal:

> I'm curious what opinions exist and what actions might be taken by core
> developers regarding storing unlimited amounts of NFT (or other?) content
> as witness data (https://docs.ordinals.com/inscriptions.html). The
> ordinal scheme is elegant and genius IMHO, but when I think about the
> future disk use of all unpruned nodes, I question whether unlimited stora=
ge
> is wise to allow for such use cases. Wouldn't it be better to find a way =
to
> impose a size limit similar to OP_RETURN for such inscriptions?
>
> I think it would be useful to link a sat to a deed or other legal
> construct for proof of ownership in the real world, so that real property
> can be transferred on the blockchain using ordinals, but storing the
> property itself on the blockchain seems nonsensical to me.
>

Low tech solution: miners charge a premium for storing images in the block
chain.  Say 2x, 5x, 10x.

This encourages bitcoin to be used as a financial network, while increasing
the security budget.

>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">p=C3=A1 27. 1. 2023 v=C2=A013:47 odes=
=C3=ADlatel Robert Dickinson via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-=
dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt=
; napsal:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr">I&#39;m curious what opinions exist and what actions might be ta=
ken by core developers regarding storing unlimited amounts of NFT (or other=
?) content as witness data (<a href=3D"https://docs.ordinals.com/inscriptio=
ns.html" target=3D"_blank">https://docs.ordinals.com/inscriptions.html</a>)=
. The ordinal scheme is elegant and genius IMHO, but when I think about the=
 future disk use of all unpruned nodes, I question whether unlimited storag=
e is wise to allow for such use cases. Wouldn&#39;t it be better to find a =
way to impose a size limit similar to OP_RETURN for such inscriptions?<br><=
br>I think it would be useful to link a sat to a deed or other legal constr=
uct for proof of ownership in the real world, so that real property can be =
transferred on the blockchain using ordinals, but storing the property itse=
lf on the blockchain seems nonsensical to me.<br></div></blockquote><div><b=
r></div><div>Low tech solution: miners charge a premium for storing images =
in the block chain.=C2=A0 Say 2x, 5x, 10x.</div><div><br></div><div>This en=
courages bitcoin to be used as a financial network, while increasing the se=
curity budget.</div><div class=3D"gmail_quote">=C2=A0<blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
_______________________________________________<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></div>

--000000000000c7688d05f3d1137a--