From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net,
Amir Taaki <zgenjix@yahoo•com>
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Date: Tue, 31 Jan 2012 11:07:00 -0500 [thread overview]
Message-ID: <201201311107.01635.luke@dashjr.org> (raw)
In-Reply-To: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
On Tuesday, January 31, 2012 9:27:26 AM Amir Taaki wrote:
> BIP 20 really has no support among implementations such as Bitcoin-Qt,
> Electrum, MultiBit or Bitcoin-JS.
It does among implementations such as Spesmilo and WalletBuddy, and has for
some time. More importantly, it achieved consensus and Final status before any
objections were made. Final only changes to Superceded. What's the point of a
formal BIP process if that process won't be followed?
> Also BIP 20 is problematic because it is incompatible with about every
> standard on the web. All the HTML, URI and everything uses decimal numbers
> alone. I see no reason for breaking with tradition.
That's not incompatibility, and not true. The standards use hexadecimal
numbers, and I can't even think of a single case off-hand where decimal is
used.
That being said, I'd be fine with a spec that used strtol-compatible satoshis
for amount. This is both simple and forward-compatible.
On Tuesday, January 31, 2012 9:53:57 AM Gary Rowe wrote:
> Regarding the decimal vs satoshi notation I see a few problems with
> satoshi:
>
> * readability - humans reading the URI would expect it to accurately
> reflect what is being displayed (subject to internationalisation issues)
> For example, amount=1.234 is more human readable than amount=123400000
> (ish)
This is true only for BTC users. While that might be a sensible unit today, it
almost certainly won't be in the future. amount=0.00001 is much worse than
amount=1000 or amount=1x3
> * backwards compatibility - existing software already uses the decimal
> notation
Existing software uses Satoshis internally, and it's generally regarded as a
design flaw that it uses BTC numbers in the JSON-RPC protocol.
> * forwards compatibility - Bitcoin needs to move beyond the satoshi to 20
> dps for some reason, this remains OK within the existing schema, but forces
> decimals into the satoshi scheme
This strikes me as more of "let's test the code earlier rather than later"
than forwards compatibility. The problem is that it's pretty much unanimous
that floating-point should never be used, and without that both
representations will be rounding when there are smaller units available.
next prev parent reply other threads:[~2012-01-31 16:07 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
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 [this message]
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=201201311107.01635.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/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