summaryrefslogtreecommitdiff
path: root/5c/5988692e7dc1b4a5af62bcbcbc6f02972e54af
blob: 5900c24d81936550fa534d00c155cb2367cd50aa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
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 <mcaldwell@swipeclock.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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 <bitcoin-development@lists.sourceforge.net>;
	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 <mcaldwell@swipeclock.com>
CC: "bitcoin-development@lists.sourceforge.net"
	<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: <CAJKMfeQO6pyi5b-83FyMSHcq0Sa1QkP+RouQVBdCYPtXXboY8A@mail.gmail.com>
	<3A69904F-0A3D-42E9-9DE7-067874E710BB@bitsofproof.com>
	<CAPg+sBha=cUHOWcU29yLrC4WTy5EghOGpVGAcQ8S0fuMvpLeRw@mail.gmail.com>
	<DFFB1B2C-F10B-4CF7-9D01-F6A27F9FA229@bitsofproof.com>
	<5353ECDF.6090903@gmail.com>
	<CALykB6n0PFwRU1gvP+KXdN2ONkOfWZPwhmP-A1fmrAJ_M3iB6A@mail.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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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" <etotheipi@gmail.com> wrote:
>=20
> Whatever we call it. I'm happy to support it as long as it's 1e-6.