Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WbvIh-0001L7-3N for bitcoin-development@lists.sourceforge.net; Sun, 20 Apr 2014 17:13:07 +0000 Received-SPF: fail (sog-mx-3.v43.ch3.sourceforge.com: domain of swipeclock.com does not designate 74.201.97.201 as permitted sender) client-ip=74.201.97.201; envelope-from=mcaldwell@swipeclock.com; helo=mxout.myoutlookonline.com; Received: from mxout.myoutlookonline.com ([74.201.97.201]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WbvIg-000081-EW for bitcoin-development@lists.sourceforge.net; Sun, 20 Apr 2014 17:13:07 +0000 Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 5CA418BE73A for ; Sun, 20 Apr 2014 12:56:53 -0400 (EDT) X-Virus-Scanned: by SpamTitan at mail.lan Received: from HUB012.mail.lan (unknown [10.110.2.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mxout.myoutlookonline.com (Postfix) with ESMTPS id BBB128BE605 for ; Sun, 20 Apr 2014 12:56:52 -0400 (EDT) Received: from MAILR023.mail.lan ([10.110.18.122]) by HUB012.mail.lan ([10.110.17.12]) with mapi; Sun, 20 Apr 2014 12:52:47 -0400 From: Mike Caldwell CC: "bitcoin-development@lists.sourceforge.net" Date: Sun, 20 Apr 2014 12:56:55 -0400 Thread-Topic: [Bitcoin-development] "bits": Unit of account Thread-Index: Ac9cuYm+v5XtX0TfR5CZH4L0n2x+Rg== Message-ID: <87BC4D35-2E10-40A0-B2FE-4C49184C0565@swipeclock.com> References: <3A69904F-0A3D-42E9-9DE7-067874E710BB@bitsofproof.com> <5353ECDF.6090903@gmail.com> <5353F63F.90307@gmail.com> In-Reply-To: <5353F63F.90307@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam-Score: 6.1 (++++++) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 4.0 SPF_CHECK_FAIL SPF reports sender host as NOT permitted to send mails from 0.9 SPF_FAIL SPF: sender does not match SPF record (fail) 1.2 MISSING_HEADERS Missing To: header X-Headers-End: 1WbvIg-000081-EW Subject: Re: [Bitcoin-development] "bits": Unit of account 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: Sun, 20 Apr 2014 17:13:07 -0000 As someone who has put a lot of thought into how to best help typical every= day people understand bitcoin, I strongly favor 1 bit =3D 1e-6 BTC as being= very straightforward to explain to non technical types, and also XBT as on= e "bit". "There are a million bits in a bit coin" is highly intelligible t= o average people.=20 I consider overload/conflict with existing meanings of "bit" as a non-issue= for typical population at large.=20 Mike Sent from my iPhone > On Apr 20, 2014, at 10:31 AM, "Alan Reiner" wrote: >=20 > Whatever we call it. I'm happy to support it as long as it's 1e-6.