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
|
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 <natanael.l@gmail.com>) id 1WOYTw-0003xk-UX
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 20:13:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.50 as permitted sender)
client-ip=74.125.82.50; envelope-from=natanael.l@gmail.com;
helo=mail-wg0-f50.google.com;
Received: from mail-wg0-f50.google.com ([74.125.82.50])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WOYTu-0006Eh-UL
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 20:13:28 +0000
Received: by mail-wg0-f50.google.com with SMTP id x13so2649122wgg.9
for <bitcoin-development@lists.sourceforge.net>;
Fri, 14 Mar 2014 13:13:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.192.132 with SMTP id hg4mr8414205wjc.28.1394827998909;
Fri, 14 Mar 2014 13:13:18 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Fri, 14 Mar 2014 13:13:18 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Fri, 14 Mar 2014 13:13:18 -0700 (PDT)
In-Reply-To: <532338DD.4050901@riseup.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>
<20140313160850.GW3180@nl.grid.coop>
<CAC1+kJOQfhFaMs34STGOeqbmHdv6bVis7o57BcF3=XYudNw_Lg@mail.gmail.com>
<CANEZrP1CtsXV7m=qpJ1px1cQw9C7AkDYXe7Op8gQqg2+VK3mYA@mail.gmail.com>
<CAC1+kJPF17cWEc9J1cEeyBerQvfrHVEXy7L8VUs+Mz7TpWW4eg@mail.gmail.com>
<532338DD.4050901@riseup.net>
Date: Fri, 14 Mar 2014 21:13:18 +0100
Message-ID: <CAAt2M197HHXxa8iDLc_pS3y5hsyckG-Z_G_dQ_dGxXO4pFJcsw@mail.gmail.com>
From: Natanael <natanael.l@gmail.com>
To: vv01f <vv01f@riseup.net>
Content-Type: multipart/alternative; boundary=047d7b87389665dc5e04f496b314
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
(natanael.l[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: 1WOYTu-0006Eh-UL
Cc: 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: Fri, 14 Mar 2014 20:13:29 -0000
--047d7b87389665dc5e04f496b314
Content-Type: text/plain; charset=UTF-8
Regarding (ISO standards) currency symbols, XBT is already used as
equivalent to 1 Bitcoin in numerous places, and XBC is taken and BT*
belongs to Bhutan (and X** is already the default for non-national currency
common items of trade), so IMHO we should define something like XUB as
microbitcoins so we can have a symbol that doesn't require changing any
existing systems and that can be standardized globally. Then those with
accounting software that needs to deal with something that has two decimals
maximum without losing precision can use that while following well defined
standards. And those who don't like large numbers can still chose to show
mBTC.
- Sent from my phone
Den 14 mar 2014 18:18 skrev "vv01f" <vv01f@riseup.net>:
> I think
> * if we change to mBTC because your state currencys price for bitcoin
> make this a valid option we will change again in future
> * users do not like changes
> * we should keep a good standard
>
> A good standard should be
> * built on standards (e.g. SI)
> * backed by best practice: never force the user to take an option he
> cannot change
> * do not make changes without users permission
> * take care of users at fault when entering 5.967 ot should be pointed
> out before sending that e.g.
> the sw understood 5967.000 000 00 BTC
> instead of 5.967 000 00 BTC
> because the user failed to use the correct delimiter.
>
> For now a good standard is
> * simply bitcoin as BTC with eight decimal places
> or could be
> * uBTC as SI prefix, probably using XBT as a symbol for compatibility
> with other software
> * satoshis (w. SI prefixes if numbers are to big) for regions where
> decimal places in prices are uncommon
>
> So I'd prefer:
> Make the choice transparent to users and set a standard that the user
> alway should be empowered to use all available decimal places.
> And there should be a set of official test-cases for wallet software and
> the desired behavior.
>
>
> ------------------------------------------------------------------------------
> 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
>
--047d7b87389665dc5e04f496b314
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">Regarding (ISO standards) currency symbols, XBT is already u=
sed as equivalent to 1 Bitcoin in numerous places, and XBC is taken and BT*=
belongs to Bhutan (and X** is already the default for non-national currenc=
y common items of trade), so IMHO we should define something like XUB as mi=
crobitcoins so we can have a symbol that doesn't require changing any e=
xisting systems and that can be standardized globally. Then those with acco=
unting software that needs to deal with something that has two decimals max=
imum without losing precision can use that while following well defined sta=
ndards. And those who don't like large numbers can still chose to show =
mBTC. </p>
<p dir=3D"ltr">- Sent from my phone</p>
<div class=3D"gmail_quote">Den 14 mar 2014 18:18 skrev "vv01f" &l=
t;<a href=3D"mailto:vv01f@riseup.net">vv01f@riseup.net</a>>:<br type=3D"=
attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
I think<br>
* if we change to mBTC because your state currencys price for bitcoin<br>
make this a valid option we will change again in future<br>
* users do not like changes<br>
* we should keep a good standard<br>
<br>
A good standard should be<br>
* built on standards (e.g. SI)<br>
* backed by best practice: never force the user to take an option he<br>
cannot change<br>
* do not make changes without users permission<br>
* take care of users at fault when entering 5.967 ot should be pointed<br>
out before sending that e.g.<br>
the sw understood 5967.000 000 00 BTC<br>
instead of 5.967 000 00 BTC<br>
because the user failed to use the correct delimiter.<br>
<br>
For now a good standard is<br>
* simply bitcoin as BTC with eight decimal places<br>
or could be<br>
* uBTC as SI prefix, probably using XBT as a symbol for compatibility<br>
with other software<br>
* satoshis (w. SI prefixes if numbers are to big) for regions where<br>
decimal places in prices are uncommon<br>
<br>
So I'd prefer:<br>
Make the choice transparent to users and set a standard that the user<br>
alway should be empowered to use all available decimal places.<br>
And there should be a set of official test-cases for wallet software and<br=
>
the desired behavior.<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>
</blockquote></div>
--047d7b87389665dc5e04f496b314--
|
