Bitcoin Core 0.9.2.1 has been released

[wumpus]

Bitcoin Core version 0.9.2.1 is now available from:

  https://bitcoin.org/bin/0.9.2.1/
  or https://bitcoin.org/en/download
  (0.9.2.1 fixes a UI issue on MacOSX as well as a rare shutdown issue, but apart from that is the same as 0.9.2)

This is a new minor version release, bringing mostly bug fixes and some minor
improvements. OpenSSL has been updated because of a security issue (CVE-2014-0224).
Upgrading to this release is recommended.

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.0 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).

Important changes
==================

Gitian OSX build
-----------------

The deterministic build system that was already used for Windows and Linux
builds is now used for OSX as well. Although the resulting executables have
been tested quite a bit, there could be possible regressions. Be sure to report
these on the Github bug tracker mentioned above.

Compatibility of Linux build
-----------------------------

For Linux we now build against Qt 4.6, and filter the symbols for libstdc++ and glibc.
This brings back compatibility with

- Debian 6+ / Tails
- Ubuntu 10.04
- CentOS 6.5

0.9.2 Release notes
=======================

The OpenSSL dependency in the gitian builds has been upgraded to 1.0.1h because of CVE-2014-0224.

RPC:
- Add `getwalletinfo`, `getblockchaininfo` and `getnetworkinfo` calls (will replace hodge-podge `getinfo` at some point)
- Add a `relayfee` field to `getnetworkinfo`
- Fix RPC related shutdown hangs and leaks
- Always show syncnode in `getpeerinfo`
- `sendrawtransaction`: report the reject code and reason, and make it possible to re-send transactions that are already in the mempool
- `getmininginfo` show right genproclimit

Command-line options:
- Fix `-printblocktree` output
- Show error message if ReadConfigFile fails

Block-chain handling and storage:
- Fix for GetBlockValue() after block 13,440,000 (BIP42)
- Upgrade leveldb to 1.17

Protocol and network code:
- Per-peer block download tracking and stalled download detection
- Add new DNS seed from bitnodes.io
- Prevent socket leak in ThreadSocketHandler and correct some proxy related socket leaks
- Use pnode->nLastRecv as sync score (was the wrong way around)

Wallet:
- Make GetAvailableCredit run GetHash() only once per transaction (performance improvement)
- Lower paytxfee warning threshold from 0.25 BTC to 0.01 BTC
- Fix importwallet nTimeFirstKey (trigger necessary rescans)
- Log BerkeleyDB version at startup
- CWallet init fix

Build system:
- Add OSX build descriptors to gitian
- Fix explicit --disable-qt-dbus
- Don't require db_cxx.h when compiling with wallet disabled and GUI enabled
- Improve missing boost error reporting
- Upgrade miniupnpc version to 1.9
- gitian-linux: --enable-glibc-back-compat for binary compatibility with old distributions
- gitian: don't export any symbols from executable
- gitian: build against Qt 4.6
- devtools: add script to check symbols from Linux gitian executables
- Remove build-time no-IPv6 setting

GUI:
- Fix various coin control visual issues
- Show number of in/out connections in debug console
- Show weeks as well as years behind for long timespans behind
- Enable and disable the Show and Remove buttons for requested payments history based on whether any entry is selected.
- Show also value for options overridden on command line in options dialog
- Fill in label from address book also for URIs
- Fixes feel when resizing the last column on tables (issue #2862)
- Fix ESC in disablewallet mode
- Add expert section to wallet tab in optionsdialog
- Do proper boost::path conversion (fixes unicode in datadir)
- Only override -datadir if different from the default (fixes -datadir in config file)
- Show rescan progress at start-up
- Show importwallet progress
- Get required locks upfront in polling functions (avoids hanging on locks)
- Catch Windows shutdown events while client is running
- Optionally add third party links to transaction context menu
- Check for !pixmap() before trying to export QR code (avoids crashes when no QR code could be generated)
- Fix "Start bitcoin on system login"

Miscellaneous:

- Replace non-threadsafe C functions (gmtime, strerror and setlocale)
- Add missing cs_main and wallet locks
- Avoid exception at startup when system locale not recognized
- Changed bitrpc.py's raw_input to getpass for passwords to conceal characters during command line input
- devtools: add a script to fetch and postprocess translations

Credits
--------

Thanks to everyone who contributed to this release:

- Addy Yeow
- Altoidnerd
- Andrea D'Amore
- Andreas Schildbach
- Bardi Harborow
- Brandon Dahler
- Bryan Bishop
- Chris Beams
- Christian von Roques
- Cory Fields
- Cozz Lovan
- daniel
- Daniel Newton
- David A. Harding
- ditto-b
- duanemoody
- Eric S. Bullington
- Fabian Raetz
- Gavin Andresen
- Gregory Maxwell
- gubatron
- Haakon Nilsen
- harry
- Hector Jusforgues
- Isidoro Ghezzi
- Jeff Garzik
- Johnathan Corgan
- jtimon
- Kamil Domanski
- langerhans
- Luke Dashjr
- Manuel Araoz
- Mark Friedenbach
- Matt Corallo
- Matthew Bogosian
- Meeh
- Michael Ford
- Michagogo
- Mikael Wikman
- Mike Hearn
- olalonde
- paveljanik
- peryaudo
- Philip Kaufmann
- philsong
- Pieter Wuille
- R E Broadley
- richierichrawr
- Rune K. Svendsen
- rxl
- shshshsh
- Simon de la Rouviere
- Stuart Cardall
- super3
- Telepatheic
- Thomas Zander
- Torstein Husebø
- Warren Togami
- Wladimir J. van der Laan
- Yoichi Hirai

[julius]

Great work. Thanks.

[100bitcoin]

GooD News

Why do u think `getinfo` is hodge-podge ?





_______________________________________________________________________________ _________________
Buy and Sell Bitcoins across the Globe :: www.100bit.co.in

[wumpus]

GooD News

Why do u think `getinfo` is hodge-podge ?

Well it combines information from different subsystems - the wallet, P2P networking, block chain handling, etc. It doesn't fit in the more modular approach that we have in mind. It is also slow to acquire all the locks and gather the information.

[Lethn]

I was suspicious at first but then I realised where the links were, I'll wait for an announcement on Bitcointalk before I click anything though lol

[gelar24]

news info good

great work thanks

[soccosocco]

GooD News

Great work. Thanks for information

[BitCoinDream]

GooD News

Why do u think `getinfo` is hodge-podge ?

Well it combines information from different subsystems - the wallet, P2P networking, block chain handling, etc. It doesn't fit in the more modular approach that we have in mind. It is also slow to acquire all the locks and gather the information.

What would happen to the APIs using getinfo data ?

[shorena]

GooD News

Why do u think `getinfo` is hodge-podge ?

Well it combines information from different subsystems - the wallet, P2P networking, block chain handling, etc. It doesn't fit in the more modular approach that we have in mind. It is also slow to acquire all the locks and gather the information.

What would happen to the APIs using getinfo data ?

Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.

---------------

Optionally add third party links to transaction context menu

Had no time to play with the new client yet, but this sounds like an invitation for phishing. nice feature to have.

[wumpus]

Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.

Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.

[BitCoinDream]

Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.

Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.

Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.

[S4VV4S]

Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.

Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.

Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.

The way I see it, it's much better for you when handling data with the new commands.
Much faster too.

[wumpus]

Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.

That's possible, but at some point it will lose information. For example, when the wallet is split off to another project, it will no longer contain wallet information. So no matter what you use it for, it will lose its remaining usefulness over time. At a certain point it's better to just remove the call and clean up the code a bit...

[saddambitcoin]

The font change looks like crap...I'm sure I'll get used to it though.

(Mac OSX)

[wumpus]

The font change looks like crap...I'm sure I'll get used to it though.

(Mac OSX)

Can you post a screenshot?

[keithers]

Are any of you using both Bitcoin Core and Litecoin QT on the same computer?   I am running Litecoin QT from an ultrabook with a dinky SSD harddrive, so I don't want to fill the whole thing up with blockchains..

[Cancan]

Awesome! Thank you core developers! Didn't get the chance to test the 9.2 RC, but will take this for a spin in short time.

[fsb4000]

Great work

[Meuh6879]

Crash at the shutdown (when i want close normally bitcoin-core).

Code:

2014-06-17 22:28:12 Added time data, samples 5, offset -1 (+0 minutes)
2014-06-17 22:28:12 nTimeOffset = +0  (+0 minutes)
2014-06-17 22:28:21 Requesting shutdown
2014-06-17 22:28:21 Running Shutdown in thread
2014-06-17 22:28:21 addcon thread interrupt
2014-06-17 22:28:21 dumpaddr thread stop
2014-06-17 22:28:21 msghand thread interrupt
2014-06-17 22:28:21 net thread interrupt
2014-06-17 22:28:22 opencon thread interrupt
2014-06-17 22:28:22 Shutdown : In progress...
2014-06-17 22:28:22 

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
cancel: Le descripteur de fichier fourni n'est pas valide       
G:\Bitcoin\bitcoin-qt.exe in Runaway exception       

2014-06-17 22:28:37 CDBEnv::EnvShutdown : Error 22 shutting down database environment: Invalid argument
Requesting initialize
Running AppInit2 in thread
2014-06-17 22:29:01 

System : windows XP 32 bits with all windows update installed ( automated : http://www.skyminds.net/pack-de-correctifs-windows-xp-post-sp3 )
Solo-mining with BFGMiner activate.
I use redirection of the blockchain folder (fixed drive).
I use the "no wallet" feature (node system).

old version 0.9.1 don't do this.

[ganabb]

Good News and Great work. But can someone kindly state the most important updates for the laymen amongst us.