Bitcoin Forum

Bitcoin Core version 0.9.3rc1 is now available from:

  https://bitcoin.org/bin/0.9.3/test/

This is a release candidate (test version) for a new minor version release, bringing
only bug fixes and updated translations.

Please report bugs using the issue tracker at github:

  https://github.com/bitcoin/bitcoin/issues

Upgrading and downgrading
==========================

How to Upgrade
--------------

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).

If you are upgrading from version 0.7.2 or earlier, the first time you run
0.9.3 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.

Downgrading warnings
--------------------

The 'chainstate' for this release is not always compatible with previous
releases, so if you run 0.9.x and then decide to switch back to a
0.8.x release you might get a blockchain validation error when starting the
old release (due to 'pruned outputs' being omitted from the index of
unspent transaction outputs).

Running the old release with the -reindex option will rebuild the chainstate
data structures and correct the problem.

Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan
the blockchain for missing spent coins, which will take a long time (tens
of minutes on a typical machine).

0.9.3 Release notes
=======================

RPC:
- Avoid a segfault on getblock if it can't read a block from disk
- Add paranoid return value checks in base58

Protocol and network code:
- Don't poll showmyip.com, it doesn't exist anymore
- Add a way to limit deserialized string lengths and use it
- Add a new checkpoint at block 295,000
- Increase IsStandard() scriptSig length
- Avoid querying DNS seeds, if we have open connections

Wallet:
- Check redeemScript size does not exceed 520 byte limit
- Ignore (and warn about) too-long redeemScripts while loading wallet

GUI:
- fix 'opens in testnet mode when presented with a BIP-72 link with no fallback'
- AvailableCoins: acquire cs_main mutex
- Fix unicode character display on MacOSX

Miscellaneous:
- key.cpp: fail with a friendlier message on missing ssl EC support
- Remove bignum dependency for scripts
- Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitcoin Core)
- Upgrade miniupnpc to 1.9.20140701
- Fix boost detection in build system on some platforms

Credits
--------

Thanks to everyone who contributed to this release:

- Andrew Poelstra
- Cory Fields
- Jeff Garzik
- Johnathan Corgan
- Julian Haight
- Michael Ford
- Pavel Vasin
- Peter Todd
- Pieter Wuille
- Rose Toomey
- Ruben Dario Ponticelli
- Trevin Hofmann
- Wladimir J. van der Laan
- Zak Wilcox

As well as everyone that helped translating on Transifex (https://www.transifex.com/projects/p/bitcoin/)

that's a good news :)

I just downloaded earlier version on my Mac 3 hours ago, Do I need re-download all of them and delete earlier version? :/

I can see Gavin is not among the thanks list. Does not he contribute anymore ?

Not really. 0.9.2.1 is still the latest stable version. This is a release candidate, so is meant for testing.

Not to this minor release, which has only a very small number of fixes. He did sign the DMG and MacOSX binaries. He certainly still contributes to the next major version (what is in git master).

Great! Is the increase in ScriptSig length to account for greater M and N values of M-of-N multisig transactions?

Great! Progress is a good thing  :)

how to upgrade on ubuntu when stable version released? I could just do "apt-get upgrade bitcoin"?

Correct:

commit 84fe0ffd685627689bbbcd14cf419938f2a100b2
Author: Peter Todd <pete@petertodd.org>
Date:   Mon Mar 10 16:38:44 2014 -0400

    Increase IsStandard() scriptSig length
   
    Removes the limits on number of pubkeys for P2SH CHECKMULTISIG outputs.
    Previously with the 500 byte scriptSig limit there were odd restrictions
    where even a 1-of-12 P2SH could be spent in a standard transaction(1),
    yet multisig scriptPubKey's requiring more signatures quickly ran out of
    scriptSig space.
   
    From a "stuff-data-in-the-blockchain" point of view not much has changed
    as with the prior commit now only allowing the dummy value to be null
    the newly allowed scriptSig space can only be used for signatures. In
    any case, just using more outputs is trivial and doesn't cost much.
   
    1) See 779b519480d8c5346de6e635119c7ee772e97ec872240c45e558f582a37b4b73
       Mined by BTC Guild.

You will have to wait for the repo [1] to be updated. AFAIK the person looking after it does so pretty fast.

[1] https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin

 :) On the run ... let's evaluate this if this build crash on WinXP like the 0.9.2.1  ;D (please, no ! The 0.9.1 is rock stable, no crash at all)

Sound good, no problem for now ... but it must pass the 48h of running time to rise in my mind.  8)

 :( No ... after 19 hours of run ... it's crash without a debuglog entry (or error box displayed).
Like the 0.9.2 and 0.9.2.1  :-\


WinXP 32bits SP3+all available updates

But It's not official yet? It's only in beta right?

Thanks gotta download it rightway,I have to re-download the blockchain once again or it does merges with previous version i have installed

Did you have to quote the whole post for that single line?

Anyway, no you dont have to download the whole blockchain again, just close the existing installation and install the new one over it (e.g. in Win just run the setup w/o uninstalling)

This is great news :) any kind of progress whether it be for testing or not is always a good sign as it shows things are progressing in a way they should be and not keeping to a stand still.

Excellent, fixes are good. I'm amazed by the number of opened issues though.
How far is some version with "new features"?
I'm going to upgrade today.

You don't get any kind of traceback or core dump from the OS either? We really need one to even start debugging this problem.
What is your usage scenario? Mining? A lot of RPC calls?
Does this happen in both bitcoin-qt and bitcoind?

Since the 0.9.1 (rock stable), the new products of bitcoin-core crash without debuglog entry or error message (windows box).
I use BFGMiner to mining with 12GH/s USB miner.

First report of this crash is here : https://bitcointalk.org/index.php?topic=655359.msg7370223#msg7370223 (read the folowed message to retrace the bug).

rc2 has been uploaded last weekend to https://bitcoin.org/bin/0.9.3/test/, with some further fixes in network and memory behaviour

 :) On the run for the test !

The last time it took ~ 2 months.

24h on RC2 : good.  :)

Imma test it out.

Running rc2 for a week, and rc1 for a month before that. Seems solid. Resource usage looks unchanged from 0.9.2.

 :( nope ... always crash after 33h ... without warning (WinXP SP3 with all availables updates).

Please report that issue including more details (perhaps also debug.log) here or over at https://github.com/bitcoin/bitcoin/issues.

Thanks,
Dia

Is this the latest version of the Bitcoincore -qt?

RC stands for Release Canditate. If you need the very latest you will have to look on github.

0.9.2.1 is the current release.

https://bitcoin.org/en/version-history

The ppa is now updated to 9.3 already, but it's not announced yet on the bitcoin.org page?

How do anyone compiler from sources and no xxxxx-qt.pro file anymore?

ps: compile for Ubunt 12.04.