Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VhFV1-0003Md-43 for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 09:15:35 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of leitl.org designates 164.177.174.8 as permitted sender) client-ip=164.177.174.8; envelope-from=eugen@leitl.org; helo=leitl.org; Received: from v8.ativel.com ([164.177.174.8] helo=leitl.org) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VhFUz-0001Bl-2K for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 09:15:35 +0000 Received: by leitl.org (Postfix, from userid 1000) id 51033540F2A; Fri, 15 Nov 2013 09:55:42 +0100 (CET) Date: Fri, 15 Nov 2013 09:55:42 +0100 From: Eugen Leitl To: bitcoin-development@lists.sourceforge.net Message-ID: <20131115085542.GJ5661@leitl.org> References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> <528547FD.2070300@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -1.5 (-) 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_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1VhFUz-0001Bl-2K 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: Fri, 15 Nov 2013 09:15:35 -0000 On Thu, Nov 14, 2013 at 04:07:58PM -0600, Allen Piscitello wrote: > Obviously the answer is to just display all fees and trading rates as BTC > or MBTC (.0000005 MBTC fee? how cheap!). On a more serious note, the > transition should definitely be thought out well as it could be very > damaging to have this confusion, but I would prefer to do it only once > rather than twice. Why not just using SI prefixes, as God intended. MBTC mega 10^6 kBTC kilo 10^3 - - 10^0 mBTC milli 10^-3 uBTC micro 10^-6 nBTC nano 10^-9 (at all possible?)