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
182
183
184
185
186
187
188
189
190
191
192
|
Return-Path: <therealsangaman@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7F69BCBC
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Dec 2017 23:00:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pf0-f170.google.com (mail-pf0-f170.google.com
[209.85.192.170])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EE9B8F4
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Dec 2017 23:00:03 +0000 (UTC)
Received: by mail-pf0-f170.google.com with SMTP id d23so2214766pfe.9
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 13 Dec 2017 15:00:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=6sgXqGvLrJ9k1/4qyn+3zT8Br6Z+ih4/R5s0ZN/WF3M=;
b=bn/gLzNXJ3HcAFDOwKXL85J1curBj28k00r7jcB8zAvDlyZZu/oy6VYvjcYDR4gqOR
CzmdhFh7ITj8dZ1w5RBUSNyKHn9SjvHyBMyvzuL+/8pFKGZZYOKLfOshA+AHKMtVWSsp
uUcPqWbl8DDrsClO83eZl6xWWR/pw+shJ8JUSGQxqrYblZiVKpYG970J1IRSebNdvl3Z
Kq5AaAzVLpDeCu0JDbmQfzMvPbAIffJ3hVWf6Rp9vRuLwSVQEtZ+N+d42aWTYoqEECTv
vvGax6E0UiQ2x8rLu0aANIUkU7YIVA/uOcMaEXtj5QbzCg50vUH+jpWHqQ9CGPdwva2B
fx2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=6sgXqGvLrJ9k1/4qyn+3zT8Br6Z+ih4/R5s0ZN/WF3M=;
b=C8/wvrcbCJwFq2SsZvx72s6Ml8G/cVXxfkyfAALh8jWexeBzW0bl2VeL2rFgwN4rqX
bHhI+j73uE0hlrHd3bPK7VZuqaC7qpOjbZbpU03GtiiBq2Kam35u1fgT0YffOOBP4Lr6
+glSIViTpUKJYjLtYnQVzQAdky5dBu2KK/4Pav1K/wNOFS6leLDsd1CnbE1cCZtM5PzX
BIuPzUNaVdfikJ5tvrn07zeZbBRcaTdsGRI+4SzQzPAEyk2uQO+VHZO5IZdrc6z1f96T
5txSNDCOHYF1hJ1jqP4MYJdywHbmddkCAaZBw5JGmeYN5jwv3yGc+F0bnb2paLtwJ4ke
JJHQ==
X-Gm-Message-State: AKGB3mJx1r6UTqZYoupsRHEfZii6pEJ09MqyCKxg8FuT+2Kb8TyliLQZ
JdRz0b0tqc/7W/SoDNbxl/AujKJodPsbguBYRfr7Bg==
X-Google-Smtp-Source: ACJfBovuvBaSnhvk/meYaP9eD9TxpTsVuVSumL5/fsNTHS5FXcf+YL5uyOWiB86Q2aE2zK9cLWf9mAV6PMKLT2NJDz4=
X-Received: by 10.159.244.142 with SMTP id y14mr7266628plr.166.1513206003266;
Wed, 13 Dec 2017 15:00:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.164.132 with HTTP; Wed, 13 Dec 2017 15:00:02 -0800 (PST)
Received: by 10.100.164.132 with HTTP; Wed, 13 Dec 2017 15:00:02 -0800 (PST)
In-Reply-To: <CADPKye0Kt87cHbuOqphMOPY3TPmO1awH46k17rEoVZ4kAejkxw@mail.gmail.com>
References: <CADPKye1m2_5PaqedMU9nPsmvpW-3S+LSoqt0LnQLXXk=MjDJew@mail.gmail.com>
<CADPKye39X_QFi_G0we39ZWXAQme=veC1hCfc_fFFwjs15Op=Lw@mail.gmail.com>
<CADPKye1FjsjG9gO7oWngx2LDnVqRQT_ia4Ke-wPfCRbXjnfZCg@mail.gmail.com>
<CADPKye03UUnJ5T94m8OdBNC5k8wnXGVB-xpbqf363gzTtfN_6A@mail.gmail.com>
<CADPKye2H66iZt=uOz765zrVtv_toeAzfoJXaqQvJaUtadqjDwg@mail.gmail.com>
<CADPKye35ZxJDcfM2e+pvw+z6eZEyzj1-6VDcpHP6Z5FtX-=GOQ@mail.gmail.com>
<CADPKye0JD5kfmsGb-AzO6EfPubOGUXtxaEqizLQUQ3QJmCMLJQ@mail.gmail.com>
<CADPKye0_eozpfG35qCmPKX-MX+qYZBLt5peU0_jBOCfVoZfefQ@mail.gmail.com>
<CADPKye0PSwH_bMYa9DzRos9SgL4e2Vid1gEKnNtcUKQB-op5UQ@mail.gmail.com>
<CADPKye04MRZkWtZm1mWnjmSe97v0-iZwAdYH6pSrFjpHfzuQ-w@mail.gmail.com>
<CADPKye2Ozj6rqApztKyoeJvekofdaiP1=jbd6buxFTebEantMA@mail.gmail.com>
<CADPKye3hyOH4Z+y_JgJUfEspSt8jL+ZGaU05v_fX3Wiwr2-N9g@mail.gmail.com>
<CADPKye11prrk663bWAatFCkjktJNgemg-ECdZdP07RECWcE6nQ@mail.gmail.com>
<CADPKye1+z2aUBXc3UECvmoNSGO23hXGzGXekFOTPy-rdHFG_Nw@mail.gmail.com>
<CADPKye0i0LaGgS4Hmp086LLCnPEHNYqJ+VbZ2h2DxycTwY2srQ@mail.gmail.com>
<CADPKye0dj5z=hDbooUOY-vhP0N+L=VzhOGn3Wue4tPgY3vnHwA@mail.gmail.com>
<CADPKye3Z8PDe_5D28hcELDurtpr=5wgzazw3RT=Fc3gUDvhcng@mail.gmail.com>
<CADPKye0-JwfDJruc00XXd55Gm0Ho4c5EKGxqcCqyuFcTY=omYQ@mail.gmail.com>
<CADPKye27FpEYtO31XjX6KcG59HjfZzaGGW0gayO-xZVbdb7jtg@mail.gmail.com>
<CADPKye0Kt87cHbuOqphMOPY3TPmO1awH46k17rEoVZ4kAejkxw@mail.gmail.com>
From: Daniel McNally <therealsangaman@gmail.com>
Date: Wed, 13 Dec 2017 18:00:02 -0500
Message-ID: <CADPKye3r+ZRGFqdF2ihyuJomzQNemUU+4+TprouPhZu_OGu89Q@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="089e082321404bfce3056040ba48"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,LOTS_OF_MONEY,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 14 Dec 2017 03:26:51 +0000
Subject: Re: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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, 13 Dec 2017 23:00:04 -0000
--089e082321404bfce3056040ba48
Content-Type: text/plain; charset="UTF-8"
I think standardization of this term is a great idea. I second all of
Jimmy's points. I think the analogy of dollars & cents to bits and satoshis
is easy to grasp, particularly given that satoshis and cents are the
smallest tangible units of their respective currencies. It's a concept
that's common across cultures and countries as it also applies to pounds
and pence, pesos and centavos, etc...
To David's points, I agree that it's not ideal that bit is a homonym for
other words, but I don't think it's a terrible flaw as context will usually
make the meaning clear. I'm actually not in love with the term "bit," but
rather the idea of a non-SI term for a millionth of a bitcoin. But bit has
already caught on to some extent and I can't think of anything better.
> - Microbitcoins trains users to understand SI prefixes, allowing them to easily
> migrate from one prefix to the next. This will be important when bitcoin
> prices rise to $10M USD[1] and the bits denomination has the same
> problems the millibitcoin denomination has now, but it's also useful in
> the short term when interacting with users who make very large payments
> (bitcoin-scale) or very small payments (nanobitcoin-scale).[2]
I find the SI prefixes to be very user unfriendly. I have plenty of smart
friends and family who constantly confuse mega, giga, micro, nano, and so
on. Rather than try to train users, I think we should choose terms that
will be easy for them to grasp right away. Even for people fluent in SI
terms, I think some of the problems regarding unit bias still exist. 500
microbitcoins sounds diminutive and uttering it is a reminder that it's a
very small fraction of a larger unit. 500 bits sounds like you have 500 of
something, neat!
I consider "bits" to be a term that's quite future proofed. While I won't
dismiss the possibility of $10M or $100M bitcoins in the not-too-distant
future, there would still be plenty of time for a bit to be a useful
day-to-day unit. Even at the $10M point, small ticket items like coffee
could still be priced at 0.30 bits for example, not bad I'd say.
Should bitcoin ever soar past the $100M mark, it might be time for a new
term akin to bits and maybe a hard fork to allow for more decimal places on
chain. A nanobitcoin could not be transacted with today anyhow. These would
all be good problems to have.
Thanks for reading and thanks to Jimmy for taking the initiative with this
BIP.
Daniel
--089e082321404bfce3056040ba48
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div dir=3D"ltr">I think standardization of this term is =
a great idea. I second all of Jimmy's points. I think the analogy of do=
llars & cents to bits and satoshis is easy to grasp, particularly given=
that satoshis and cents are the smallest tangible units of their respectiv=
e currencies. It's a concept that's common across cultures and coun=
tries as it also applies to pounds and pence, pesos and centavos, etc...</d=
iv><div dir=3D"ltr"><br></div><div dir=3D"ltr">To David's points, I agr=
ee that it's not ideal that bit is a homonym for other words, but I don=
't think it's a terrible flaw as context will usually make the mean=
ing clear. I'm actually not in love with the term "bit," but =
rather the idea of a non-SI term for a millionth of a bitcoin. But bit has =
already caught on to some extent and I can't think of anything better.<=
div dir=3D"auto"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><span style=3D"font-size:12.8px">- Microbitcoins trains users to=
understand SI prefixes, allowing them to=C2=A0</span><span style=3D"font-s=
ize:12.8px">easily migrate from one prefix to the next.=C2=A0 This will be =
important=C2=A0</span><span style=3D"font-size:12.8px">when bitcoin prices =
rise to $10M USD[1] and the bits denomination has=C2=A0</span><span style=
=3D"font-size:12.8px">the same problems the millibitcoin denomination has n=
ow, but it's also</span><span style=3D"font-size:12.8px">=C2=A0useful i=
n the short term when interacting with users who make very</span><span styl=
e=3D"font-size:12.8px">=C2=A0large payments (bitcoin-scale) or very small p=
ayments=C2=A0</span><span style=3D"font-size:12.8px">(nanobitcoin-scale).[2=
]</span></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"au=
to">I find the SI prefixes to be very user unfriendly. I have plenty of sma=
rt friends and family who constantly confuse mega, giga, micro, nano, and s=
o on. Rather than try to train users, I think we should choose terms that w=
ill be easy for them to grasp right away. Even for people fluent in SI term=
s, I think some of the problems regarding unit bias still exist. 500 microb=
itcoins sounds diminutive and uttering it is a reminder that it's a ver=
y small fraction of a larger unit. 500 bits sounds like you have 500 of som=
ething, neat!=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I co=
nsider "bits" to be a term that's quite future proofed. While=
I won't dismiss the possibility of $10M or $100M bitcoins in the not-t=
oo-distant future, there would still be plenty of time for a bit to be a us=
eful day-to-day unit. Even at the $10M point, small ticket items like coffe=
e could still be priced at 0.30 bits for example, not bad I'd say.</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">Should bitcoin ever soar pas=
t the $100M mark, it might be time for a new term akin to bits and maybe a =
hard fork to allow for more decimal places on chain. A nanobitcoin could no=
t be transacted with today anyhow. These would all be good problems to have=
.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks for readi=
ng and thanks to Jimmy for taking the initiative with this BIP.=C2=A0</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Daniel</div><div dir=3D"ltr">=
</div></div>
--089e082321404bfce3056040ba48--
|
