summaryrefslogtreecommitdiff
path: root/a6/f3954f3339e8b9825144123a51bc6d865f147c
blob: df4e004b69ff41b84558282902ee552b67cd2104 (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
92
93
94
95
96
97
98
99
100
101
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1WO5BU-00045r-ON
	for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Mar 2014 12:56:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.169 as permitted sender)
	client-ip=74.125.82.169; envelope-from=jgarzik@bitpay.com;
	helo=mail-we0-f169.google.com; 
Received: from mail-we0-f169.google.com ([74.125.82.169])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WO5BT-0008NM-RD
	for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Mar 2014 12:56:28 +0000
Received: by mail-we0-f169.google.com with SMTP id w62so819937wes.14
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 13 Mar 2014 05:56:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=e26zXeGNAWNc5y7B0Cu7rkdnoN1c76PszWGlCY0n3MA=;
	b=NR8G4uM+JF2mX/B0ayGbAw2k5FqSkQVHGfkOmD0sGRvE3kKs7QGtdtLbsL+3MXq6sJ
	Nw8UT0URJ3Z/muFAhxv19sc0jRDucNRTgve7H48koHfI9YeNKQ9eVIEGjhM3tfZumXP3
	DFO/6G+I63SedzVHMKqctLZ2sv5h4VrD1tMyejFsrtlX6wlv8D9Xv737swCqrHX/GM2q
	+KYRWDNDXLc4rDSsBYxvMDlRpoo99ff/UKY7XAUvNk+ltSMhtdM8ESy2ry8DWeI4rTtO
	5omHquDbGeNMYF5ME8/7Ga0VquRXVfQ+J51YFoVMTnVXDQ4r5UYQzY+ExYHVVOX8+WsW
	IE/g==
X-Gm-Message-State: ALoCoQnnRaHpydz6y4F2MqMwRcTeuAw6GZuNWE7cmbFEAtoSlH3fApVO3BDRpsaQmp0oM5l9lCRq
X-Received: by 10.194.118.163 with SMTP id kn3mr1178264wjb.77.1394715381786;
	Thu, 13 Mar 2014 05:56:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Thu, 13 Mar 2014 05:56:01 -0700 (PDT)
In-Reply-To: <EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
	<52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io>
	<CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com>
	<EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 13 Mar 2014 08:56:01 -0400
Message-ID: <CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
To: Wendell <w@grabhive.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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 SPF_PASS               SPF: sender matches SPF record
	-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
X-Headers-End: 1WO5BT-0008NM-RD
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <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: Thu, 13 Mar 2014 12:56:29 -0000

Resurrecting this topic.  Bitcoin Wallet moved to mBTC several weeks
ago, which was disappointing -- it sounded like the consensus was
uBTC, and moving to uBTC later --which will happen-- may result in
additional user confusion, thanks to yet another decimal place
transition.



On Sun, Nov 17, 2013 at 9:28 PM, Wendell <w@grabhive.com> wrote:
> We're with uBTC too. Been waiting for the signal to do this, let's do it right after the fee system is improved.
>
> -wendell
>
> grabhive.com | twitter.com/hivewallet | gpg: 6C0C9411
>
> On Nov 15, 2013, at 6:03 AM, Jeff Garzik wrote:
>
>> Go straight to uBTC. Humans and existing computer systems handle numbers to
>> the left of the decimals just fine (HK Dollars, Yen). The opposite is
>> untrue (QuickBooks really does not like 3+ decimal places).
>



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