From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vh5mu-0007g4-FP for bitcoin-development@lists.sourceforge.net; Thu, 14 Nov 2013 22:53:24 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.178 as permitted sender) client-ip=209.85.216.178; envelope-from=etotheipi@gmail.com; helo=mail-qc0-f178.google.com; Received: from mail-qc0-f178.google.com ([209.85.216.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vh5ms-00021y-Lr for bitcoin-development@lists.sourceforge.net; Thu, 14 Nov 2013 22:53:24 +0000 Received: by mail-qc0-f178.google.com with SMTP id i7so1655156qcq.9 for ; Thu, 14 Nov 2013 14:53:17 -0800 (PST) X-Received: by 10.224.25.8 with SMTP id x8mr5951961qab.77.1384469597170; Thu, 14 Nov 2013 14:53:17 -0800 (PST) Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net. [76.111.96.126]) by mx.google.com with ESMTPSA id b9sm152403qas.7.2013.11.14.14.53.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 14 Nov 2013 14:53:16 -0800 (PST) Message-ID: <5285545C.4030607@gmail.com> Date: Thu, 14 Nov 2013 17:53:16 -0500 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> <52854F59.9000500@monetize.io> In-Reply-To: <52854F59.9000500@monetize.io> X-Enigmail-Version: 1.6 Content-Type: multipart/alternative; boundary="------------060602010704010707010308" X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -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 (etotheipi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 X-Headers-End: 1Vh5ms-00021y-Lr Subject: Re: [Bitcoin-development] moving the default display to mbtc X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 22:53:24 -0000 This is a multi-part message in MIME format. --------------060602010704010707010308 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I really like the XBT idea. It makes a lot of sense to match the ISO currency symbol (though the ISO guys will have to adjust the way they've defined the "XBT"). And I do agree that going right to uBTC and skipping mBTC makes sense, too. I'd prefer them not be called "micro bitcoins." I really want to call them "microbes" ... but I'm not sure that has the right flavor for money transfer :) "Please give me 872 microbes". Perhaps we just call them "bits." Or even "micros" or "microbits". As I write this, I realize there's probably 872 threads on the forums about this already... But we would want to promote a consistent term, to avoid further confusion when people use different names for the new unit. It's not guaranteed to be successful, but if we pick a good name, and build it into the interface on the first release pushing the new unit, we have a chance to make the transition even easier. On 11/14/2013 05:31 PM, Mark Friedenbach wrote: > Whoops, this was meant for the list: > > Drawing on analogues from national currencies, it's also possible to > alleviate the confusion by switching currency symbols, e.g. to XBT or > NBC (New Bitcoin). > > 1 XBC == 1 uBTC > > On 11/14/13 2:03 PM, Jeff Garzik wrote: > > Go straight to uBTC. Humans and existing computer systems handle > > numbers to the left of the decimals just fine (HK Dollars, Yen). > > The opposite is untrue (QuickBooks really does not like 3+ decimal > > places). > > > - Jeff > > > On Nov 14, 2013 4:40 PM, "Mark Friedenbach" > > wrote: > > > For this reason I'm in favor of skipping mBTC and moving straight > > to uBTC. Having eight, or even five decimal places is not intuitive > > to the average user. Two decimal places is becoming standard for > > new national currencies, and we wouldn't be too far from human > > scale everyday numbers: 25.00uBTC ~= $0.01 currently. And I don't > > think very many people on this list would consider bitcoin > > overvalued in the long term perspective. > > > Better to go through a confusing renumbering only once. > > > Mark > > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --------------060602010704010707010308 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I really like the XBT idea.  It makes a lot of sense to match the ISO currency symbol (though the ISO guys will have to adjust the way they've defined the "XBT").  And I do agree that going right to uBTC and skipping mBTC makes sense, too.

I'd prefer them not be called "micro bitcoins."  I really want to call them "microbes" ... but I'm not sure that has the right flavor for money transfer :)  "Please give me 872 microbes".  Perhaps we just call them "bits."  Or even "micros" or "microbits".  As I write this, I realize there's probably 872 threads on the forums about this already...

But we would want to promote a consistent term, to avoid further confusion when people use different names for the new unit.  It's not guaranteed to be successful, but if we pick a good name, and build it into the interface on the first release pushing the new unit, we have a chance to make the transition even easier.





On 11/14/2013 05:31 PM, Mark Friedenbach wrote:
Whoops, this was meant for the list:

Drawing on analogues from national currencies, it's also possible to
alleviate the confusion by switching currency symbols, e.g. to XBT or
NBC (New Bitcoin).

1 XBC == 1 uBTC

On 11/14/13 2:03 PM, Jeff Garzik wrote:
> Go straight to uBTC. Humans and existing computer systems handle
> numbers to the left of the decimals just fine (HK Dollars, Yen).
> The opposite is untrue (QuickBooks really does not like 3+ decimal
> places).

> - Jeff

> On Nov 14, 2013 4:40 PM, "Mark Friedenbach" <mark@monetize.io
> <mailto:mark@monetize.io>> wrote:

> For this reason I'm in favor of skipping mBTC and moving straight
> to uBTC. Having eight, or even five decimal places is not intuitive
> to the average user. Two decimal places is becoming standard for
> new national currencies, and we wouldn't be too far from human
> scale everyday numbers: 25.00uBTC ~= $0.01 currently. And I don't
> think very many people on this list would consider bitcoin
> overvalued in the long term perspective.

> Better to go through a confusing renumbering only once.

> Mark
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--------------060602010704010707010308--