bitcoinj 0.10.3

153 views
Skip to first unread message

Andreas Schildbach

unread,
Nov 21, 2013, 4:29:29 PM11/21/13
to bitc...@googlegroups.com, bitcoinj...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just pushed v0.10.3. It fixes the issues with outgoing transactions
stuck in a state where they are never being broadcasted.

For a more thorough list of changes, have a look at the git log.

The v0.10.3 release is signed with my GPG key. The git hash of the
release is c269d20. There is also a pre-built jar available in our
Maven repository:

http://code.google.com/p/bitcoinj/source/checkout?repo=distribution
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlKOezkACgkQymYr4YuHemCjMACdFcqHIDVBdeIgXwTOd8l2AH2q
AUEAn3YIosJUsP6gRCXdMSjsXJjXu9JW
=YhG5
-----END PGP SIGNATURE-----

Mike Hearn

unread,
Nov 24, 2013, 11:35:05 AM11/24/13
to bitcoinj...@googlegroups.com, bitc...@googlegroups.com
Please be aware that this release contains an API change. Andreas did not note it, unfortunately, but it's there.

The numSeenPeers member of TransactionConfidence now reflects the number of peers that announced the transaction. With the default settings this is not expected to go higher than half the number of connected peers now so code that relied on the former definition should be adjusted. What this also means is that for a newly broadcast transaction, numSeenPeers will be zero, not one as before.

The new definition is intended to make the definition match the name, and to avoid having transactions be flagged as broadcast when actually they never made it to the network.
Reply all
Reply to author
Forward
0 new messages