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
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WO64m-0008B5-9y
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 13:53:36 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.179 as permitted sender)
client-ip=209.85.214.179; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f179.google.com;
Received: from mail-ob0-f179.google.com ([209.85.214.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO64k-0002BJ-VE
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 13:53:36 +0000
Received: by mail-ob0-f179.google.com with SMTP id va2so1053986obc.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 06:53:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.92.202 with SMTP id co10mr841481oeb.73.1394718809655;
Thu, 13 Mar 2014 06:53:29 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Thu, 13 Mar 2014 06:53:29 -0700 (PDT)
In-Reply-To: <CAJHLa0NEEppHg_Lmi_Oxnz_gPSHZPfQpeg+-8MrvFYDmdM83-g@mail.gmail.com>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io>
<CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com>
<EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com>
<CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
<CA+s+GJBSGPBQWWYR1NYSc2E4Y1BWAn8zf7xsu4wQ1O8cA8OWbw@mail.gmail.com>
<CAJHLa0NEEppHg_Lmi_Oxnz_gPSHZPfQpeg+-8MrvFYDmdM83-g@mail.gmail.com>
Date: Thu, 13 Mar 2014 14:53:29 +0100
X-Google-Sender-Auth: AcOnw-sw33hvojeT1WQur_Lu390
Message-ID: <CANEZrP2O4hDBiCNvO1oV5X7OtnQ4xVDD=RtozQY8ESRHgXQu9w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7b33d67c360fb004f47d47ed
X-Spam-Score: 2.0 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
2.5 US_DOLLARS_3 BODY: Mentions millions of $ ($NN, NNN,
NNN.NN)
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 LOTS_OF_MONEY Huge... sums of money
X-Headers-End: 1WO64k-0002BJ-VE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Wendell <w@grabhive.com>
Subject: Re: [Bitcoin-development] moving the default display to mbtc
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 13 Mar 2014 13:53:36 -0000
--047d7b33d67c360fb004f47d47ed
Content-Type: text/plain; charset=UTF-8
BitPay should use mBTC as well. Unless you can point to any major wallets,
exchanges or price watching sites that use uBTC by default?
I think it is highly optimistic to assume we'll need another 1000x shift
any time soon. By now Bitcoin isn't obscure anymore. Lots of people have
heard about it. Getting from $1 to $1000 was amazing, but it was possible
through huge media coverage. Getting from $1000 to $1,000,000 would take
massive adoption of the kind Bitcoin isn't ready for yet.
On Thu, Mar 13, 2014 at 2:45 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> <vendor hat: on>
>
> Based on this seeming consensus, BitPay was headed towards uBTC
> internally, and hoped to coordinate messaging and rollout with others
> in the community. Ah well, proceed apace, and Bitcoin Wallet will
> catch up, I suppose.
>
> Multiple unit changes negatively impact users, but we are already there :/
>
>
> On Thu, Mar 13, 2014 at 9:34 AM, Wladimir <laanwj@gmail.com> wrote:
> >
> > On Thu, Mar 13, 2014 at 1:56 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> >>
> >> Resurrecting this topic. Bitcoin Wallet moved to mBTC several weeks
> >> ago, which was disappointing -- it sounded like the consensus was
> >> uBTC, and moving to uBTC later --which will happen-- may result in
> >> additional user confusion, thanks to yet another decimal place
> >> transition.
> >
> >
> > I've kind of given up getting any consensus about this, or even getting
> > people to care.
> >
> > Everyone agrees that a decimal shift would be good, but it's the same
> boring
> > shed painting discussion every time on how many decimals. In the end
> nothing
> > happens.
> >
> > I can't really blame Andreas for finally taking action and making the
> change
> > to mBTC. People in the community are familiar with mBTC because some
> > exchanges and price sites used mBTC (at least for a while when >$1000),
> also
> > mBTC seems to be catching on on reddit etc.
> >
> > Moving to muBTC (which in itself would be better because it is the final
> > unit change ever needed without hardfork) would require more coordinated
> > education effort.
> >
> > Wladimir
>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b33d67c360fb004f47d47ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">BitPay should use mBTC as well. Unless you can point to an=
y major wallets, exchanges or price watching sites that use uBTC by default=
?<div><br></div><div>I think it is highly optimistic to assume we'll ne=
ed another 1000x shift any time soon. By now Bitcoin isn't obscure anym=
ore. Lots of people have heard about it. Getting from $1 to $1000 was amazi=
ng, but it was possible through huge media coverage. Getting from $1000 to =
$1,000,000 would take massive adoption of the kind Bitcoin isn't ready =
for yet.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Mar 13, 2014 at 2:45 PM, Jeff Garzik <span dir=3D"ltr"><=
<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com<=
/a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><vendor hat: on><br>
<br>
Based on this seeming consensus, BitPay was headed towards uBTC<br>
internally, and hoped to coordinate messaging and rollout with others<br>
in the community. =C2=A0Ah well, proceed apace, and Bitcoin Wallet will<br>
catch up, I suppose.<br>
<br>
Multiple unit changes negatively impact users, but we are already there :/<=
br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Thu, Mar 13, 2014 at 9:34 AM, Wladimir <<a href=3D"mailto:laanwj@gmai=
l.com">laanwj@gmail.com</a>> wrote:<br>
><br>
> On Thu, Mar 13, 2014 at 1:56 PM, Jeff Garzik <<a href=3D"mailto:jga=
rzik@bitpay.com">jgarzik@bitpay.com</a>> wrote:<br>
>><br>
>> Resurrecting this topic. =C2=A0Bitcoin Wallet moved to mBTC severa=
l weeks<br>
>> ago, which was disappointing -- it sounded like the consensus was<=
br>
>> uBTC, and moving to uBTC later --which will happen-- may result in=
<br>
>> additional user confusion, thanks to yet another decimal place<br>
>> transition.<br>
><br>
><br>
> I've kind of given up getting any consensus about this, or even ge=
tting<br>
> people to care.<br>
><br>
> Everyone agrees that a decimal shift would be good, but it's the s=
ame boring<br>
> shed painting discussion every time on how many decimals. In the end n=
othing<br>
> happens.<br>
><br>
> I can't really blame Andreas for finally taking action and making =
the change<br>
> to mBTC. People in the community are familiar with mBTC because some<b=
r>
> exchanges and price sites used mBTC (at least for a while when >$10=
00), also<br>
> mBTC seems to be catching on on reddit etc.<br>
><br>
> Moving to muBTC (which in itself would be better because it is the fin=
al<br>
> unit change ever needed without hardfork) would require more coordinat=
ed<br>
> education effort.<br>
><br>
> Wladimir<br>
<br>
<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--047d7b33d67c360fb004f47d47ed--
|
