Tagged new release 0.2.0

[Stefan Thomas]

Hey all,

There has been a tremendous amount of progress in bitcoinjs-lib recently. Big thanks to:

https://github.com/weilu
https://github.com/kyledrake
https://github.com/dcousens
https://github.com/abrkn
https://github.com/caedesvvv

and anyone else who contributed!

Changes since 0.1.3 include:

* HD Wallets
* Fee estimation
* Numerous bug fixes
* Improved test coverage

It's time to start publishing this new version of bitcoinjs to NPM. I went ahead and tagged an initial release 0.2.0, hopefully I'm not stepping on any toes. Kyle has maintainer permissions on NPM, so I'll leave it up to him to publish bugfix releases if needed. But as-is, this new version is already a vast improvement over the aging 0.1.3.


- Stefan

[Kyle Drake]

Hi Stefan!

I agree with your thoughts, it's time. Not perfect (code never is), but a great start and worth a release. I will publish it to NPM tomorrow.

Thanks to everyone that has contributed and helped to build this great project, and to those that have used it to build incredible things. And especially to Stefan Thomas, who's pioneering work in the cryptocurrency space is the shoulders we all stand on.

bitcoinjs-lib is now used by the vast majority of web/JS wallets, and has more than a million users, who have spent over a billion dollars worth of Bitcoin with this code (and variations of it).

Here's to another million (and another billion),

-Kyle

--
You received this message because you are subscribed to the Google Groups "BitcoinJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinjs+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kyle Drake]

Hi all, I wanted to give a quick update on the release.

I have decided to delay the release for a few more (2-7ish) days for the following reasons:

- Everyone is busy dealing with heartbleed, including myself. If you are running an HTTPS/SSL server, you are very likely affected by this vulnerability. This is a very, very serious issue, and I strongly recommend reading more about the situation and making sure that your infrastructure has been patched, and that you have revoked and reissued your SSL certificates, and recommend that your users change their passwords after you have done so. You can read more here: http://heartbleed.com, and see if your site is affected here: http://filippo.io/Heartbleed. This is not related to bitcoinjs-lib (infact, it I believe confirms a lot of bitcoinjs-lib's core tenets: Don't Trust the Server), but this problem is so bad, that I have zero qualms about mentioning it here, especially since a lot of you are probably doing Bitcoin related work on servers with SSL.

- There was a bug discovered that could lead to malformed secret keys: https://github.com/bitcoinjs/bitcoinjs-lib/issues/121. I intend to release 0.2.1 instead of 0.2.0, to prevent this bug from being published to production.

That's all for now, thank you. I will provide an update when the publish happens. Thank you,

-Kyle