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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WO8Vf-0003hp-8e
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 16:29:31 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.42 as permitted sender)
client-ip=74.125.82.42; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f42.google.com;
Received: from mail-wg0-f42.google.com ([74.125.82.42])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO8Ve-0008Bf-Bf
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 16:29:31 +0000
Received: by mail-wg0-f42.google.com with SMTP id y10so1070449wgg.1
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 09:29:24 -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=9ALv34c1uDLkY6oyrEbZHC3/DHUv/EWwHrjgUwyaock=;
b=R5xRjwmFuG/FfTMVfteA3y4X2b8cJORHExN4T7w57ONah9ovIHX+uF/u3uKMC1Wdvu
0hI9UZ1C3kzsRLmJcit5hz7LD8+Xu4uFZ/4q0DHCjaYItNlfRo7gpeWh4xEL/226sJJV
GdBlQ3VQCPAvPHC7GRwz1h3h6U3FQISZEs3VMrXp8GTjoJAFfnYwYZN2oCYqn5Cv3xJe
kSwOHKXJ9GGZAV41q30g7mq8e5ZOWdnqSdrz44wBv43i3LhpWK4oRTCQ4JZ3HAM2h7VM
Od41t91phQWubSEjQuxQcAboisd4lklDjJFOup6lHXP518EJ5y4WdJ1uwd0KyPrq7phV
KfqQ==
X-Gm-Message-State: ALoCoQmY504WHIJ8Zc64FGnmxy6yZPUKtaOQRniVEx9GnZiZQYUM7rfXCWa6sjrbuX4x/pRbkkmp
X-Received: by 10.181.13.112 with SMTP id ex16mr2320837wid.23.1394728163992;
Thu, 13 Mar 2014 09:29:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Thu, 13 Mar 2014 09:29:03 -0700 (PDT)
In-Reply-To: <5321D95C.2070402@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>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 13 Mar 2014 12:29:03 -0400
Message-ID: <CAJHLa0MrLGDVO7LFpUSb+LCxNjKebQQ7UHSwyWPYwzWw5WcbAw@mail.gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
X-Headers-End: 1WO8Ve-0008Bf-Bf
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 16:29:31 -0000
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/
|
