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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1V9sd1-00022I-Ly
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 08:09:55 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.177 as permitted sender)
client-ip=209.85.214.177; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f177.google.com;
Received: from mail-ob0-f177.google.com ([209.85.214.177])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V9scz-00048B-Lr
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 08:09:55 +0000
Received: by mail-ob0-f177.google.com with SMTP id f8so489941obp.36
for <bitcoin-development@lists.sourceforge.net>;
Thu, 15 Aug 2013 01:09:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.148.8 with SMTP id to8mr24926607obb.17.1376554188211;
Thu, 15 Aug 2013 01:09:48 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.80.165 with HTTP; Thu, 15 Aug 2013 01:09:48 -0700 (PDT)
In-Reply-To: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
References: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
Date: Thu, 15 Aug 2013 10:09:48 +0200
X-Google-Sender-Auth: H7pCWZ8arJvl0C_3x495lZexaz4
Message-ID: <CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=089e0139fc76670c2a04e3f7ffb0
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: 1V9scz-00048B-Lr
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 08:09:55 -0000
--089e0139fc76670c2a04e3f7ffb0
Content-Type: text/plain; charset=UTF-8
Sounds awesome!
Pieter told me at lunch that headers first cut sync time to 45 minutes for
him, which is another amazing improvement from the master of optimisations.
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.
Also, Jeff said that BitPay want to be a leader in support for the
protocol. So let's try and co-ordinate release dates so we can make a bit
of a splash and grab the ecosystems attention.
On Thu, Aug 15, 2013 at 2:29 AM, Gavin Andresen <gavinandresen@gmail.com>wrote:
> I plan on spending about half my time on code review and helping get pull
> requests tested, and the other half of my time working on code that
> probably won't make it into the 0.9 release.
>
Sounds brilliant. It'll be nice to see the pull request queue drain. Any
ideas what the non-0.9 code will be? Fee rework? DoS work?
--089e0139fc76670c2a04e3f7ffb0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Sounds awesome!<div class=3D"gmail_extra"><br>Pieter told =
me at lunch that headers first cut sync time to 45 minutes for him, which i=
s another amazing improvement from the master of optimisations.</div><div c=
lass=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Pieter, Matt and I also agreed that fo=
r maximum impact we should really try to ship payment protocol support in a=
t least two clients simultaneously and ideally with a big merchant signed u=
p too - to send a powerful message that we really mean it. Someone voluntee=
red last week to do it for bitcoinj and if he doesn't pull through, I h=
ave 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 Wall=
et or MultiBit updates out once bcj has support pretty fast.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Also, Jeff =
said that BitPay want to be a leader in support for the protocol. So let=
9;s try and co-ordinate release dates so we can make a bit of a splash and =
grab the ecosystems attention.<br>
<br><div class=3D"gmail_quote">On Thu, Aug 15, 2013 at 2:29 AM, Gavin Andre=
sen <span dir=3D"ltr"><<a href=3D"mailto:gavinandresen@gmail.com" target=
=3D"_blank">gavinandresen@gmail.com</a>></span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div dir=3D"ltr"><div>I plan on spending about half my time on code review =
and helping get pull requests tested, and the other half of my time working=
on code that probably won't make it into the 0.9 release.</div></div>
</blockquote><div><br></div><div>Sounds brilliant. It'll be nice to see=
the pull request queue drain. Any ideas what the non-0.9 code will be? Fee=
rework? DoS work?=C2=A0</div></div></div></div>
--089e0139fc76670c2a04e3f7ffb0--
|
