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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1V9tsu-000186-1N
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 09:30:24 +0000
X-ACL-Warn:
Received: from mail-oa0-f48.google.com ([209.85.219.48])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V9tsr-0003ba-EI
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 09:30:24 +0000
Received: by mail-oa0-f48.google.com with SMTP id o17so543413oag.7
for <bitcoin-development@lists.sourceforge.net>;
Thu, 15 Aug 2013 02:30:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc:content-type;
bh=xr5miPNqJnvyDq10TE1Akg//byLOAPFHeX2WRRpTkbc=;
b=TWWyu5wdlXW5svPnX2LcN+I6WX+ZrO5yjFjNJwASq/QEZYdO1A+M9HGvQgSJUQnxSB
tq1BfA3eAjXi4rI9s6nqC8G1DGXhHQJm1OUIZ8CXhlHAMyfnpTJoS3gJB5YyYTynKOIB
FBn2rSQh+HBDM2HV8iCHvgFZLdfDp+9y72BN+9AOSE2SFprrfwtjMkx+9zKdOkx7EGqf
XCTzO7CzQi25gq/3OtCHFxLsxPgwYkNr5ca67j5Os4vRLdax+IkmuiS8dU0FyZTAmjq7
j+GWc6g6PvyybqjzAgnSl+mvSYVp7ajHSwLF6U+POHNoHlY+ijZaqaPHEylelOM3/dj7
T0WQ==
X-Gm-Message-State: ALoCoQlrfMj6lIJ2LRYv0d4T7VhsZ/ZTYNHAhy78jFDg7BwXVOb3L9rFDIDTcpYHhhgp0CkCp1YL
X-Received: by 10.182.65.1 with SMTP id t1mr25151462obs.5.1376554969357; Thu,
15 Aug 2013 01:22:49 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.60.162.7 with HTTP; Thu, 15 Aug 2013 01:22:19 -0700 (PDT)
In-Reply-To: <CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
References: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
<CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Thu, 15 Aug 2013 10:22:19 +0200
X-Google-Sender-Auth: ZdllA7jVmCRp4RX_CwuhWKDhNks
Message-ID: <CAJna-HhS=iNcTcTzEm_GDtjzxbSTDJ0KvEjLvpnR_HngRYjHeA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=089e015389baf6771d04e3f82d1f
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1V9tsr-0003ba-EI
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
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, 15 Aug 2013 09:30:24 -0000
--089e015389baf6771d04e3f82d1f
Content-Type: text/plain; charset=ISO-8859-1
> Pieter, Matt and I also agreed that for maximum impact we should really
> try to ship payment protocol support in at least two clients simultaneously
> and ideally with a big merchant signed up too - to send a powerful message
> that we really mean it. Someone volunteered last week to do it for bitcoinj
> and if he doesn't pull through, I have some old code from EOY 2012 that I
> could update to the latest spec and ship at least some basic support. I'd
> hope that we can get Bitcoin Wallet or MultiBit updates out once bcj has
> support pretty fast.
>
We're planning to support payment protocol in Trezor as well, if it counts.
I think it's a missing piece in absolute security of hardware wallets.
slush
--089e015389baf6771d04e3f82d1f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
Pieter, Matt and I also agreed that for maximum impact we should really try=
to ship payment protocol support in at least two clients simultaneously an=
d ideally with a big merchant signed up too - to send a powerful message th=
at we really mean it. Someone volunteered last week to do it for bitcoinj a=
nd if he doesn't pull through, I have some old code from EOY 2012 that =
I could update to the latest spec and ship at least some basic support. I&#=
39;d hope that we can get Bitcoin Wallet or MultiBit updates out once bcj h=
as support pretty fast.</div>
</div></blockquote><div><br></div><div style>We're planning to support =
payment protocol in Trezor as well, if it counts. I think it's a missin=
g piece in absolute security of hardware wallets.</div><div style><br>
</div>
<div style>slush</div></div></div></div>
--089e015389baf6771d04e3f82d1f--
|
