bitcoinj 0.6 is now available

[Mike Hearn]

I'm pleased to announce the release of version 0.6 of bitcoinj, the leading Java implementation of Bitcoin. You can download the source from Google Code, or use the release-0.6 branch from git. Our Nexus repository will be updated soon.

This release focuses on improved compliance with the protocol, improved and more scalable network handling, a more flexible send API, other misc API improvements and of course, a large pile of bug fixes. You should upgrade your software to use bitcoinj 0.6 as soon as possible, if only to benefit from the fixes - the API changes are minimal so it should be easy.

In more detail:

• Thanks to Jim Burton, the wallet now stores the depth and work done for all transactions, and coinbase transactions are now processed correctly. The ability to handle pubkey-only outputs was added, so these are now spendable. Migration from 0.5 wallets that don't store this is supported, but only for depth, by using WalletProtobufSerializer.setChainHeight().
• Made some more APIs documented and public.
• Improved block chain download handling.
• Added compatibility with the broken URIs generated by blockchain.info, meaning that the iPhone app and Android apps can now read each others QRcodes.
• Wallets can now auto-save themselves, taking the hassle of managing wallet persistence away from your app. See the javadocs for Wallet.autoSaveToFile() for information on this.
• The network layer was rewritten on top of Netty to be more robust, more scalable and to remove flakyness in the unit tests. Thanks to Miron Cuperman for this work.
• Thanks to Matt Corallo the ping/pong protocol is now supported. Also various protocol conformance issues and other misc bugs were resolved.
• WalletTool now has a RAW_DUMP option that prints the raw protocol buffer form as text.
• You can now explicitly set fees on a created transaction using the fee member of SendRequest. Please note that the correct fees for a transaction are still not auto-calculated or minimized. This will come in a future release.
• Many bug fixes.

API changes:

• TransactionConfidence.OVERRIDDEN_BY_DOUBLE_SPEND is now called DEAD
• PeerGroup.broadcastTransaction now returns a Guava ListenableFuture (which is a subclass of Future, so it's compatible). The future completes when the transaction has been heard back from the network, instead of just being written out.
• Wallet.sendCoins() now returns a SendResult that contains both the transaction, and the future returned by PeerGroup.broadcastTransaction(), so it will no longer block. As a result sendCoinsAsync() has been removed.
• Various send methods on Wallet now take a SendRequest object that lets you customize the created transactions. The methods that let you explicitly set the change address are removed, you should set the changeAddress member of the SendRequest instead.

Future work will involve merging more changes from Matt Corallo to make bitcoinj optionally fully validating, supporting Bloom filtering of connections (again thanks to Matt), merging encrypted wallets from Jim Burton, and supporting testnet3.[/list]

[molecular]

Am I doing something wrong? This worked 2 days ago:

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/
Initialized empty Git repository in /home/nick/workspace/bitcoinj/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?

[Andreas Schildbach]

Am I doing something wrong? This worked 2 days ago:

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/
Initialized empty Git repository in /home/nick/workspace/bitcoinj/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?

Works at my place. Just try again?

[molecular]

Am I doing something wrong? This worked 2 days ago:

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/
Initialized empty Git repository in /home/nick/workspace/bitcoinj/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?

Works at my place. Just try again?

Tried again... no luck.

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/ test
Initialized empty Git repository in /home/nick/workspace/test/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?
nick@zero ~/workspace $ ping code.google.com
PING code.l.google.com (74.125.228.96) 56(84) bytes of data.
64 bytes from iad23s08-in-f0.1e100.net (74.125.228.96): icmp_req=1 ttl=53 time=123 ms

what IP do you get for code.google.com?

[Andreas Schildbach]

what IP do you get for code.google.com?

code.l.google.com 173.194.69.113

Are you able to clone other repos? And other repos from different services (e.g. github)?

[Mushroomized]

cool gunna play around with this

[Sergio_Demian_Lerner]

I'm pleased to announce the release of version 0.6 of bitcoinj, the leading Java implementation of Bitcoin. You can download the source from Google Code, or use the release-0.6 branch from git. Our Nexus repository will be updated soon.

Mike, don't forget to implement all the DoS checks Satoshi client has implemented. (Check https://en.bitcoin.it/wiki/Weaknesses#Denial_of_Service_.28DoS.29_attacks)


For instance, each time you receive an alert you process it with processAlert(), without checking for duplicates. Checking the alert requires CPU and possibly GUI resources to show the alert to the user.

A malicious user may attack your application by continuously sending repeated alerts

Best regards, Sergio.

[Mike Hearn]

For 0.6 there's no need to worry about DoS attacks because it's an SPV client that chooses who it connects to. In the unlikely event that you connect to a node that recognizes bitcoinj in the subVer and chooses to try and flood you with bad traffic, you can just restart the app and connect to some new nodes. No big deal.

If you're taking part in the P2P network as a full node DoS and chain split attacks are a bigger issue, and that will start to be a concern from 0.7 onwards. I'm not working on fully validating mode myself, that's from BlueMatt, so most likely 0.7 will just ship with a warning that you shouldn't allow inbound connections and you shouldn't mine against it.

[paraipan]

Am I doing something wrong? This worked 2 days ago:

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/
Initialized empty Git repository in /home/nick/workspace/bitcoinj/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?

Works at my place. Just try again?

Tried again... no luck.

nick@zero ~/workspace $ git clone https://code.google.com/p/bitcoinj/ test
Initialized empty Git repository in /home/nick/workspace/test/.git/
fatal: https://code.google.com/p/bitcoinj//info/refs not found: did you run git update-server-info on the server?
nick@zero ~/workspace $ ping code.google.com
PING code.l.google.com (74.125.228.96) 56(84) bytes of data.
64 bytes from iad23s08-in-f0.1e100.net (74.125.228.96): icmp_req=1 ttl=53 time=123 ms

what IP do you get for code.google.com?

Try with:

Code:

git clone https://code.google.com/p/bitcoinj test

^ notice the missing slash ( / )