Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.169 as permitted sender)
	client-ip=209.85.216.169; envelope-from=etotheipi@gmail.com;
	helo=mail-qc0-f169.google.com; 
Message-ID: <5321EC89.6020300@gmail.com>
Date: Thu, 13 Mar 2014 13:36:09 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.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>	<CANEZrP2O4hDBiCNvO1oV5X7OtnQ4xVDD=RtozQY8ESRHgXQu9w@mail.gmail.com>	<CAJHLa0PB-V+KgEr5uCj+mceESggp8G4MmLGHHpz2UD_R_w-zfQ@mail.gmail.com>	<5321D95C.2070402@gmail.com>	<CAJHLa0MrLGDVO7LFpUSb+LCxNjKebQQ7UHSwyWPYwzWw5WcbAw@mail.gmail.com>	<5321E87B.8050908@monetize.io>
	<CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com>
In-Reply-To: <CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------070603070207040009050605"
Subject: Re: [Bitcoin-development] moving the default display to mbtc
Precedence: list

This is a multi-part message in MIME format.
--------------070603070207040009050605
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


On 03/13/2014 01:24 PM, Mike Hearn wrote:
>
>     Using milli- and micro- notation for currency units is also not very
>     well supported. Last time this thread was active, I believe there
>     was a
>     suggestion to use 1 XBT == 1 uBTC.
>
>
> Unfortunately I think some people already started using XBT to mean
> the same as BTC (another ship that sailed: somehow Bhutan will have to
> live with it). So if some software started to redefine it to mean
> something else, that seems like a recipe for accidentally sending far
> too much or too little money by mistake.
>

There is also the benefit that if someone screws up BTC and uBTC, it's
likely to fail.  Most people don't have 1e6 times as much money in their
wallet as they attempted to send in a single transaction.  Similarly,
sending one-millionth of what you meant to is likely invalid or below
the dust limit. 

Well it looks like the consensus is to do it, instead of talking about
it.  I'm going to make sure we get uBTC into the next Armory release. 

--------------070603070207040009050605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 03/13/2014 01:24 PM, Mike Hearn
      wrote:<br>
    </div>
    <blockquote
cite="mid:CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Using
              milli- and micro- notation for currency units is also not
              very<br>
              well supported. Last time this thread was active, I
              believe there was a<br>
              suggestion to use 1 XBT == 1 uBTC.</blockquote>
            <div><br>
            </div>
            <div>Unfortunately I think some people already started using
              XBT to mean the same as BTC (another ship that sailed:
              somehow Bhutan will have to live with it). So if some
              software started to redefine it to mean something else,
              that seems like a recipe for accidentally sending far too
              much or too little money by mistake.</div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    There is also the benefit that if someone screws up BTC and uBTC,
    it's likely to fail.&nbsp; Most people don't have 1e6 times as much money
    in their wallet as they attempted to send in a single transaction.&nbsp;
    Similarly, sending one-millionth of what you meant to is likely
    invalid or below the dust limit.&nbsp; <br>
    <br>
    Well it looks like the consensus is to do it, instead of talking
    about it.&nbsp; I'm going to make sure we get uBTC into the next Armory
    release.&nbsp; <br>
  </body>
</html>

--------------070603070207040009050605--