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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <etotheipi@gmail.com>) id 1WO9YI-0006kT-FU
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:36:18 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.169 as permitted sender)
client-ip=209.85.216.169; envelope-from=etotheipi@gmail.com;
helo=mail-qc0-f169.google.com;
Received: from mail-qc0-f169.google.com ([209.85.216.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO9YH-00039Y-Kf
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:36:18 +0000
Received: by mail-qc0-f169.google.com with SMTP id i17so1564753qcy.14
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 10:36:12 -0700 (PDT)
X-Received: by 10.224.167.19 with SMTP id o19mr4018496qay.77.1394732172211;
Thu, 13 Mar 2014 10:36:12 -0700 (PDT)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126])
by mx.google.com with ESMTPSA id u7sm8413587qap.5.2014.03.13.10.36.11
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 13 Mar 2014 10:36:11 -0700 (PDT)
Message-ID: <5321EC89.6020300@gmail.com>
Date: Thu, 13 Mar 2014 13:36:09 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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> <5321E87B.8050908@monetize.io>
<CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com>
In-Reply-To: <CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
boundary="------------070603070207040009050605"
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(etotheipi[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1WO9YH-00039Y-Kf
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 17:36:18 -0000
This is a multi-part message in MIME format.
--------------070603070207040009050605
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 03/13/2014 01:24 PM, Mike Hearn wrote:
>
> Using milli- and micro- notation for currency units is also not very
> well supported. Last time this thread was active, I believe there
> was a
> suggestion to use 1 XBT == 1 uBTC.
>
>
> Unfortunately I think some people already started using XBT to mean
> the same as BTC (another ship that sailed: somehow Bhutan will have to
> live with it). So if some software started to redefine it to mean
> something else, that seems like a recipe for accidentally sending far
> too much or too little money by mistake.
>
There is also the benefit that if someone screws up BTC and uBTC, it's
likely to fail. Most people don't have 1e6 times as much money in their
wallet as they attempted to send in a single transaction. Similarly,
sending one-millionth of what you meant to is likely invalid or below
the dust limit.
Well it looks like the consensus is to do it, instead of talking about
it. I'm going to make sure we get uBTC into the next Armory release.
--------------070603070207040009050605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 03/13/2014 01:24 PM, Mike Hearn
wrote:<br>
</div>
<blockquote
cite="mid:CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Using
milli- and micro- notation for currency units is also not
very<br>
well supported. Last time this thread was active, I
believe there was a<br>
suggestion to use 1 XBT == 1 uBTC.</blockquote>
<div><br>
</div>
<div>Unfortunately I think some people already started using
XBT to mean the same as BTC (another ship that sailed:
somehow Bhutan will have to live with it). So if some
software started to redefine it to mean something else,
that seems like a recipe for accidentally sending far too
much or too little money by mistake.</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
There is also the benefit that if someone screws up BTC and uBTC,
it's likely to fail. Most people don't have 1e6 times as much money
in their wallet as they attempted to send in a single transaction.
Similarly, sending one-millionth of what you meant to is likely
invalid or below the dust limit. <br>
<br>
Well it looks like the consensus is to do it, instead of talking
about it. I'm going to make sure we get uBTC into the next Armory
release. <br>
</body>
</html>
--------------070603070207040009050605--
|
