Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WOVgl-0000iX-6o for bitcoin-development@lists.sourceforge.net; Fri, 14 Mar 2014 17:14:31 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of riseup.net designates 198.252.153.129 as permitted sender) client-ip=198.252.153.129; envelope-from=vv01f@riseup.net; helo=mx1.riseup.net; Received: from mx1.riseup.net ([198.252.153.129]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WOVgj-0003km-36 for bitcoin-development@lists.sourceforge.net; Fri, 14 Mar 2014 17:14:31 +0000 Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 0545D5141E for ; Fri, 14 Mar 2014 10:14:22 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: vv01f@fulvetta.riseup.net) with ESMTPSA id 45E0F165 Message-ID: <532338DD.4050901@riseup.net> Date: Fri, 14 Mar 2014 18:14:05 +0100 From: vv01f User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> <20140313160850.GW3180@nl.grid.coop> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.1 at mx1 X-Virus-Status: Clean X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [198.252.153.129 listed in list.dnswl.org] -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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Headers-End: 1WOVgj-0003km-36 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, 14 Mar 2014 17:14:31 -0000 I think * if we change to mBTC because your state currencys price for bitcoin make this a valid option we will change again in future * users do not like changes * we should keep a good standard A good standard should be * built on standards (e.g. SI) * backed by best practice: never force the user to take an option he cannot change * do not make changes without users permission * take care of users at fault when entering 5.967 ot should be pointed out before sending that e.g. the sw understood 5967.000 000 00 BTC instead of 5.967 000 00 BTC because the user failed to use the correct delimiter. For now a good standard is * simply bitcoin as BTC with eight decimal places or could be * uBTC as SI prefix, probably using XBT as a symbol for compatibility with other software * satoshis (w. SI prefixes if numbers are to big) for regions where decimal places in prices are uncommon So I'd prefer: Make the choice transparent to users and set a standard that the user alway should be empowered to use all available decimal places. And there should be a set of official test-cases for wallet software and the desired behavior.