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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1RsFBJ-0004LU-7V
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:59:37 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=gmaxwell@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RsFBD-0002CC-G4
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:59:37 +0000
Received: by vbbff1 with SMTP id ff1so85574vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 31 Jan 2012 06:59:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.91.200 with SMTP id cg8mr8109203vdb.65.1328021966115; Tue,
31 Jan 2012 06:59:26 -0800 (PST)
Received: by 10.220.151.200 with HTTP; Tue, 31 Jan 2012 06:59:26 -0800 (PST)
In-Reply-To: <CAJna-Hhx_JquBCOWA096YDe1HzJhGBrcZvvaDg2_2x9XJM+pNA@mail.gmail.com>
References: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
<CAJna-Hhx_JquBCOWA096YDe1HzJhGBrcZvvaDg2_2x9XJM+pNA@mail.gmail.com>
Date: Tue, 31 Jan 2012 09:59:26 -0500
Message-ID: <CAAS2fgTx3LVT=JkHQpFTiuPnR0utKUZ4at99Jfk96xJR7CBmAw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: slush <slush@centrum.cz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.2 (-)
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
(gmaxwell[at]gmail.com)
-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
0.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RsFBD-0002CC-G4
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
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: Tue, 31 Jan 2012 14:59:37 -0000
On Tue, Jan 31, 2012 at 9:33 AM, slush <slush@centrum.cz> wrote:
> excuse me if it was already discussed, but maybe using satoshis instead o=
f
> decimal bitcoin would be better choice? We all know about pains with prop=
er
> handling decimal numbers across of all implementations - and it's not onl=
y
> about json-rpc.
Mixed bag of worms there, even ignoring what people have already
implemented=E2=80=94 if you make it use satoshis people who are working wit=
h
things at COIN scale are inevitably going to end up multiplying
numbers stored as radix-2 floating point to get satoshis and then are
going to be confused when it comes out "wrong".
Using decimal numbers at least lets them treat the values as strings
and avoid arithmetic that will end up confusing them.
|
