From: Gregory Maxwell <gmaxwell@gmail•com>
To: slush <slush@centrum•cz>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Date: Tue, 31 Jan 2012 09:59:26 -0500 [thread overview]
Message-ID: <CAAS2fgTx3LVT=JkHQpFTiuPnR0utKUZ4at99Jfk96xJR7CBmAw@mail.gmail.com> (raw)
In-Reply-To: <CAJna-Hhx_JquBCOWA096YDe1HzJhGBrcZvvaDg2_2x9XJM+pNA@mail.gmail.com>
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 of
> decimal bitcoin would be better choice? We all know about pains with proper
> handling decimal numbers across of all implementations - and it's not only
> about json-rpc.
Mixed bag of worms there, even ignoring what people have already
implemented— if you make it use satoshis people who are working with
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.
next prev parent reply other threads:[~2012-01-31 14:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 14:27 Amir Taaki
2012-01-31 14:33 ` slush
2012-01-31 14:52 ` Amir Taaki
[not found] ` <CAKm8k+1cHagzj3T27S=h0PueH8EgcCkEajZGgAw7HcQ=N-46ow@mail.gmail.com>
2012-01-31 14:53 ` Gary Rowe
2012-01-31 15:02 ` Gregory Maxwell
2012-01-31 15:04 ` Gary Rowe
2012-01-31 14:59 ` Gregory Maxwell [this message]
2012-01-31 16:04 ` Matt Corallo
2012-01-31 18:22 ` Matt Corallo
2012-01-31 19:02 ` Wladimir
2012-01-31 21:42 ` Matt Corallo
2012-01-31 22:14 ` Andreas Schildbach
2012-01-31 22:37 ` Gary Rowe
2012-01-31 22:47 ` Matt Corallo
2012-02-04 14:03 ` thomasV1
2012-02-04 16:03 ` Gary Rowe
2012-02-04 17:15 ` Matt Corallo
2012-01-31 16:07 ` Luke-Jr
2012-02-02 17:07 Gary Rowe
2012-02-02 17:39 ` Matt Corallo
2012-02-02 17:46 ` Gary Rowe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAS2fgTx3LVT=JkHQpFTiuPnR0utKUZ4at99Jfk96xJR7CBmAw@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox