Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WO6gV-0000b9-Br for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 14:32:35 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WO6gS-0003s2-Tq for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 14:32:35 +0000 Received: by mail-we0-f175.google.com with SMTP id q58so914371wes.6 for ; Thu, 13 Mar 2014 07:32:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=oADWxu4g5WTyyNWJCvWuxfDnWUoEk6fltI0wuydyOGY=; b=dKa+bZ/dQkhc8qwUy7QStLZ8CjEcdV4RShUDnnVEsySV9HSlCBazvxct8TUi198v3n fbLjXfRsbTI7CD+YrGsp/OWsMhwWP9px2gVGzCl8QwQ2gO4y1MjZn3H8PgD1kbFPVwD7 5+8It6JdWySZ02+uyWzQjfIGFUjLxkh95rtmXaZ7ZMkLSnQtrU4BAdEPWyFV7OyuXygP 0FNLyBXHK6UYHvHKG7fCiD94iw21ITFgTREIA5YGADeVQWVd5b8/c6NLGtWDDNGouebE wTGvlzqFYI/VhUKpkPLfO7/QDPYb5GGp6EwAjDUiubE4/kVKv2l/Y8jSr0Ldi2xSTEzs RuRw== X-Gm-Message-State: ALoCoQmIxedUDIAWWigBBS3YIDjBFeeX/3Cjxemq5JANlabBR51Po627Av3wH1F4n7EwhXUT5fE8 X-Received: by 10.181.13.112 with SMTP id ex16mr1868609wid.23.1394721146549; Thu, 13 Mar 2014 07:32:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Thu, 13 Mar 2014 07:32:06 -0700 (PDT) In-Reply-To: References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> From: Jeff Garzik Date: Thu, 13 Mar 2014 10:32:06 -0400 Message-ID: To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -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: 1WO6gS-0003s2-Tq Cc: Bitcoin Dev , Wendell 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, 13 Mar 2014 14:32:35 -0000 On Thu, Mar 13, 2014 at 9:53 AM, Mike Hearn wrote: > BitPay should use mBTC as well. Unless you can point to any major wallets, > exchanges or price watching sites that use uBTC by default? > > I think it is highly optimistic to assume we'll need another 1000x shift any > time soon. By now Bitcoin isn't obscure anymore. Lots of people have heard Such hand-wavy, data-free logic is precisely why community coordination is preferred to random apps making random decisions in this manner. mBTC is problematic because you do not need 1000x shift in value to produce annoyances for major accounting packages that are hard-limited to two decimal places. Further, spreadsheets hide information if formatting is configured naively -- that is, if formatting is configured for bitcoin the way it is configured for other currencies. Fundamentally, more than two decimal places tends to violate the Principle Of Least Astonishment with many humans, and as a result, popular software systems have been written with that assumption. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/