From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1U7vdx-0004zn-HK for bitcoin-development@lists.sourceforge.net; Tue, 19 Feb 2013 22:26:33 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.178 as permitted sender) client-ip=209.85.214.178; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f178.google.com; Received: from mail-ob0-f178.google.com ([209.85.214.178]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1U7vdr-000894-BU for bitcoin-development@lists.sourceforge.net; Tue, 19 Feb 2013 22:26:33 +0000 Received: by mail-ob0-f178.google.com with SMTP id wd20so6995701obb.23 for ; Tue, 19 Feb 2013 14:26:22 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.171.5 with SMTP id aq5mr8705516oec.38.1361312781967; Tue, 19 Feb 2013 14:26:21 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.86.169 with HTTP; Tue, 19 Feb 2013 14:26:21 -0800 (PST) Date: Tue, 19 Feb 2013 23:26:21 +0100 X-Google-Sender-Auth: qC_xLePWs-lZzjD-gfuz7Zz_dYo Message-ID: From: Mike Hearn To: Bitcoin Dev Content-Type: multipart/alternative; boundary=bcaec5523dcccc20d304d61b540c 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 0.0 HTML_OBFUSCATE_05_10 BODY: Message is 5% to 10% HTML obfuscation 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: 1U7vdr-000894-BU Subject: [Bitcoin-development] bitcoinj 0.7 released X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 22:26:33 -0000 --bcaec5523dcccc20d304d61b540c Content-Type: text/plain; charset=UTF-8 I'm pleased to announce the release of version 0.7 of the bitcoinj Java library for working with Bitcoin. Bitcoinj forms the foundation of MultiBit, Bitcoin Wallet for Android, SatoshiDice and more. To get bitcoinj 0.7, check out our source from git and then run *git reset --hard a9bd8631b904*. This will place you on the 0.7 release in a secure manner. This paragraph was written on Tuesday 19th February 2013 and is signed with the following key, which will be used in all release announcements in future: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m. Signature for the last paragraph: IMvY1FsQobjU2t83ztQL3CTA+V+7WWKBFwMC+UWKCOMyTKA+73iSsFnCHdbFjAOEFMQH/NvJMTgGeVCSV/F9hfs= If you want to, you can check that the original announcement mail sent to bitcoinj@googlegroups.com is correctly signed with the google.com DKIM key, to establish a full chain of trust. *Release notes* - Thanks to Matt Corallo, we now support a* fully verifying mode* in addition to simplified verification. This is a tremendous amount of work that wouldn't have happened without Matt! Right now, we strongly discourage anyone from using it for mining (which is not supported out of the box anyway). Use it in a production environment only if you know what you're doing and are willing to risk losing money. If you do use it, let us know so we can contact you when problems are discovered. Read the documentation carefully before you begin. - Also thanks to Matt, *Bloom filtering* is now implemented and activated by default. When bitcoinj connects to a peer that supports Bloom filtering, only transactions relevant to the wallet will be downloaded which makes bandwidth usage scale with the size of your wallet, not global system activity. A configurable false positive ratio allows you to trade off bandwidth vs privacy. App developers don't need to do anything to take advantage of this, it is enabled automatically. - PeerGroup now pings its peers and calculates moving averages of the ping times. Ping time, versions and block heights are taken into account when selecting the peer to download the chain from. - You can now customize which outputs the wallet uses to create spends. The new default coin selector object allows you to spend unconfirmed change as long as it's been seen propagating across the network, addressing a common end-user pain point in wallet apps. - Optimized networking code for faster startup. - A new PeerMonitor example app shows how to put properties of connected peers into a GUI. - The Wallet is now decoupled from the BlockChain using the new BlockChainListener interface. This will simplify the development of some apps that want to process transactions but not maintain an actual wallet. - The dependencies of broadcast transactions are now downloaded and risk analyzed. At the moment they are only being checked for having a timelock. In future we may also analyze tree depth. The goal is to make certain kinds of protocol abuse harder. Wallets will reject timelocked transactions by default, this can be overridden via a property. - You can now create timelocked transactions with WalletTool? if you want to. - Compressed public keys are now used by default. - Support testnet3 - Support bitcoin-qt compatible message signing and verification. - ECDSA key recovery is now implemented and allows you to obtain the public key from an extended signature. If the signature is not extended then there are multiple key possibilities returned. - Many bugfixes and minor improvements API changes: - ECKey.sign() now takes a Sha256Hash as an argument and returns an ECDSASignature object in response. To get DER encoded signatures, use the encodeToDER() method of ECDSASignature. - ECKey.publicKeyFromPrivate now takes an additional compressed parameter. - PeerGroup.start()/PeerGroup.shutDown() now run asynchronously and return futures you can use to wait for them. You cannot restart a PeerGroup once it has been shut down any more. *Credits* * * Thanks to Matt Corallo (a.k.a. BlueMatt) for his huge contributions to this release. As always, thanks to Andreas Schildbach for his thorough testing, ideas and high volume of quality bug reports. Also thanks to Jim Burton for the same reasons. Finally thanks to Ben (piuk) of blockchain.info for funding the ECDSA key recovery feature. --bcaec5523dcccc20d304d61b540c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm pleased to announce the release of version 0.7 of the bitcoinj Ja= va library for working with Bitcoin. Bitcoinj forms the foundation of Multi= Bit, Bitcoin Wallet for Android, SatoshiDice and more.

To get= bitcoinj 0.7, check out our source from git and then run=C2=A0git reset= --hard=C2=A0a9bd8631b904. This will place you on the 0.7 release in a = secure manner. This paragraph was written on Tuesday 19th February 2013 and= is signed with the following key, which will be used in all release announ= cements in future:=C2=A016vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m.

Signature for the last= paragraph:=C2=A0IMvY1FsQobjU2t83ztQL3CTA+V+7WWKBFwMC+UWKCOMyTKA+73iSsFnCHd= bFjAOEFMQH/NvJMTgGeVCSV/F9hfs=3D

If you want to, you ca= n check that the original announcement mail sent to bitcoinj@googlegroups.com is correctly signed wit= h the=C2=A0google.com= =C2=A0DKIM key, to establish a full chain of trust.

Release notes
  • Thanks to Matt Corallo, = we now support a=C2=A0fully verifying mode=C2=A0in addition to simpl= ified verification. This is a tremendous amount of work that wouldn't h= ave happened without Matt! Right now, we strongly discourage anyone from us= ing it for mining (which is not supported out of the box anyway). Use it in= a production environment only if you know what you're doing and are wi= lling to risk losing money. If you do use it, let us know so we can contact= you when problems are discovered. Read the documentation carefully before = you begin.
  • Also thanks to Matt,=C2= =A0Bloom filtering=C2=A0is now implemented and activated by default.= When bitcoinj connects to a peer that supports Bloom filtering, only trans= actions relevant to the wallet will be downloaded which makes bandwidth usa= ge scale with the size of your wallet, not global system activity. A config= urable false positive ratio allows you to trade off bandwidth vs privacy. A= pp developers don't need to do anything to take advantage of this, it i= s enabled automatically.
  • PeerGroup= =C2=A0now pings its peers and calculates moving averages of the ping times.= Ping time, versions and block heights are taken into account when selectin= g the peer to download the chain from.
  • You can now customize wh= ich outputs the wallet uses to create spends. The new default coin selector= object allows you to spend unconfirmed change as long as it's been see= n propagating across the network, addressing a common end-user pain point i= n wallet apps.
  • Optimized networking cod= e for faster startup.
  • A new=C2=A0PeerMonitor=C2=A0example app shows how to put p= roperties of connected peers into a GUI.
  • The Wallet is now decoup= led from the=C2=A0BlockChain=C2=A0using the new=C2=A0BlockChainListener=C2=A0interface. This will simplify the developme= nt of some apps that want to process transactions but not maintain an actua= l wallet.
  • The dependencies of broa= dcast transactions are now downloaded and risk analyzed. At the moment they= are only being checked for having a timelock. In future we may also analyz= e tree depth. The goal is to make certain kinds of protocol abuse harder. W= allets will reject timelocked transactions by default, this can be overridd= en via a property.
  • You can now create timel= ocked transactions with WalletTool?= =C2=A0if you want to.
  • Compressed public keys a= re now used by default.
  • Support testnet3
  • Support bitcoin-qt compatible message signing and verification.
  • ECDSA key recovery is no= w implemented and allows you to obtain the public key from an extended sign= ature. If the signature is not extended then there are multiple key possibi= lities returned.
  • Many bugfixes and minor = improvements

API ch= anges:

  • ECKey.sign()=C2=A0now takes a=C2=A0Sha256Hash= =C2=A0as an argument and returns an=C2=A0ECDSASignature=C2= =A0object in response. To get DER encoded signatures, use the=C2=A0ECDSASignature.
  • ECKey.publicKe= yFromPrivate=C2=A0now takes an additional compressed parameter.
  • PeerGroup.star= t()/PeerGroup.shutDown()=C2=A0now run asynchronously and return future= s you can use to wait for them. You cannot restart aPeerGroup=C2=A0once it has been shut down any more.
Credits=
T= hanks to Matt Corallo (a.k.a. BlueMatt) for his huge contributions to this = release.

As always, thanks to = Andreas Schildbach for his thorough testing, ideas and high volume of quali= ty bug reports. Also thanks to Jim Burton for the same reasons.

Finally thanks to Ben= (piuk) of=C2=A0block= chain.info=C2=A0for funding the ECDSA key recovery feature.
--bcaec5523dcccc20d304d61b540c--