summaryrefslogtreecommitdiff
path: root/df/7f4b2d2969b855235146323ee70a1e8b6c0552
blob: c1ae3e7218278d9a5cbae7b3a9000ade6e7dd293 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
Return-Path: <melvincarvalho@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 7DCBDC002B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  3 Feb 2023 19:56:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 4537860F1B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  3 Feb 2023 19:56:31 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 4537860F1B
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=KCo6q/zH
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id B7PSEP-79_aj
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  3 Feb 2023 19:56:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 42B5160EC4
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com
 [IPv6:2607:f8b0:4864:20::b2f])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 42B5160EC4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  3 Feb 2023 19:56:30 +0000 (UTC)
Received: by mail-yb1-xb2f.google.com with SMTP id 74so7340220ybl.12
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 03 Feb 2023 11:56:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=86ospYhMB5tZuDVdTwxjgGwkKSV+vXs8qQFM5U39TXw=;
 b=KCo6q/zHgAy8V0rI+h+XUmH/YjOyjgtwJGrJ+rXQGPaPc/7DvreMgfv5orExW9X1q9
 NwFbLsAF7FmHg8AhhazSMGkR3cLFBrHeAr3n1OiBIdwNzQMHvEWkeLKqsocqtiJ567y3
 AHnfgfCs823nNYNrl1tIYp3acQ451dBRvZgukyPI+klzKMQhy6yCWS920EcHI1+NgdUu
 xKtlbd2PDhdu4aRiu3fSNtVNTh09LMF+Fr80/oB1QV+TCHSMN+sJiycmCGq3+W2UWTrd
 HFuYo8emHnZ5uvtFLHxFK/JlBlYmoBoNjsTebMSkBQHdgVKdyCT9e644P1n7DpBsLvxZ
 Di0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=86ospYhMB5tZuDVdTwxjgGwkKSV+vXs8qQFM5U39TXw=;
 b=b32F3mesvMCEaYK7H8wpgU3pZopp1UxD+cOGOcXqmnqR3OTVtr9R2QCVsy6DNl2QKb
 5k+l7JvHFjV0RvG0N4G7v7ns7mhvYgif6gntY3cqph4RQiQ2klrGAqcTbyTfFP08acIb
 JKWZphtem+BsxL/vWicGQh7E0iiMT3wqwxu+7MZAIuQYF+SpqoVXiyO8OdNJIPWoiOKY
 v8r+Gb9dHnGtzqezaXPlvkbwbjDelre8hkklzEa0LNP7sxT0hheyGxHbplws3DgnWSYH
 wXEcqwolILu/H+C2nL0AgB2slSkCsxk8Z08WtDbFW5T9yeD3bo1jpn3bpMSg8zMgQ2C7
 3zeg==
X-Gm-Message-State: AO0yUKXUcOXWy2sVYgxdacJq6kDuT5K9l4Dcsz7HLwAIvUjRosn/m6uc
 7llnWY2MADiakoBq9H6spBFa/YbNECxCmX9KkHk=
X-Google-Smtp-Source: AK7set81+zgVSyzMPxf7dRFJPh55FUXCfMRvysoBusZKLgj/G21P3o1mKAuZoj03Yw4Ph5mTI5ELUo8dSvEqXpPEoiM=
X-Received: by 2002:a25:e7d7:0:b0:80b:5988:2042 with SMTP id
 e206-20020a25e7d7000000b0080b59882042mr1219612ybh.54.1675454189101; Fri, 03
 Feb 2023 11:56:29 -0800 (PST)
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"
X-Mailman-Approved-At: Fri, 03 Feb 2023 20:16:58 +0000
Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2023 19:56:31 -0000

--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--