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
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
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 1S6193-0004yV-2Z
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Mar 2012 14:50:13 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com;
helo=mail-we0-f175.google.com;
Received: from mail-we0-f175.google.com ([74.125.82.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1S618y-0002HV-Rm
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Mar 2012 14:50:13 +0000
Received: by wera1 with SMTP id a1so1595681wer.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Mar 2012 06:50:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.139.129 with SMTP id c1mr1605084wej.48.1331304602728; Fri,
09 Mar 2012 06:50:02 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.216.162.66 with HTTP; Fri, 9 Mar 2012 06:50:02 -0800 (PST)
Date: Fri, 9 Mar 2012 15:50:02 +0100
X-Google-Sender-Auth: dKuZbLD7QI1DHDhkg2pEj_qSkbM
Message-ID: <CANEZrP2YHcDirFus=tOZniDf2bb=GdVSf09Ov1N=iqKa4T-wUw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=0016e6d975e8eef8eb04bad081f7
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: 1S618y-0002HV-Rm
Subject: [Bitcoin-development] [ANNOUNCE] BitCoinJ 0.4
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: Fri, 09 Mar 2012 14:50:13 -0000
--0016e6d975e8eef8eb04bad081f7
Content-Type: text/plain; charset=UTF-8
I'm pleased to announce the release of BitCoinJ 0.4, the leading Java
implementation of the Bitcoin protocol. BitCoinJ implements simplified
payment verification, a lightweight mode in which no central server or
authority is needed but the resource requirements are still low enough to
be usable on smartphones.
This version of the library is used in the new releases of Android Wallet
and MultiBit.
New in this release <http://code.google.com/p/bitcoinj/wiki/ReleaseNotes>
- Ability to use "getheaders" to quickly catch up new users to the head
of the chain. This is a big performance win.
- ECKeys no longer require the private part, allowing for "watching
wallets" that cannot spend, but still gather and track the transactions
associated with the public keys.
- A new API that implements transaction confidences. Get a quick summary
or detailed information about how much confidence you can have that a given
transaction won't be reversed.
- A new DerbyBlockStore that stores block headers and related data in
the Apache Derby relational database.
- Protocol buffers are now a supported serialization format for the
wallet. This means BitCoinJ based protobuf wallets can be read and
manipulated by any language/platform with a protobufs implementation, which
is most of them. There are extension points in the format to allow third
parties to add new features.
- Various new event listeners that help you learn when the state of the
wallet or transactions change.
- Support for post February 20th version handshakes (most library users
already got this fix via backports)
- All event listeners are now allowed to remove themselves during their
own execution.
- New APIs that allow you to create offline transactions and then
broadcast them at a later point. Pending relevant transactions are recorded
and announced to all newly connected nodes, ensuring a transaction won't
"get lost" if there was flaky network connectivity at the time of creation.
Pending transactions are supported much better in this release than in
previous releases.
- Wallet now can now take an invalid transaction and complete it by
adding sufficient inputs and a change output. This enables the creation of
multi-sends, as well as making experimentation with contracts easier.
- Support for BIP 14: apps can now set their own "user agent" which will
be put in the subVer field along with the library version.
- Updated DNS seeds list.
- A new WalletTool program for command line usage, and a ToyWallet app
showing how to set everything up.
- Support parsing and checking of alert messages.
- New articles explaining how to use the library:
- Working with
transactions<http://code.google.com/p/bitcoinj/wiki/WorkingWithTransactions>
- Working with the
wallet<http://code.google.com/p/bitcoinj/wiki/WorkingWithTheWallet>
- The usual assortment of bugfixes, new APIs, robustness and test suite
improvements.
Thanks to everyone who contributed to this release, in particular Andreas
Schildbach, Miron Cuperman, Roman Maneleil, Chris Rico and Vasile Rotaru.
In the next release cycle, I'll be focusing on the following areas:
1. Real support for transaction fee calculations (most users apply a
custom patch for this today)
2. A better block chain API
3. Have the library manage save points for the wallet itself
4. Further chain download time optimizations
5. More support for moving apps onto "work done" as a confidence
measurement
Of course contributors are welcome to work on whatever they want.
thanks
--0016e6d975e8eef8eb04bad081f7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<span style>I'm pleased to announce the release of BitCoinJ 0.4, the le=
ading Java implementation of the Bitcoin protocol. BitCoinJ implements simp=
lified payment verification, a lightweight mode in which no central server =
or authority is needed but the resource requirements are still low enough t=
o be usable on smartphones.</span><div style>
<br></div><div style>This version of the library is used in the new release=
s of Android Wallet and MultiBit.<br><div><br></div><div><a href=3D"http://=
code.google.com/p/bitcoinj/wiki/ReleaseNotes" target=3D"_blank" style=3D"co=
lor:rgb(17,85,204)">New in this release</a></div>
<div><ul style=3D"padding-left:25px;max-width:62em"><li style=3D"margin-lef=
t:15px;margin-bottom:0.3em">Ability to use "getheaders" to quickl=
y catch up new users to the head of the chain. This is a big performance wi=
n.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">ECKeys no longer require=
the private part, allowing for "watching wallets" that cannot sp=
end, but still gather and track the transactions associated with the public=
keys.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">A new API that implement=
s transaction confidences. Get a quick summary or detailed information abou=
t how much confidence you can have that a given transaction won't be re=
versed.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">A new DerbyBlockStore=C2=
=A0that stores block headers and related data in the Apache Derby relationa=
l database.</li><li style=3D"margin-left:15px;margin-bottom:0.3em">Protocol=
buffers are now a supported serialization format for the wallet. This mean=
s BitCoinJ based protobuf wallets can be read and manipulated by any langua=
ge/platform with a protobufs implementation, which is most of them. There a=
re extension points in the format to allow third parties to add new feature=
s.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">Various new event listen=
ers that help you learn when the state of the wallet or transactions change=
.</li><li style=3D"margin-left:15px;margin-bottom:0.3em">Support for post F=
ebruary 20th version handshakes (most library users already got this fix vi=
a backports)</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">All event listeners are =
now allowed to remove themselves during their own execution.</li><li style=
=3D"margin-left:15px;margin-bottom:0.3em">New APIs that allow you to create=
offline transactions and then broadcast them at a later point. Pending rel=
evant transactions are recorded and announced to all newly connected nodes,=
ensuring a transaction won't "get lost" if there was flaky n=
etwork connectivity at the time of creation. Pending transactions are suppo=
rted much better in this release than in previous releases.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">Wallet now can now take =
an invalid transaction and complete it by adding sufficient inputs and a ch=
ange output. This enables the creation of multi-sends, as well as making ex=
perimentation with contracts easier.</li>
<li style=3D"margin-left:15px;margin-bottom:0.3em">Support for BIP 14: apps=
can now set their own "user agent" which will be put in the subV=
er field along with the library version.</li><li style=3D"margin-left:15px;=
margin-bottom:0.3em">
Updated DNS seeds list.</li><li style=3D"margin-left:15px;margin-bottom:0.3=
em">A new WalletTool=C2=A0program for command line usage, and a ToyWallet=
=C2=A0app showing how to set everything up.</li><li style=3D"margin-left:15=
px;margin-bottom:0.3em">
Support parsing and checking of alert messages.</li><li style=3D"margin-lef=
t:15px;margin-bottom:0.3em">New articles explaining how to use the library:=
=C2=A0</li><ul><li style=3D"margin-left:15px;margin-bottom:0.3em"><font fac=
e=3D"arial, sans-serif"><a href=3D"http://code.google.com/p/bitcoinj/wiki/W=
orkingWithTransactions" target=3D"_blank" style=3D"color:rgb(17,85,204)">Wo=
rking with transactions</a></font></li>
<li style=3D"margin-left:15px;margin-bottom:0.3em"><font face=3D"arial, san=
s-serif"><a href=3D"http://code.google.com/p/bitcoinj/wiki/WorkingWithTheWa=
llet" target=3D"_blank" style=3D"color:rgb(17,85,204)">Working with the wal=
let</a></font></li>
</ul><li style=3D"margin-left:15px;margin-bottom:0.3em">The usual assortmen=
t of bugfixes, new APIs, robustness and test suite improvements.</li></ul><=
/div><div><div>Thanks to everyone who contributed to this release, in parti=
cular Andreas Schildbach, Miron Cuperman, Roman Maneleil, Chris Rico and Va=
sile Rotaru.</div>
<div><br></div><div>In the next release cycle, I'll be focusing on the =
following areas:</div><div><ol><li style=3D"margin-left:15px">Real support =
for transaction fee calculations (most users apply a custom patch for this =
today)</li>
<li style=3D"margin-left:15px">A better block chain API</li><li style=3D"ma=
rgin-left:15px">Have the library manage save points for the wallet itself</=
li><li style=3D"margin-left:15px">Further chain download time optimizations=
</li>
<li style=3D"margin-left:15px">More support for moving apps onto "work=
done" as a confidence measurement</li></ol><div>Of course contributor=
s are welcome to work on whatever they want.</div></div><div><br></div><div=
>
thanks</div></div></div>
--0016e6d975e8eef8eb04bad081f7--
|
