summaryrefslogtreecommitdiff
path: root/73/ea8b50e2ff6c1425d6c79a2824728e4cd5a057
blob: 3f245fa833b9be2378a176f83ebbd99285ae7024 (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
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 <jgarzik@bitpay.com>) id 1WO9Kl-0003ut-Km
	for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Mar 2014 17:22:19 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=jgarzik@bitpay.com;
	helo=mail-wi0-f174.google.com; 
Received: from mail-wi0-f174.google.com ([209.85.212.174])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WO9Kk-0001mH-R4
	for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Mar 2014 17:22:19 +0000
Received: by mail-wi0-f174.google.com with SMTP id d1so4244529wiv.1
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 13 Mar 2014 10:22:12 -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=opjFNpHO4UuYy88h7G6kGXTn1ErknucXWAEBwy2fiIw=;
	b=HhQuvL1bI/tIDFWeV5U90Cyz6nyxLOPodA6vlQS0ffOj4SoWw+sCoyXX8MiR1cgDSO
	cIX1JkK8vN8BbkinneOQ0mF66WDN23VJVkPQLi2LZF1nxKZOiG7WNdvwbSUw8MT6YCql
	gArAF4vDk+1IdG69iDyYU/UqgsdbiAD757V599NYxxhmeSrDC2aOND+O/JHeniKwhNqy
	hHhGmbFpe5vyB98H/+p1hxXhlaKcWBE8RMWV989qT7kZbMcBLxMdi9ri/Kk/B3yooafY
	t1l0BKtibuzNwjJkNM7f3/PEp1kU5xiofCbADqm63PxT60KoaAN7lx5Bh0cldV661GYA
	uwAQ==
X-Gm-Message-State: ALoCoQlXybrUeWE0QIF7kfQpaaapG2KyRlxl7TVWILCAQsXPrtSLoRxo6hI4fm8poFUoXGn9OgLa
X-Received: by 10.194.9.99 with SMTP id y3mr2747125wja.60.1394731332588; Thu,
	13 Mar 2014 10:22:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Thu, 13 Mar 2014 10:21:52 -0700 (PDT)
In-Reply-To: <5321E87B.8050908@monetize.io>
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>
	<CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
	<CA+s+GJBSGPBQWWYR1NYSc2E4Y1BWAn8zf7xsu4wQ1O8cA8OWbw@mail.gmail.com>
	<CAJHLa0NEEppHg_Lmi_Oxnz_gPSHZPfQpeg+-8MrvFYDmdM83-g@mail.gmail.com>
	<CANEZrP2O4hDBiCNvO1oV5X7OtnQ4xVDD=RtozQY8ESRHgXQu9w@mail.gmail.com>
	<CAJHLa0PB-V+KgEr5uCj+mceESggp8G4MmLGHHpz2UD_R_w-zfQ@mail.gmail.com>
	<5321D95C.2070402@gmail.com>
	<CAJHLa0MrLGDVO7LFpUSb+LCxNjKebQQ7UHSwyWPYwzWw5WcbAw@mail.gmail.com>
	<5321E87B.8050908@monetize.io>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 13 Mar 2014 13:21:52 -0400
Message-ID: <CAJHLa0NHTR3ZmTxQFeORZ_EqHcxfK+eBVsRf_A-tKA+PsjXJjw@mail.gmail.com>
To: Mark Friedenbach <mark@monetize.io>
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: 1WO9Kk-0001mH-R4
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 17:22:19 -0000

On Thu, Mar 13, 2014 at 1:18 PM, Mark Friedenbach <mark@monetize.io> wrote:
> Using milli- and micro- notation for currency units is also not very
> well supported. Last time this thread was active, I believe there was a
> suggestion to use 1 XBT == 1 uBTC. This would bring us completely within
> the realm of supported behavior in accounting applications.

Yes.  That was in Tamas's recursive link, and also brought up on
github by jcorgan.  +1

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