From mboxrd@z Thu Jan 1 00:00:00 1970 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 1WgOX2-00089d-W7 for bitcoin-development@lists.sourceforge.net; Sat, 03 May 2014 01:14:25 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53; envelope-from=etotheipi@gmail.com; helo=mail-qa0-f53.google.com; Received: from mail-qa0-f53.google.com ([209.85.216.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WgOX1-0003Kg-3H for bitcoin-development@lists.sourceforge.net; Sat, 03 May 2014 01:14:24 +0000 Received: by mail-qa0-f53.google.com with SMTP id ih12so1041751qab.40 for ; Fri, 02 May 2014 18:14:17 -0700 (PDT) X-Received: by 10.224.57.142 with SMTP id c14mr27213171qah.23.1399079657213; Fri, 02 May 2014 18:14:17 -0700 (PDT) Received: from [192.168.1.11] (pool-98-110-182-20.bstnma.fios.verizon.net. [98.110.182.20]) by mx.google.com with ESMTPSA id t5sm1390051qas.10.2014.05.02.18.14.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 May 2014 18:14:16 -0700 (PDT) Message-ID: <536442D3.50508@gmail.com> Date: Fri, 02 May 2014 21:13:55 -0400 From: Alan Reiner User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> In-Reply-To: Content-Type: multipart/alternative; boundary="------------010508050301010606070603" X-Spam-Score: -0.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 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 0.0 LOTS_OF_MONEY Huge... sums of money X-Headers-End: 1WgOX1-0003Kg-3H 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: Sat, 03 May 2014 01:14:25 -0000 This is a multi-part message in MIME format. --------------010508050301010606070603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I've been a strong supporter of the 1e-6 unit switch since the beginning and ready to do whatever I can with Armory to help ease that transition. I'm happy to prioritize a release that updates the Armory interface to make "bits" the default unit, when the time is right. I think it makes sense to get as many apps and services to upgrade nearly simultaneously. My plan is to have a popup on the first load of the new version that briefly introduces the change, and mentions that they can go back to the old way in the settings, but make them work to do it. For the transient period (6 months?) all input boxes will auto-update nearby labels with the converted-to-BTC value as they type, so that they don't have to do any math in their head. Similarly, all displayed BTC values will show both. But the 1e-6 unit will always be default or first unless they explicitly change it in the interface. On 5/2/2014 8:54 PM, Ben Davenport wrote: > I fully support this (it's what I suggested over a year ago), but what > it comes down to is BitPay, Coinbase, Blockchain and Bitstamp getting > together, agreeing what they're going to use, and doing a little joint > customer education campaign around it. If there's community momentum > around "bits", great. > > My only addition is that I think we should all stop trying to attach > SI prefixes to the currency unit. Name me another world currency that > uses SI prefixes. No one quotes amounts as 63 k$ or 3 M$. The accepted > standard at least in the US is , > i.e. $63k or $3M. That may not be accepted form everywhere, but in any > case it's an informal format, not a formal one. The important point is > there should be one base unit that is not modified with SI prefixes. > And I think the arguments are strong for that unit being = 100 satoshi. > > Ben > > > > > On Fri, May 2, 2014 at 12:17 PM, Jeff Garzik > wrote: > > > > Related: > http://blog.bitpay.com/2014/05/02/bitpay-bitcoin-and-where-to-put-that-decimal-point.html > > -- > Jeff Garzik > Bitcoin core developer and open source evangelist > BitPay, Inc. https://bitpay.com/ > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. Get > unparalleled scalability from the best Selenium testing platform > available. > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. Get > unparalleled scalability from the best Selenium testing platform available. > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --------------010508050301010606070603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I've been a strong supporter of the 1e-6 unit switch since the beginning and ready to do whatever I can with Armory to help ease that transition.  I'm happy to prioritize a release that updates the Armory interface to make "bits" the default unit, when the time is right.  I think it makes sense to get as many apps and services to upgrade nearly simultaneously.

My plan is to have a popup on the first load of the new version that briefly introduces the change, and mentions that they can go back to the old way in the settings, but make them work to do it.  For the transient period (6 months?) all input boxes will auto-update nearby labels with the converted-to-BTC value as they type, so that they don't have to do any math in their head.  Similarly, all displayed BTC values will show both.  But the 1e-6 unit will always be default or first unless they explicitly change it in the interface.




On 5/2/2014 8:54 PM, Ben Davenport wrote:
I fully support this (it's what I suggested over a year ago), but what it comes down to is BitPay, Coinbase, Blockchain and Bitstamp getting together, agreeing what they're going to use, and doing a little joint customer education campaign around it. If there's community momentum around "bits", great.

My only addition is that I think we should all stop trying to attach SI prefixes to the currency unit. Name me another world currency that uses SI prefixes. No one quotes amounts as 63 k$ or 3 M$. The accepted standard at least in the US is <currency-symbol><amount><modifier>, i.e. $63k or $3M. That may not be accepted form everywhere, but in any case it's an informal format, not a formal one. The important point is there should be one base unit that is not modified with SI prefixes. And I think the arguments are strong for that unit being = 100 satoshi.

Ben




On Fri, May 2, 2014 at 12:17 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
<vendor hat: on>

Related: http://blog.bitpay.com/2014/05/02/bitpay-bitcoin-and-where-to-put-that-decimal-point.html

--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development



------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs


_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development

--------------010508050301010606070603--