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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WO9mo-0007nY-QT
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:51:18 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.179 as permitted sender)
client-ip=209.85.214.179; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f179.google.com;
Received: from mail-ob0-f179.google.com ([209.85.214.179])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO9mn-0003H7-QO
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:51:18 +0000
Received: by mail-ob0-f179.google.com with SMTP id va2so1409025obc.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 10:51:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.174.170 with SMTP id bt10mr2471797oec.47.1394733072408;
Thu, 13 Mar 2014 10:51:12 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Thu, 13 Mar 2014 10:51:12 -0700 (PDT)
In-Reply-To: <5321EC89.6020300@gmail.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>
<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>
<CANEZrP1v01LtSLF5FGEGprT2XZhryzC8QkvDrbFUv1Px1VgHoQ@mail.gmail.com>
<5321EC89.6020300@gmail.com>
Date: Thu, 13 Mar 2014 18:51:12 +0100
X-Google-Sender-Auth: 5ta-yjVrVhk2gxHpSih9kx3NyjE
Message-ID: <CANEZrP3cw6VV7YMsr1+TvKEws_rHRyS=DMxZiMcaHKBb_QZxmg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6c52c566a3704f480995b
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WO9mn-0003H7-QO
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:51:18 -0000
--047d7bd6c52c566a3704f480995b
Content-Type: text/plain; charset=UTF-8
>
> Well it looks like the consensus is to do it, instead of talking about
> it. I'm going to make sure we get uBTC into the next Armory release.
>
Hmm - be careful with the word "consensus" here. A bunch of people on a
mailing list does not make consensus ;)
If you survey other wallets, you'll find most already switched to mBTC,
that it took some effort to do so (look at the size of the patches for
instance) and that probably, nobody is super-keen to change again so soon.
So uBTC would make you different to most of the other wallets and services
in wide usage.
If Armory wants to do that, that's no problem, maybe it will be a
competitive advantage - just saying, don't quote this thread as indicating
some kind of community consensus.
Wallets and services that are using mBTC (that I know of)
blockchain.info
MultiBit
Bitcoin Wallet (Android)
Hive
Bitcoinity
KnC Wallet (defaults to BTC but can be switched to mBTC in settings, uBTC
not an option)
Mullvad
btcstore.eu
Doing a google search for [bitcoin "mBTC"] and [bitcoin "uBTC"], the former
has a bunch of sites and services with prices in mBTC. The latter only has
faucets, as far as I can tell, which sort of makes sense.
--047d7bd6c52c566a3704f480995b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Well i=
t looks like the consensus is to do it, instead of talking
about it.=C2=A0 I'm going to make sure we get uBTC into the next Ar=
mory
release.</div></blockquote><div><br></div><div>Hmm - be careful with th=
e word "consensus" here. A bunch of people on a mailing list does=
not make consensus ;)</div><div><br></div><div>If you survey other wallets=
, you'll find most already switched to mBTC, that it took some effort t=
o do so (look at the size of the patches for instance) and that probably, n=
obody is super-keen to change again so soon. So uBTC would make you differe=
nt to most of the other wallets and services in wide usage.=C2=A0</div>
<div><br></div><div>If Armory wants to do that, that's no problem, mayb=
e it will be a competitive advantage - just saying, don't quote this th=
read as indicating some kind of community consensus.</div><div><br></div>
<div>Wallets and services that are using mBTC (that I know of)</div><div><b=
r></div><div><a href=3D"http://blockchain.info">blockchain.info</a></div><d=
iv>MultiBit</div><div>Bitcoin Wallet (Android)</div><div>Hive</div><div>Bit=
coinity</div>
<div>KnC Wallet (defaults to BTC but can be switched to mBTC in settings, u=
BTC not an option)</div><div>Mullvad</div><div><a href=3D"http://btcstore.e=
u">btcstore.eu</a></div><div><br></div><div>Doing a google search for [bitc=
oin "mBTC"] and [bitcoin "uBTC"], the former has a bunc=
h of sites and services with prices in mBTC. The latter only has faucets, a=
s far as I can tell, which sort of makes sense.</div>
</div></div></div>
--047d7bd6c52c566a3704f480995b--
|
