public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development]  BIP 20 Rejected, process for BIP 21N
Date: Tue, 31 Jan 2012 14:53:57 +0000	[thread overview]
Message-ID: <CAKm8k+1Ha=e8BpUDsRb_UWzmBeMpbRsYu37dwkcGXSG_n7Cd2Q@mail.gmail.com> (raw)
In-Reply-To: <CAKm8k+1cHagzj3T27S=h0PueH8EgcCkEajZGgAw7HcQ=N-46ow@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4360 bytes --]

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)
* backwards compatibility - existing software already uses the decimal
notation
* 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
* simplicity - dual decimal/satoshi variants should be discouraged under
the "single representation" approach

It's relatively straightforward to convert a string encoded decimal into an
internal integer for currency calculations just by applying a multiplying
factor. One never uses doubles or floats for money.


On 31 January 2012 14:33, slush <slush@centrum.cz> wrote:

> Hi Amir,
>
> >  All the HTML, URI and everything uses decimal numbers alone. I see no
> reason for breaking with tradition.
>
> 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.
>
> Otherwise I agree, BIP 21 is better than BIP 20 because it's easier to
> implement all points of the standard.
>
> Best,
> slush
>
> On Tue, Jan 31, 2012 at 3:27 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
>
>> BIP 20 really has no support among implementations such as Bitcoin-Qt,
>> Electrum, MultiBit or Bitcoin-JS. As the most active and visible user
>> facing GUI projects (all with some form of URI Scheme), their opinion
>> carries the most weight. To a lesser degree Bitcoin-Qt has the large
>> majority of users too (although that's a line of reasoning I'd discourage).
>>
>> Normally we should probably Reject BIP 21 and re-submit a new standard
>> (for history's sake), but as a) BIP 21 is largely a copy paste of BIP 20
>> sans some sections b) it is still a draft, probably the best thing here is
>> if you all agree on something to run it by BlueMatt and then we'll make it
>> the new BIP 21.
>>
>> I can see a consensus forming on most parts. Just the send private key is
>> contentious, and there's the topic of adding a time to expire field for
>> merchants (this is a very good idea IMO).
>>
>> 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. Note that everytime I
>> have to write Color or Vectorize (as a British speaker) in my code, I die a
>> little inside. But it's convention and American English = International
>> English. Also it would be cool if all code used a *real* international
>> language (like Esperanto) but the world ain't perfect! We live in a
>> decimal-counting English-speaking Windows-using God-worshipping world!
>>
>> (no offense to decimal-counting English-speaking Windows-using
>> God-worshipping world- I do half those things too :)
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 5764 bytes --]

  parent reply	other threads:[~2012-01-31 14:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 14:27 [Bitcoin-development] BIP 20 Rejected, process for BIP 21N 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 [this message]
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
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='CAKm8k+1Ha=e8BpUDsRb_UWzmBeMpbRsYu37dwkcGXSG_n7Cd2Q@mail.gmail.com' \
    --to=g.rowe@froot.co.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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