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
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
|
Return-Path: <casey@rodarmor.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 0D33BC0011
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 23 Feb 2022 07:11:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id DF5FD60F34
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 23 Feb 2022 07:11:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=rodarmor.com
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 AAw-TCty2art
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 23 Feb 2022 07:11:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com
[IPv6:2a00:1450:4864:20::535])
by smtp3.osuosl.org (Postfix) with ESMTPS id 1266460B34
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 23 Feb 2022 07:11:00 +0000 (UTC)
Received: by mail-ed1-x535.google.com with SMTP id c6so39794014edk.12
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 22 Feb 2022 23:11:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rodarmor.com; s=google;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=HFbVk2NeFEIGAObc6Xk3obI/U5m6K0nAbU5jpaU2Hms=;
b=WV435oL3SvN/K9BtRyFYzaufD9VOqtIrC+uMo6VUlf/H6364XFFmBIImq/Uhk3bjtw
NkeUrN4J9JR0K/Dva2IV6F9JNFONFXVKz167sARUE8mmZYlyC5F+ASu9XuCZRCyxvGPc
tWmpsRXa1DTv1hqd4S1wosxsWEEsM2XgPe17+sXMEuq+V0rwYQnXS0ZRli6eoVt18fkL
xvIuDXmDsP5dDvNU9xvYiuq8tHwqDpxr0uqMvPR399nR6NOX1tqWSQh72FAjwYVu6d2Y
1ubKVOOmq9oT45suDm7AFpz+GMVmkSwj+AUuhzqMvRe6TE3Zc1j+OhrMlvmXJFj8ShcR
Nzvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=HFbVk2NeFEIGAObc6Xk3obI/U5m6K0nAbU5jpaU2Hms=;
b=kPHyvY80WH7pMUU5NdrRAuhA3wuqWGUgvdA0WwmKf4kj5g1SKlChZB23bdwKKaDaUh
FkJjHlcu1oNQ8P3VsbNjbjRrB2ID7Gukv9nnxkOL3mXx2sNjkFyhmaKkilXJSeoBt0Kw
hv+Puvm/Mdp82Hl3+/p4+/1Y8Er5FuSN6Fy4fc0TRC5tCrWqPEa3Tsdav5AR1jR5J4T5
b2KkCmgLaSTlTyPNe1XGabXd6AQfPxPWorhsWGzptvcAnua+m13sMKhOqoyzuvgZI36u
Ncce0mNkfImfna87AlWurZp4KxA02l1zJsgIDWUl+4Zozn1CnIzq5D96eX9qUdtDOCMj
Nrxw==
X-Gm-Message-State: AOAM531v4F8DMQe4SaxXAsQqDun+5Q42oJwMI4yg4kTw1z6un+qYnj5J
y3sWJq6pUs9vgZm6iykcaYnd3zTj9U+9ntnKfHTjs7FKPms=
X-Google-Smtp-Source: ABdhPJxYo7UJlMJcmppMcdPd9xb1wUMocDzNnCBdo1dqaDNoEhWGdONjpxDmMuNLg7G5HG7IqrZVz2dQTD0+QTD/Fao=
X-Received: by 2002:a05:6402:2709:b0:413:1871:3bc7 with SMTP id
y9-20020a056402270900b0041318713bc7mr10461838edd.71.1645600259219; Tue, 22
Feb 2022 23:10:59 -0800 (PST)
Received: from 649336022844 named unknown by gmailapi.google.com with
HTTPREST; Wed, 23 Feb 2022 08:10:58 +0100
Mime-Version: 1.0
In-Reply-To: <0642a5e59464779569f9d0aab452ee27@willtech.com.au>
X-Mailer: Superhuman Web (2022-02-22T23:05:56Z)
X-Superhuman-ID: kzz7w5j3.d92c6c8b-3543-4ca5-9ab4-645951fe42f9
X-Superhuman-Draft-ID: draft00310be68983c774
References: <CANLPe+OZ33vcZheOyo2RdrvWzQvj3RzZc6sHTafGwbqEG2G4pA@mail.gmail.com>
<0642a5e59464779569f9d0aab452ee27@willtech.com.au>
From: Casey Rodarmor <casey@rodarmor.com>
Date: Wed, 23 Feb 2022 08:10:58 +0100
Message-ID: <CANLPe+M0Zi1nme88KmwWxX_a0O9=enhK1WVGoEaS=AZ6VYDzCQ@mail.gmail.com>
To: damian@willtech.com.au
Content-Type: multipart/alternative; boundary="000000000000e4b6de05d8aa2a77"
X-Mailman-Approved-At: Wed, 23 Feb 2022 21:47:57 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
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: Wed, 23 Feb 2022 07:11:02 -0000
--000000000000e4b6de05d8aa2a77
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
=E2=80=8BWell done, your bip looks well presented for discussion.
Thank you!
You say to number each satoshi created? For a 50 BTC block reward that is
> 5,000,000,000 ordinal numbers, and when some BTC is transferred to anothe=
r
> UTXO how do you determine which ordinal numbers, say if I create a
> transaction to pay-to another UTXO.
>
It uses a first-in-first out algorithm, so the first ordinal number of the
first input becomes the first ordinal number of the first output.
The system sounds expensive eventually to cope with approximately
> 2,100,000,000,000,000 ordinals.
>
A full index is expensive, but it doesn't have to track 2.1 individual
entries, it only has to track contiguous ordinal ranges, which scales with
the number of outputs=E2=80=93all outputs, not just unspent outputs=E2=80=
=93since an output
might split an ordinal range.
If I understand ordinals 0 to 5,000,000,000 as assigned to the first
> Bitcoin created from mining block-reward. Say if I send some Bitcoin to
> another UTXO then first-in-first-out algorithm splits those up to assign =
1
> to 100,000,000 to the 1 BTC that I sent, and 100,000,001 to 5,000,000,000
> are assigned to the change plus if any fee?-DA.
>
That's correct, assuming that the 1 BTC output is first, and the 4 BTC
output is second. Although it's actually 0 to 99,999,999 that go to the
first output, and 100,000,000 to 499,999,999 that are assigned to the
second output, less any fees.
--000000000000e4b6de05d8aa2a77
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html><head></head><body><div><div><blockquote class=3D""><div class=3D""><=
div class=3D""><div class=3D""><div class=3D"">=E2=80=8BWell done, your bip=
looks well presented for discussion.<br></div></div></div></div></blockquo=
te><div><div><br></div><div>Thank you!<br></div><div><br></div></div><div c=
lass=3D""><div class=3D"sh-quoted-content"><div class=3D""><div class=3D"gm=
ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote" style=3D"null" id=3D"null"><p class=3D"">You say to=20
number each satoshi created? For a 50 BTC block reward that is=20
5,000,000,000 ordinal numbers, and when some BTC is transferred to=20
another UTXO how do you determine which ordinal numbers, say if I create=20
a transaction to pay-to another UTXO.<br></p></div></div></blockquote></div=
></div></div></div><div><div><br></div><div>It uses a first-in-first out al=
gorithm, so the first ordinal number of the first input becomes the first o=
rdinal number of the first output.<br></div><div><br></div></div><div class=
=3D""><div class=3D"sh-quoted-content"><div class=3D""><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote" style=3D"null" id=3D"null"><p class=3D"">The system sounds=
expensive=20
eventually to cope with approximately 2,100,000,000,000,000 ordinals.<br></=
p></div></div></blockquote></div></div></div></div><div><div><br></div><div=
>A full index is expensive, but it doesn't have to track 2.1 individual=
entries, it only has to track contiguous ordinal ranges, which scales with=
the number of outputs=E2=80=93all outputs, not just unspent outputs=E2=80=
=93since an output might split an ordinal range.<br></div><div><br></div></=
div><div class=3D""><div class=3D"sh-quoted-content"><div class=3D""><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote" style=3D"null" id=3D"null"><p class=3D"">If=
=20
I understand ordinals 0 to 5,000,000,000 as assigned to the first=20
Bitcoin created from mining block-reward. Say if I send some Bitcoin to=20
another UTXO then first-in-first-out algorithm splits those up to assign=20
1 to 100,000,000 to the 1 BTC that I sent, and 100,000,001 to=20
5,000,000,000 are assigned to the change plus if any fee?-DA.<br></p></div>=
</div></blockquote></div></div></div></div><div><div><br></div><div>That=
9;s correct, assuming that the 1 BTC output is first, and the 4 BTC output =
is second. Although it's actually 0 to 99,999,999 that go to the first =
output, and 100,000,000 to 499,999,999 that are assigned to the second outp=
ut, less any fees.<br></div></div><div><br></div></div><div></div></div></b=
ody></html>
--000000000000e4b6de05d8aa2a77--
|
