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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <drak@zikula.org>) id 1WOBHa-0007Wf-A0
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 19:27:10 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of zikula.org
designates 74.125.82.181 as permitted sender)
client-ip=74.125.82.181; envelope-from=drak@zikula.org;
helo=mail-we0-f181.google.com;
Received: from mail-we0-f181.google.com ([74.125.82.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WOBHY-0004Fn-SC
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 19:27:10 +0000
Received: by mail-we0-f181.google.com with SMTP id q58so1281152wes.12
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 12:27:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=Vbeb6c7n+5mKx+i8h46DA/y7L0hm/Fe4Gdtz3Hel95Q=;
b=F03Y86fd+NRVkqNbU0Q+y1mg7CgAuuBb8yBIzrO1uGmbVDcW3AYR9yCuPgHrSLQ70I
HVPSz8bEOuW4p4r30J2Vqb/IZwXzkcBUdTGxGMjasIr6kuTi0LnkDxIUyFptJZxd5/0A
wMsJV9oaCIbVgsbSJoPuZQMuQ7c/8T7qkkhA6D0q8pNIY4vy5v1N28NKAWRW+832yDA0
rbxvONBSz3WUnlwcg0lpcxZDz1HgJl7Hje8CmEzAqNvWot+elDLX1048nVVYOR6T6zyQ
wElUXUODH95aL20pKmu7DWOfhmE9YFooKifvCBQYXoFeoLs0tW3jN2FfF/Kx1TJzCS3X
4qdw==
X-Gm-Message-State: ALoCoQk0n4s8y/sEO9ijq/va/+x23dsacmdWrVXc+X+ddtRRx+hO6UKvZQkPdSloxh/qFD3QPbu6
X-Received: by 10.194.84.144 with SMTP id z16mr3169191wjy.23.1394738822445;
Thu, 13 Mar 2014 12:27:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.205.69 with HTTP; Thu, 13 Mar 2014 12:26:42 -0700 (PDT)
In-Reply-To: <CAJHLa0MrLGDVO7LFpUSb+LCxNjKebQQ7UHSwyWPYwzWw5WcbAw@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>
<CANEZrP2O4hDBiCNvO1oV5X7OtnQ4xVDD=RtozQY8ESRHgXQu9w@mail.gmail.com>
<CAJHLa0PB-V+KgEr5uCj+mceESggp8G4MmLGHHpz2UD_R_w-zfQ@mail.gmail.com>
<5321D95C.2070402@gmail.com>
<CAJHLa0MrLGDVO7LFpUSb+LCxNjKebQQ7UHSwyWPYwzWw5WcbAw@mail.gmail.com>
From: Drak <drak@zikula.org>
Date: Thu, 13 Mar 2014 19:26:42 +0000
Message-ID: <CANAnSg2ajK=pb-fBBvonzW2Ed+8f+5TtaE7XcfNh_71Xyk2O=A@mail.gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=089e0102ddae110d5504f481f008
X-Spam-Score: -0.5 (/)
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WOBHY-0004Fn-SC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 19:27:10 -0000
--089e0102ddae110d5504f481f008
Content-Type: text/plain; charset=UTF-8
I agree with you Jeff. The unit switch needs to happen once and once only,
but that is exactly why I said the defaults really need to change in
Bitcoin-Qt since that is still the main reference implementation and it
will influence others.
Bitpay could also take the lead here and make the switch to their defaults.
That would greatly assist the uBTC movement.
Regardless of what anyone says, Bitcoin-Qt is still the main reference
implementation and the best way to encourage a change in the community at
large is for the default units to be changed here. Core devs can surely
garner enough consensus among themselves to accept and merge a PR to that
effect. That will send a message, more than anything else that can be done.
My two satoshi.
Drak
On 13 March 2014 16:29, Jeff Garzik <jgarzik@bitpay.com> wrote:
> On Thu, Mar 13, 2014 at 12:14 PM, Alan Reiner <etotheipi@gmail.com> wrote:
> > Of course, as Mike said, this ship may have already sailed, but if
> > there's any way to revisit this, I'm there. We're just about to do
> > another Armory release and could support this very easily.
>
> mBTC now just means the issue -will- be revisited in the future. Just
> a question of when, not if.
>
> People and software in various nations handle big numbers for small
> values (e.g. Yen) just fine.
> People and software do -not- handle extra decimal places well, field
> experience shows.
>
> <vendor hat: on> To roll out QuickBooks support --without converting
> any numbers, a key financial attribute-- mBTC is simply insufficient
> today, not in the future.
>
> I also argue that it is a security risk, as follows: To support
> accounting packages limited to 2 decimal places, decimal point
> conversion must be performed. This produces a situation where your
> accounting system shows numbers that do not visually match the numbers
> in the bitcoin software. That, in turn, making auditing more
> difficult, particularly for outsiders.
>
> Shipping with mBTC defaults was decidedly unwise, considering that --
> like BTC -- it fails to solve existing, known problems that uBTC can
> solve, and considering the inevitable mBTC->uBTC switch.
>
> --
> 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
>
--089e0102ddae110d5504f481f008
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I agree with you Jeff. The unit switch needs to happen onc=
e and once only, but that is exactly why I said the defaults really need to=
change in Bitcoin-Qt since that is still the main reference implementation=
and it will influence others.<div>
<br></div><div>Bitpay could also take the lead here and make the switch to =
their defaults. That would greatly assist the uBTC movement.</div><div><br>=
</div><div>Regardless of what anyone says, Bitcoin-Qt is still the main ref=
erence implementation and the best way to encourage a change in the communi=
ty at large is for the default units to be changed here. Core devs can sure=
ly garner enough consensus among themselves to accept and merge a PR to tha=
t effect. That will send a message, more than anything else that can be don=
e.</div>
<div><br></div><div>My two satoshi.</div><div><br></div><div>Drak</div></di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 13 March=
2014 16:29, Jeff Garzik <span dir=3D"ltr"><<a href=3D"mailto:jgarzik@bi=
tpay.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"><div class=3D"">On Thu, Mar 13, 2014 at 12:1=
4 PM, Alan Reiner <<a href=3D"mailto:etotheipi@gmail.com">etotheipi@gmai=
l.com</a>> wrote:<br>
> Of course, as Mike said, this ship may have already sailed, but if<br>
> there's any way to revisit this, I'm there. =C2=A0We're ju=
st about to do<br>
> another Armory release and could support this very easily.<br>
<br>
</div>mBTC now just means the issue -will- be revisited in the future. =C2=
=A0Just<br>
a question of when, not if.<br>
<br>
People and software in various nations handle big numbers for small<br>
values (e.g. Yen) just fine.<br>
People and software do -not- handle extra decimal places well, field<br>
experience shows.<br>
<br>
<vendor hat: on> =C2=A0To roll out QuickBooks support --without conve=
rting<br>
any numbers, a key financial attribute-- mBTC is simply insufficient<br>
today, not in the future.<br>
<br>
I also argue that it is a security risk, as follows: =C2=A0To support<br>
accounting packages limited to 2 decimal places, decimal point<br>
conversion must be performed. =C2=A0This produces a situation where your<br=
>
accounting system shows numbers that do not visually match the numbers<br>
in the bitcoin software. =C2=A0That, in turn, making auditing more<br>
difficult, particularly for outsiders.<br>
<br>
Shipping with mBTC defaults was decidedly unwise, considering that --<br>
like BTC -- it fails to solve existing, known problems that uBTC can<br>
solve, and considering the inevitable mBTC->uBTC switch.<br>
<div class=3D"im HOEnZb"><br>
--<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>
</div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------------=
-------------------------------------------------<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>
--089e0102ddae110d5504f481f008--
|
