Bitcoin 0.9.0 FINAL is available [Changelog] [Download]

[rme]

THIS IS NOT THE LATEST RELEASE OF BITCOIN CORE
NEW RELEASE: 0.9.1 https://bitcointalk.org/index.php?topic=562400.0









The Core Developers of Bitcoin released the 0.9.0 FINAL of Bitcoin Core (aka Bitcoin QT).


DOWNLOAD:
https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-linux.tar.gz
https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-macosx.dmg
https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-win.zip
https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-win32-setup.exe
https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-win64-setup.exe

Code:

15616baea0640277c81a8ca4d3e0d963834b8a7d  bitcoin-0.9.0-linux.tar.gz
82b7210587c2037beb5d0b3b9ef2643b7580dfe7  bitcoin-0.9.0-macosx.dmg
5bac25ffc2afa7eaea2bbbd783b787325cf8b537  bitcoin-0.9.0-win.zip
23b315772c86389a8ac05c13bd352f4ec631a659  bitcoin-0.9.0-win32-setup.exe
b404b0ed348be5b15c0704bfdc6b838a732c338e  bitcoin-0.9.0-win64-setup.exe

This is a Final Version, but its the same as 0.9.0rc3

Sources:
https://github.com/bitcoin/bitcoin/releases
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.9.0/
https://bitcoin.org/bin/0.9.0/README.txt


Bitcoin Core version 0.9.0 is now available from:

  https://bitcoin.org/bin/0.9.0/

This is a release candidate for a new major version. A major version brings
both new features and bug fixes.

Please report bugs using the issue tracker at github:

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

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), uninstall all
earlier versions of Bitcoin, 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.

On Windows, do not forget to uninstall all earlier versions of the Bitcoin
client first, especially if you are switching to the 64-bit version.

Windows 64-bit installer
-------------------------

New in 0.9.0 is the Windows 64-bit version of the client. There have been
frequent reports of users running out of virtual memory on 32-bit systems
during the initial sync. Because of this it is recommended to install the
64-bit version if your system supports it.

NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP
and the SHA256SUMS.asc file to make sure your binaries are correct.
In the final 0.9.0 release, Windows setup.exe binaries will be code-signed.

OSX 10.5 / 32-bit no longer supported
-------------------------------------

0.9.0 drops support for older Macs. The minimum requirements are now:
* A 64-bit-capable CPU (see http://support.apple.com/kb/ht3696);
* Mac OS 10.6 or later (see https://support.apple.com/kb/ht1633).

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

The 'chainstate' for this release is not always compatible with previous
releases, so if you run 0.9 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).

Rebranding to Bitcoin Core
---------------------------

To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we
have renamed the reference client to Bitcoin Core.

Autotools build system
-----------------------

For 0.9.0 we switched to an autotools-based build system instead of individual
(q)makefiles.

Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and
bitcoind makes it easier for experienced open source developers to contribute
to the project.

Be sure to check doc/build-*.md for your platform before building from source.

Bitcoin-cli
-------------

Another change in the 0.9 release is moving away from the bitcoind executable
functioning both as a server and as a RPC client. The RPC client functionality
("tell the running bitcoin daemon to do THIS") was split into a separate
executable, 'bitcoin-cli'. The RPC client code will eventually be removed from
bitcoind, but will be kept for backwards compatibility for a release or two.

`walletpassphrase` RPC
-----------------------

The behavior of the `walletpassphrase` RPC when the wallet is already unlocked
has changed between 0.8 and 0.9.

The 0.8 behavior of `walletpassphrase` is to fail when the wallet is already unlocked:

    > walletpassphrase 1000
    walletunlocktime = now + 1000
    > walletpassphrase 10
    Error: Wallet is already unlocked (old unlock time stays)

The new behavior of `walletpassphrase` is to set a new unlock time overriding
the old one:

    > walletpassphrase 1000
    walletunlocktime = now + 1000
    > walletpassphrase 10
    walletunlocktime = now + 10 (overriding the old unlock time)

Transaction malleability-related fixes
--------------------------------------

This release contains a few fixes for transaction ID (TXID) malleability
issues:

- -nospendzeroconfchange command-line option, to avoid spending
  zero-confirmation change
- IsStandard() transaction rules tightened to prevent relaying and mining of
  mutated transactions
- Additional information in listtransactions/gettransaction output to
  report wallet transactions that conflict with each other because
  they spend the same outputs.
- Bug fixes to the getbalance/listaccounts RPC commands, which would report
  incorrect balances for double-spent (or mutated) transactions.
- New option: -zapwallettxes to rebuild the wallet's transaction information

Transaction Fees
----------------

This release drops the default fee required to relay transactions across the
network and for miners to consider the transaction in their blocks to
0.01mBTC per kilobyte.

Note that getting a transaction relayed across the network does NOT guarantee
that the transaction will be accepted by a miner; by default, miners fill
their blocks with 50 kilobytes of high-priority transactions, and then with
700 kilobytes of the highest-fee-per-kilobyte transactions.

The minimum relay/mining fee-per-kilobyte may be changed with the
minrelaytxfee option. Note that previous releases incorrectly used
the mintxfee setting to determine which low-priority transactions should
be considered for inclusion in blocks.

The wallet code still uses a default fee for low-priority transactions of
0.1mBTC per kilobyte. During periods of heavy transaction volume, even this
fee may not be enough to get transactions confirmed quickly; the mintxfee
option may be used to override the default.

0.9.0 Release notes
=======================

RPC:

- New notion of 'conflicted' transactions, reported as confirmations: -1
- 'listreceivedbyaddress' now provides tx ids
- Add raw transaction hex to 'gettransaction' output
- Updated help and tests for 'getreceivedby(account|address)'
- In 'getblock', accept 2nd 'verbose' parameter, similar to getrawtransaction,
  but defaulting to 1 for backward compatibility
- Add 'verifychain', to verify chain database at runtime
- Add 'dumpwallet' and 'importwallet' RPCs
- 'keypoolrefill' gains optional size parameter
- Add 'getbestblockhash', to return tip of best chain
- Add 'chainwork' (the total work done by all blocks since the genesis block)
  to 'getblock' output
- Make RPC password resistant to timing attacks
- Clarify help messages and add examples
- Add 'getrawchangeaddress' call for raw transaction change destinations
- Reject insanely high fees by default in 'sendrawtransaction'
- Add RPC call 'decodescript' to decode a hex-encoded transaction script
- Make 'validateaddress' provide redeemScript
- Add 'getnetworkhashps' to get the calculated network hashrate
- New RPC 'ping' command to request ping, new 'pingtime' and 'pingwait' fields
  in 'getpeerinfo' output
- Adding new 'addrlocal' field to 'getpeerinfo' output
- Add verbose boolean to 'getrawmempool'
- Add rpc command 'getunconfirmedbalance' to obtain total unconfirmed balance
- Explicitly ensure that wallet is unlocked in `importprivkey`
- Add check for valid keys in `importprivkey`

Command-line options:

- New option: -nospendzeroconfchange to never spend unconfirmed change outputs
- New option: -zapwallettxes to rebuild the wallet's transaction information
- Rename option '-tor' to '-onion' to better reflect what it does
- Add '-disablewallet' mode to let bitcoind run entirely without wallet (when
  built with wallet)
- Update default '-rpcsslciphers' to include TLSv1.2
- make '-logtimestamps' default on and rework help-message
- RPC client option: '-rpcwait', to wait for server start
- Remove '-logtodebugger'
- Allow `-noserver` with bitcoind

Block-chain handling and storage:

- Update leveldb to 1.15
- Check for correct genesis (prevent cases where a datadir from the wrong
  network is accidentally loaded)
- Allow txindex to be removed and add a reindex dialog
- Log aborted block database rebuilds
- Store orphan blocks in serialized form, to save memory
- Limit the number of orphan blocks in memory to 750
- Fix non-standard disconnected transactions causing mempool orphans
- Add a new checkpoint at block 279,000

Wallet:

- Bug fixes and new regression tests to correctly compute
  the balance of wallets containing double-spent (or mutated) transactions
- Store key creation time. Calculate whole-wallet birthday.
- Optimize rescan to skip blocks prior to birthday
- Let user select wallet file with -wallet=foo.dat
- Consider generated coins mature at 101 instead of 120 blocks
- Improve wallet load time
- Don't count txins for priority to encourage sweeping
- Don't create empty transactions when reading a corrupted wallet
- Fix rescan to start from beginning after importprivkey
- Only create signatures with low S values

Mining:

- Increase default -blockmaxsize/prioritysize to 750K/50K
- 'getblocktemplate' does not require a key to create a block template
- Mining code fee policy now matches relay fee policy

Protocol and network:

- Drop the fee required to relay a transaction to 0.01mBTC per kilobyte
- Send tx relay flag with version
- New 'reject' P2P message (BIP 0061, see
  https://gist.github.com/gavinandresen/7079034 for draft)
- Dump addresses every 15 minutes instead of 10 seconds
- Relay OP_RETURN data TxOut as standard transaction type
- Remove CENT-output free transaction rule when relaying
- Lower maximum size for free transaction creation
- Send multiple inv messages if mempool.size > MAX_INV_SZ
- Split MIN_PROTO_VERSION into INIT_PROTO_VERSION and MIN_PEER_PROTO_VERSION
- Do not treat fFromMe transaction differently when broadcasting
- Process received messages one at a time without sleeping between messages
- Improve logging of failed connections
- Bump protocol version to 70002
- Add some additional logging to give extra network insight
- Added new DNS seed from bitcoinstats.com

Validation:

- Log reason for non-standard transaction rejection
- Prune provably-unspendable outputs, and adapt consistency check for it.
- Detect any sufficiently long fork and add a warning
- Call the -alertnotify script when we see a long or invalid fork
- Fix multi-block reorg transaction resurrection
- Reject non-canonically-encoded serialization sizes
- Reject dust amounts during validation
- Accept nLockTime transactions that finalize in the next block

Build system:

- Switch to autotools-based build system
- Build without wallet by passing `--disable-wallet` to configure, this
  removes the BerkeleyDB dependency
- Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more
  recent versions
- Windows 64-bit build support
- Solaris compatibility fixes
- Check integrity of gitian input source tarballs
- Enable full GCC Stack-smashing protection for all OSes

GUI:

- Switch to Qt 5.2.0 for Windows build
- Add payment request (BIP 0070) support
- Improve options dialog
- Show transaction fee in new send confirmation dialog
- Add total balance in overview page
- Allow user to choose data directory on first start, when data directory is
  missing, or when the -choosedatadir option is passed
- Save and restore window positions
- Add vout index to transaction id in transactions details dialog
- Add network traffic graph in debug window
- Add open URI dialog
- Add Coin Control Features
- Improve receive coins workflow: make the 'Receive' tab into a form to request
  payments, and move historical address list functionality to File menu.
- Rebrand to `Bitcoin Core`
- Move initialization/shutdown to a thread. This prevents "Not responding"
  messages during startup. Also show a window during shutdown.
- Don't regenerate autostart link on every client startup
- Show and store message of normal bitcoin:URI
- Fix richtext detection hang issue on very old Qt versions
- OS X: Make use of the 10.8+ user notification center to display Growl-like
  notifications
- OS X: Added NSHighResolutionCapable flag to Info.plist for better font
  rendering on Retina displays.
- OS X: Fix bitcoin-qt startup crash when clicking dock icon
- Linux: Fix Gnome bitcoin: URI handler

Miscellaneous:

- Add Linux script (contrib/qos/tc.sh) to limit outgoing bandwidth
- Add '-regtest' mode, similar to testnet but private with instant block
  generation with 'setgenerate' RPC.
- Add 'linearize.py' script to contrib, for creating bootstrap.dat
- Add separate bitcoin-cli client

Credits
--------

Thanks to everyone who contributed to this release:

- Andrey
- Ashley Holman
- b6393ce9-d324-4fe1-996b-acf82dbc3d53
- bitsofproof
- Brandon Dahler
- Calvin Tam
- Christian Decker
- Christian von Roques
- Christopher Latham
- Chuck
- coblee
- constantined
- Cory Fields
- Cozz Lovan
- daniel
- Daniel Larimer
- David Hill
- Dmitry Smirnov
- Drak
- Eric Lombrozo
- fanquake
- fcicq
- Florin
- frewil
- Gavin Andresen
- Gregory Maxwell
- gubatron
- Guillermo Céspedes Tabárez
- Haakon Nilsen
- HaltingState
- Han Lin Yap
- harry
- Ian Kelling
- Jeff Garzik
- Johnathan Corgan
- Jonas Schnelli
- Josh Lehan
- Josh Triplett
- Julian Langschaedel
- Kangmo
- Lake Denman
- Luke Dashjr
- Mark Friedenbach
- Matt Corallo
- Michael Bauer
- Michael Ford
- Michagogo
- Midnight Magic
- Mike Hearn
- Nils Schneider
- Noel Tiernan
- Olivier Langlois
- patrick s
- Patrick Strateman
- paveljanik
- Peter Todd
- phantomcircuit
- phelixbtc
- Philip Kaufmann
- Pieter Wuille
- Rav3nPL
- R E Broadley
- regergregregerrge
- Robert Backhaus
- Roman Mindalev
- Rune K. Svendsen
- Ryan Niebur
- Scott Ellis
- Scott Willeke
- Sergey Kazenyuk
- Shawn Wilkinson
- Sined
- sje
- Subo1978
- super3
- Tamas Blummer
- theuni
- Thomas Holenstein
- Timon Rapp
- Timothy Stranex
- Tom Geller
- Torstein Husebø
- Vaclav Vobornik
- vhf / victor felder
- Vinnie Falco
- Warren Togami
- Wil Bown
- Wladimir J. van der Laan

[1714123767]

1714123767

[1714123767]

1714123767

[Hamuki]

FIRST!! lol..

Nice with a update!

Great job!

[xiaoma9hao]

Great job!

[alch1mista]

Great job! Thanks

[jubalix]

see that list of dev's

and the quality of the dev...= near bitcoins biggest asset.....

[deliciousowl]

good news is good news

[h00395]

Very cool!!!

[vlaoou321]

 ;)thx

[ripper234]

Kudos for the terrific work you are doing!

[ganabb]

Double spend handling in the wallet was improved?

[pbj sammich]

Great Job all!

[Skinnkavaj]

Finally.

[Liquid]

Thank you 

[KSV]

a huge thanks guys!

[Chalkbot]

Thanks for all your hard work.

[pr9me]

Niceshwan!

[natoshisakamoto]

Just posted it to Rap Genius, in case people would like to help annotate it and help translate some of the more complicated technical points into plain English...

http://rapgenius.com/The-bitcoin-dev-team-bitcoin-090-final-lyrics

[contro]

Thank you, i will try it out, i hope i doesnt lagg my latop so much

[Kazimir]

You guys are heroes.

[virtuexru]

Thanks for all your hard work.

I second this notion.

[Massimo80]

There are some quirks in the Italian translation (and some text which hasn't even been translated).

Where can I report them?

[btcdrak]

On the Mac build at least, the "pre-release build" banner is showing. Seems like that flag was not turned off?

[Buffer Overflow]

Keep up the good work.

[chriswilmer]

AWESOME!!!

[Buziss]

The win64 version is missing on this page. https://bitcoin.org/en/download

[jgarzik]

A note on OP_RETURN and data storage in the block chain was added to the release notes:
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.9.0.md

[tinus42]

Just installed it and it's running as a full node now.

[Luke-Jr]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

Edit: Correction: By default, IPs are only logged when a node connects. This is still a potential concern, but was introduced in 0.7.0, not 0.9.0.

[SeaofBTC]

Great job to all devs, that's a large list of teamwork. The community will never be able to thank you all enough for your work.

[emzone]

That's great news! The most serous problem - the transaction malleability bug is now resolved!

[phelix]

Awesome! I have a feeling this release is quite mature. +1 for Coin Control

[btcdrak]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

Is that on by default? I thought IP logging was only enabled if explicitly enabled.

[Luke-Jr]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

Is that on by default? I thought IP logging was only enabled if explicitly enabled.

It is always on and cannot be disabled in this release.

[Saicere]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).

./bitcoind -daemon
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)

Supported versions are:

GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBC_2.2.5
GLIBC_2.3
GLIBC_2.4
GLIBC_2.3.2

[Luke-Jr]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

Is that on by default? I thought IP logging was only enabled if explicitly enabled.

It is always on and cannot be disabled in this release.

I must have missed that. But wasn't there talk of adding ability to control that? Maybe not merged yet?

Not merged yet.

[btcdrak]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

Is that on by default? I thought IP logging was only enabled if explicitly enabled.

It is always on and cannot be disabled in this release.

Ah yes, there is a pending PRs for this https://github.com/bitcoin/bitcoin/pull/3764

[mgroenouwe]

Big thanks to all devzz!

[knight22]

Awesome! 

[Lauda]

Someone should perhaps make note of a security regression in 0.9.0:
IP addresses of your peers are now logged, making your debug.log file valuable to crackers and/or governments.

This is definitely a issue for me. I'll test the version which doesn't include this.

[Luke-Jr]

Correction: By default, IPs are only logged when a node connects. This is still a potential concern, but was introduced in 0.7.0, not 0.9.0.

[gigantic]

what is the easiest way to upgrade bitcoin-qt on ubuntu to this version?

[giszmo]

Epic release is epic

[rme]

457 online full nodes are running Bitcoin 0.9.0

Source:
http://getaddr.bitnodes.io/nodes/1395255600/?q=%2FSatoshi%3A0.9.0%2F

[klabaki]

Thanks a lot!





Does anyone know what this means?

0.9.0 Release notes
=======================

Protocol and network:

- Dump addresses every 15 minutes instead of 10 seconds

It's not clear whether it refers to IP addresses or Bitcoin addresses? Please explain.

[mmitech]

am I the only one having problems with linux ? I cant even open the Bin, my system doesn't know which application to use to open the files !!! first time happens to me.

Also I am trying the ubuntu PPA but I am getting the older version instead of v0.9 !!


Edit: Armory did handle that file extension, but I cant get Bitcoin GUI to open...

[Radar]

Yes, finally a new Bitcoin wallet! ^__^!!!

[jgarzik]

For new users downloading the chain for the first time...

Please torrent the chain.

[dishwara]

Do need to uninstall 32 bit version, before installing 64 bit version?
Also, can have both 32 & 64 bit version in a same pc accessing same wallet?

[Massimo80]

Also, can have both 32 & 64 bit version in a same pc accessing same wallet?

Yes (the wallet and blockchain db are identical), but not at the same time, because the files would be locked by the first one launched.

But why would you want to run both versions? It's the exact same program, just compiled for a different CPU architecture.

[drrussellshane]

So far I like it and am enjoying the new features!

[isimme]

Mac OS X version, at least via the og post link, is beta not final..

[mmeijeri]

If I uninstall the old version, do I have to backup the blockchain or will the uninstaller leave it on disk? Same question for wallet.dat. Of course, I've already backed up wallet.dat, but it would be nice to know.

[ErnieRox]

Good Job Guys, Thanx!! 

[wumpus]

If I uninstall the old version, do I have to backup the blockchain or will the uninstaller leave it on disk? Same question for wallet.dat. Of course, I've already backed up wallet.dat, but it would be nice to know.

Uninstall does not touch your data files. It just uninstalls the software. Which is all that is needed.

No need to mess with your data files at all (though backing up the wallet is a good idea always)

Do need to uninstall 32 bit version, before installing 64 bit version?

You don't *need* to, but it's recommended just in case to avoid issues.

Also, can have both 32 & 64 bit version in a same pc accessing same wallet?

Sure, as long as they're not running at the same time.

Also I am trying the ubuntu PPA but I am getting the older version instead of v0.9 !!

Then you need to wait for the PPA to be updated. It's updated seperately.

[Luke-Jr]

+1 to always keeping an up-to-date backup of your wallet!

[jgarzik]

Here is a quick overview of the release: http://garzikrants.blogspot.com/2014/03/bitcore-core-v090-release-overview.html

[David M]

Upgrade on Windows 7 32bit was fine.

I love the Network traffic graph and coin control.

Kudos to all the contributors.

[Gavin Andresen]

On the Mac build at least, the "pre-release build" banner is showing. Seems like that flag was not turned off?

This was a release process bug; I re-built/signed/uploaded the OSX .dmg to fix it (and updated the SHASUMS files).

The warning is harmless, and no code was changed, so if you don't want to re-download and install you don't have to.

Thanks to lots of hard work from Luke Dashjr and Cory Fields we should (fingers crossed!) have deterministic OSX builds working before the next release, which will make this kind of error impossible.

[isimme]

On the Mac build at least, the "pre-release build" banner is showing. Seems like that flag was not turned off?

This was a release process bug; I re-built/signed/uploaded the OSX .dmg to fix it (and updated the SHASUMS files).

The warning is harmless, and no code was changed, so if you don't want to re-download and install you don't have to.

Thanks to lots of hard work from Luke Dashjr and Cory Fields we should (fingers crossed!) have deterministic OSX builds working before the next release, which will make this kind of error impossible.

Awesome, Thanks everyone!

[Ente]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).

./bitcoind -daemon
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)

Supported versions are:

GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBC_2.2.5
GLIBC_2.3
GLIBC_2.4
GLIBC_2.3.2

Same problem on (stock) Debian.
Bitcoin core doesn't run out-of-the-box:

Code:

/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/bitcoin/bin/64/bitcoind)
/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/bitcoin/bin/64/bitcoind)

Does it run on *any* linux distro?

Ente

[chriswilmer]

It runs fine on Ubuntu 12.04 (I didn't use the PPA, I just downloaded the binary and ran it)

[nobbynobbynoob]

Installed today. It looks good, just have to get used to the slightly different interface, especially under Receive.

Great work as always, devs!

[Ente]

I pulled the git, installed "automake", now it complains

Code:

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing

..although I have "libdb-dev" installed.

Any hints?

Ente

[dserrano5]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).

./bitcoind -daemon
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)

Same problem on (stock) Debian.
Bitcoin core doesn't run out-of-the-box:

Code:

/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/bitcoin/bin/64/bitcoind)
/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/bitcoin/bin/64/bitcoind)

Does it run on *any* linux distro?

Ente

This has already been discussed before: https://bitcointalk.org/index.php?topic=495683.msg5523984#msg5523984

[mmitech]

I pulled the git, installed "automake", now it complains

Code:

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing

..although I have "libdb-dev" installed.

Any hints?

Ente

I had the same problem, didn't want to play around it, tried Armory, just out of curiosity, Armory started Bitcoind without any problem, although I didn't try to do anything else(yet)...

[mmeijeri]

Top of the page still says "News: Bitcoin Core 0.8.6 is now available. Download."

[Cornelius]

Very nice collective work! Thanks! 

[bbulker]

Great job everyone, thank you.

[520Bit]

An Open Letter and Plea to the Bitcoin Core Development Team： https://www.counterparty.co/plea-bitcoin-core-development-team/

[teukon]

A big thanks to the Core Devs for all their hard work.  This is a terrific release!

Same problem on (stock) Debian.
Bitcoin core doesn't run out-of-the-box:

Code:

/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/bitcoin/bin/64/bitcoind)
/opt/bitcoin/bin/64/bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/bitcoin/bin/64/bitcoind)

Yeah, that was slightly annoying.  Debian Stable uses glibc 2.13 (which was enough for the Linux build of Bitcoin 0.8.6).  Maybe this is a sign that I should be joining the ranks of those that build from source each time.

For now, I'll just use the more recent version of glibc available in Testing.  Here's a quick guide for anyone wanting to do the same:

Add:

Code:

deb http://http.debian.net/debian/ testing main
deb-src http://http.debian.net/debian/ testing main

to /etc/apt/sources.list.

Add:

Code:

APT::Default-Release "stable";

to /etc/apt/apt.conf.d/70debconf.

Run:

Code:

apt-get update
apt-get -t testing install libc6

[Luke-Jr]

An Open Letter and Plea to the Bitcoin Core Development Team： https://www.counterparty.co/plea-bitcoin-core-development-team/

Your threat to abuse multisig is no different than a thief telling his victim "leave your windows open for me or I'll break them".
Even in the rare cases where some data storage is needed, 40 bytes is more than enough for reasonable uses.
The only arguments for more, always come down to "we want to force people to store our data against their will".
Stop abusing Bitcoin. Thanks.

[bbulker]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).
...

This is keeping me from updating my full node.

[anton000]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).
...

This is keeping me from updating my full node.

same. as expecting it to run out of the box with centos 6.5. will try to build on a different box. can risk building on a production server. sigh

[Newar]

Does it run on *any* linux distro?

Ente

No joy on Fedora 20 here 

[jonathan]

Debian Wheezy 7.4 here:

$ ./bitcoind
bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by bitcoind)

Wheezy uses 2.13 ==> https://packages.debian.org/wheezy/libc6

So I'll have to stick with 0.8.6 for the time being. I trust I'm not hurting the network if I do that, right?

[Newar]

Also, no joy in Lubuntu. It shows what should be executables as shared libraries and doesn't know what to do with them.

The PPA is at 0.8.6.

[sgravina]

Bug:

MacOS 10.9.2
Under the send tab.  The number in the Amount box changes by itself.  I tried to force this to happen but I couldn't.  It did happen though.  I typed in 2.2 and it kept changing to different values like 2.199, 2.203, etc without me doing anything.

Also,
The 'esc' key erases all send fields.  Not expected behavior.

[wtogami]

FYI, the linux binary doesn't run out of the box on CentOS 6 (6.5 fully updated).

./bitcoind -daemon
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)

EDIT:
I made gitian builds of 0.9.0 that should work on the same operating systems as the 0.8.6 builds.  However the builds in https://github.com/bitcoin/bitcoin/pull/3914 might eventually be better if it becomes an official fix.

[Icon]

question: is the 1 time use btc address per transaction active now in the new 0.9 client?

thanks

Icon

[Serge]

are there any no longer used data files at %appdata%/bitcoin that are safe to get rid off for the sake of extra disk space? 

i think i'm seeing 2 blockchains in mine, one in folder 'blocks' that is current and an older chain at the root of %appdata%/bitcoin that stopped updating over a year ago, around 6 gigs. is it safe to dump it?

[iongchun]

There are some quirks in the Italian translation (and some text which hasn't even been translated).

Where can I report them?

The translations in 0.9.0 release is not the latest on Transifex.
I don't understand why the release team don't pull the latest into the release,
especially some strings are just replaced/updated several weeks before the release.
It annoys me as a translator because it happens several times, and I see half-baked translations in a release.
It could be better that the release schedule includes a period to call for translations,
so developers have a deadline to update strings to be localized,
and translators have a deadline to finish their work.

[Maged]

are there any no longer used data files at %appdata%/bitcoin that are safe to get rid off for the sake of extra disk space? 

i think i'm seeing 2 blockchains in mine, one in folder 'blocks' that is current and an older chain at the root of %appdata%/bitcoin that stopped updating over a year ago, around 6 gigs. is it safe to dump it?

Yes, you can get rid of that one, but it's just a hard link to a file in the blocks folder, so deleting it doesn't actually free up any space.

[5thStreetResearch]

Nice work, thanks and keep it up!

[Equate]

Thank you

[whatcoinorg]

Thank you for your hard work.

[r3wt]

give us back the address pages.

[dewdeded]

I pulled the git, installed "automake", now it complains

Code:

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing

..although I have "libdb-dev" installed.

Any hints?

Ente

locate db_cxx.h

then you have different options:

a) fixing directories with symlinks, so configure finds it within the default dirs (/usr/lib and /usr/include)
b) using ./configure flags or BASH settings to specifiy where libs are searched/found
(e.g. something like ./configure BDB_LIBS=/usr/local/db48/lib BDB_CPPFLAGS=-I/usr/local/db48/include)

[Vort]

give us back the address pages.

This pages are hidden within File menu

[Ente]

I pulled the git, installed "automake", now it complains

Code:

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing

..although I have "libdb-dev" installed.

Any hints?

Ente

locate db_cxx.h

then you have different options:

a) fixing directories with symlinks, so configure finds it within the default dirs (/usr/lib and /usr/include)
b) using ./configure flags or BASH settings to specifiy where libs are searched/found
(e.g. something like ./configure BDB_LIBS=/usr/local/db48/lib BDB_CPPFLAGS=-I/usr/local/db48/include)

Thanks pal. It turned out I need "libdb++-dev" instead of "libdb-dev".

One step closer now, next roadblock:

Code:

checking for Berkeley DB C++ headers... default
configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore)

There is only v5.1 available on Debian

edit: recompiling with "--with-incompatible-bdb"

Ente

[dewdeded]

Second one is known and https://github.com/bitcoin/bitcoin/issues/3686 .

[Ente]

Second one is known and https://github.com/bitcoin/bitcoin/issues/3686 .

Thanks again for your help.

In the meantime I compiled with:

Code:

aptitude install automake libdb++-dev libboost-dev
aptitude install libboost-{system,filesystem,chrono,program-options,thread,test}-dev

./autogen.sh
./configure --with-incompatible-bdb 
make

Works on Debian.
Take care that your wallet files may be incompatible to other bitcoin-core installations because of the different berkeley db version. Which is no issue for me.

Ente

[Gummo]

I've installed 0.9 on ubuntu 13.10 (copied the files in the archive to /usr/bin)

It's working fine. Though I thought the transaction fee's were lowered to 0.00001 btc. It's the same 0.0001 as before. Did I do something wrong?

[alexeft]

Hey guys, the linux version doesn't work on centos 6.5 x64. It requires newer version of glibc
I compiled a static version of bitcoind, but still get the same message.

Message is:
--------------------------------
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)
---------------------------------

Can this be fixed in anyway?

Thanks!

[r3wt]

give us back the address pages.

This pages are hidden within File menu

ah thanks. i'm happy now. little confused by the request payment feature, but the improvements are nice to say the least.

[wumpus]

Hey guys, the linux version doesn't work on centos 6.5 x64. It requires newer version of glibc
I compiled a static version of bitcoind, but still get the same message.

Message is:
--------------------------------
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)
---------------------------------

Can this be fixed in anyway?

Thanks!

This is a known issue.
Can you try the static builds here  https://github.com/bitcoin/bitcoin/pull/3914 ?

[alexeft]

Hey guys, the linux version doesn't work on centos 6.5 x64. It requires newer version of glibc
I compiled a static version of bitcoind, but still get the same message.

Message is:
--------------------------------
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./bitcoind)
./bitcoind: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./bitcoind)
---------------------------------

Can this be fixed in anyway?

Thanks!

This is a known issue.
Can you try the static builds here  https://github.com/bitcoin/bitcoin/pull/3914 ?

It works!

Thanks

[rmines]

Successfully upgraded to 0.9.0
I like the new receive window and the lowered tx fees, good work devs!

[davidpbrown]

what is the easiest way to upgrade bitcoin-qt on ubuntu to this version?

I'm on Mint but expect it's the same for you. I couldn't just double run the bitcoin-qt as I coudl with 0.8.6 but it runs when started from the command line.
So, cd ~/bitcoin-0.9.0-linux/bin/32 and ./bitcoin-qt &

[btcpay86]

It's nice.

[rallasnackbar]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

[dave3]

File --> Sending Addresses...
File --> Receiving Addresses...

[rallasnackbar]

File --> Sending Addresses...
File --> Receiving Addresses...

Too late, already uninstalled that crap, and back to 0.8.6

Why the hell do devs have to change something that is fine.

[Scarecrow]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

I was just about to do this upgrade, what exactly is the problem you're referring to?

[rallasnackbar]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

I was just about to do this upgrade, what exactly is the problem you're referring to?

The receive list as we know it is fucked. This is what it used to look like https://bitbargain.co.uk/s/img/sign_message.png

The new one looks like you have to fill out a note from grandma evertime you want to receive coins,.

[Scarecrow]

Thanks for the heads up.

I'll hold back and await further developments.

[CaptEmulation]

Great release!  I've been using the RC and appreciate the features separating the wallet from the server (network).  Send TX new UI was also needed.  Also getbestblockhash is a small time saver.

Edit: Well as pointed above, some problems with UI.  I was mostly focusing on bitcoind in my evaluation.

[GrapeApe]

what is the easiest way to upgrade bitcoin-qt on ubuntu to this version?

I'm on Mint but expect it's the same for you. I couldn't just double run the bitcoin-qt as I coudl with 0.8.6 but it runs when started from the command line.
So, cd ~/bitcoin-0.9.0-linux/bin/32 and ./bitcoin-qt &

Wow thanks I have been pulling my hair out here. To think that simple solution was probably there for me the whole time. Why is my Ubuntu 12.04 trying to use gedit to open the executable? The icons for them is the paper one and gedit is set as default to open them. What is different to make Ubuntu not recognize them as executables?

[alexeft]

what is the easiest way to upgrade bitcoin-qt on ubuntu to this version?

I'm on Mint but expect it's the same for you. I couldn't just double run the bitcoin-qt as I coudl with 0.8.6 but it runs when started from the command line.
So, cd ~/bitcoin-0.9.0-linux/bin/32 and ./bitcoin-qt &

Wow thanks I have been pulling my hair out here. To think that simple solution was probably there for me the whole time. Why is my Ubuntu 12.04 trying to use gedit to open the executable? The icons for them is the paper one and gedit is set as default to open them. What is different to make Ubuntu not recognize them as executables?

The file does not have the "executable" permission probably. Right click on it and add the permission.

[crazy987]

Great!

[Serge]

are there any no longer used data files at %appdata%/bitcoin that are safe to get rid off for the sake of extra disk space?  

i think i'm seeing 2 blockchains in mine, one in folder 'blocks' that is current and an older chain at the root of %appdata%/bitcoin that stopped updating over a year ago, around 6 gigs. is it safe to dump it?

Yes, you can get rid of that one, but it's just a hard link to a file in the blocks folder, so deleting it doesn't actually free up any space.

thanks. although i'm not sure that's the case with hard linking.
split files in blocks folder are 131MB  while at the root only one of them 131MB and other 4 files vary between 1-2gigs

i think that's the old chain format back from 2011-12 that isn't being used as back few client version updates the blockchain i believe was rebuilt to a new format

[alphateam]

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

[GrapeApe]

what is the easiest way to upgrade bitcoin-qt on ubuntu to this version?

I'm on Mint but expect it's the same for you. I couldn't just double run the bitcoin-qt as I coudl with 0.8.6 but it runs when started from the command line.
So, cd ~/bitcoin-0.9.0-linux/bin/32 and ./bitcoin-qt &

Wow thanks I have been pulling my hair out here. To think that simple solution was probably there for me the whole time. Why is my Ubuntu 12.04 trying to use gedit to open the executable? The icons for them is the paper one and gedit is set as default to open them. What is different to make Ubuntu not recognize them as executables?

The file does not have the "executable" permission probably. Right click on it and add the permission.

Uuhh yeah thanks... It's checked, but for some reason gedit is set as default application to open it with and if I remove it as default app Ubuntu doesn’t know what to do with it. It's no big deal I was just curious why Ubuntu isn't recognizing it as an executable. All of the binaries in the bin directory are doing this...

[wumpus]

Uuhh yeah thanks... It's checked, but for some reason gedit is set as default application to open it with and if I remove it as default app Ubuntu doesn’t know what to do with it. It's no big deal I was just curious why Ubuntu isn't recognizing it as an executable. All of the binaries in the bin directory are doing this...

It's because we are compiling/linking with -pie. This adds address space randomization, which is a security/hardening feature that makes exploits more difficult. But it means that the executable is seen as a shared library by naive tools such as "file" and seemingly the Gnome file manager.

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

[GrapeApe]

Uuhh yeah thanks... It's checked, but for some reason gedit is set as default application to open it with and if I remove it as default app Ubuntu doesn’t know what to do with it. It's no big deal I was just curious why Ubuntu isn't recognizing it as an executable. All of the binaries in the bin directory are doing this...

It's because we are compiling/linking with -pie. This adds address space randomization, which is a security/hardening feature that makes exploits more difficult. But it means that the executable is seen as a shared library by naive tools such as "file" and seemingly the Gnome file manager.

Yep that explains it perfectly. Thanks to all that responded and a Big Thanks to the devs.

Edit: And yes I am using the Gnome file manager.....

[alphateam]

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

Win 8.1 64bits

[wumpus]

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

Win 8.1 64bits

OK created an issue
https://github.com/bitcoin/bitcoin/issues/3916

[C. Bergmann]

Some stupid questions.
How to uninstall the old client? Just delete the folder and the appdata? Do I have to delete the blocks also?
(btw.: I redirected the block-directory, can someone tell me the command line again?)

[mmeijeri]

Don't delete the data folder (answered earlier in this thread). Especially not your wallet.dat!!! Well, at least not until you're 100% sure you've backed up the latest version properly.

[wumpus]

How to uninstall the old client? Just delete the folder and the appdata? Do I have to delete the blocks also?

Run the uninstaller. If you never ran an installer, you don't need to do anything and you can just remove the old .exe.

Do not remove the data! (blocks and/or wallet) Do make sure that you back up your wallet before upgrading. Although the uninstaller doesn't touch the data, it doesn't hurt to be careful.

[Newar]

Uuhh yeah thanks... It's checked, but for some reason gedit is set as default application to open it with and if I remove it as default app Ubuntu doesn’t know what to do with it. It's no big deal I was just curious why Ubuntu isn't recognizing it as an executable. All of the binaries in the bin directory are doing this...

It's because we are compiling/linking with -pie. This adds address space randomization, which is a security/hardening feature that makes exploits more difficult. But it means that the executable is seen as a shared library by naive tools such as "file" and seemingly the Gnome file manager.

Yep that explains it perfectly. Thanks to all that responded and a Big Thanks to the devs.

Edit: And yes I am using the Gnome file manager.....

It explains it, but how do you execute it? Stumped.

[wumpus]

It explains it, but how do you execute it? Stumped.

Either from the command line, or launch it from an (executable) script.

[GrapeApe]

It explains it, but how do you execute it? Stumped.

Either from the command line, or launch it from an (executable) script.

Open a terminal cd into the directory that bitcoin-qt is in and type "./bitcoin-qt &" without the quotes the & is there to just free it up from the terminal you opened it up with so you can close it out of the way.

[Newar]

It explains it, but how do you execute it? Stumped.

Either from the command line, or launch it from an (executable) script.

Open a terminal cd into the directory that bitcoin-qt is in and type "./bitcoin-qt &" without the quotes the & is there to just free it up from the terminal you opened it up with so you can close it out of the way.

That worked, thank you. Next stumbling block: It seems the data directories for the blocks and wallet have changed? The client starts with 270 weeks back. Where can I set the datadir?

[GrapeApe]

That worked, thank you. Next stumbling block: It seems the data directories for the blocks and wallet have changed? The client starts with 270 weeks back. Where can I set the datadir?

I didn't have to set my directory but this may help as a terminal command option  -datadir=<dir>         Specify data directory

Edit: I don't know if this has anything to do with it but you may have to install Berkley DB 4.8 but others here will know better than me about that. Don't do it based on my advice. I did to avoid the error I was getting when compiling my own.

[C. Bergmann]

How to uninstall the old client? Just delete the folder and the appdata? Do I have to delete the blocks also?

Run the uninstaller. If you never ran an installer, you don't need to do anything and you can just remove the old .exe.

Do not remove the data! (blocks and/or wallet) Do make sure that you back up your wallet before upgrading. Although the uninstaller doesn't touch the data, it doesn't hurt to be careful.

Thank you.
I don't have the option "uninstall".
I have a backup of the wallet.dat

So I just have to delete the old .exe? That's everything?

[C. Bergmann]

I made it, and I think I have it. But ... what happened to the -datadir commandline? I need to redirect bitcoin core on another directory to load the blockchain ...

edit: datadir=<directory> is still in my .conf, but it still has to download all the blocks

[J.Socal]

I was using 0.8.4 before.I uninstalled it using windows uninstaller.restarted comp.Then installed  0.9.0..Its up and running already with all info from previous version.Is this normal?I thought It was suppose to install the blockchain again?

[GrapeApe]

I was using 0.8.4 before.I uninstalled it using windows uninstaller.restarted comp.Then installed  0.9.0..Its up and running already with all info from previous version.Is this normal?I thought It was suppose to install the blockchain again?

Yes that is normal you only need to redownload/reindex the blockchain if you were using 0.7.2 or earlier.

I made it, and I think I have it. But ... what happened to the -datadir commandline? I need to redirect bitcoin core on another directory to load the blockchain ...

edit: datadir=<directory> is still in my .conf, but it still has to download all the blocks

I'm not sure what to tell you and Newar about this I've never had to use the -datadir command. I suppose if your wallet is intact and accessible by QT it could be worse.

Like I said  a few post back installing Berkley DB 4.8 may have something to do with this but you should check with someone smarter than me...

[J.Socal]

Is there a way to delete transaction history?

[Luke-Jr]

Is there a way to delete transaction history?

There is really no good way to do this with Bitcoin.

[J.Socal]

On my wallet I mean..Guess only way is to fully uninstall it and reinstall.

[CanaryInTheMine]

On my wallet I mean..Guess only way is to fully uninstall it and reinstall.

Your transactions are on blockchain.  Your wallet file has your private key/s.  When the client reads a tx on blockchain for which it has a private key, it lists them.  That's what you're asking about?

You can't delete your tx's from blockchain.
You can delete your wallet file and get a new one, but even Satoshi himself said that you should keep your wallets around.

[GrapeApe]

Is there a way to delete transaction history?

Well if you must just move your current wallet.dat file to another directory and start QT when it doesn't find a wallet.dat file it will create a new one then you can make note of the newly created address and switch your old wallet.dat file back in there making sure to make a backup of the new one and not to get things mixed up and screwed up and then send all the coins to the new address. Don't get confused and mix things up you can loose your coins.....

Edit: To echo what Canary said once the transaction is entered into the blockchain it's there forever.

[S4VV4S]

I was using 0.8.4 before.I uninstalled it using windows uninstaller.restarted comp.Then installed  0.9.0..Its up and running already with all info from previous version.Is this normal?I thought It was suppose to install the blockchain again?

Yes that is normal you only need to redownload/reindex the blockchain if you were using 0.7.2 or earlier.

I made it, and I think I have it. But ... what happened to the -datadir commandline? I need to redirect bitcoin core on another directory to load the blockchain ...

edit: datadir=<directory> is still in my .conf, but it still has to download all the blocks

I'm not sure what to tell you and Newar about this I've never had to use the -datadir command. I suppose if your wallet is intact and accessible by QT it could be worse.

Like I said  a few post back installing Berkley DB 4.8 may have something to do with this but you should check with someone smarter than me...

I am guessing you are using windows?
You will need to create a .bat file in your Bitcoin.exe directory and just have a shortcut of that on your desktop or something.

@echo off
bitcoin-qt.exe -datadir=X:\BitCoin

That did the trick for me

[S4VV4S]

OK, I just installed it and it says beta.
So is it the final release or a beta version?

[Luke-Jr]

OK, I just installed it and it says beta.
So is it the final release or a beta version?

Bitcoin as a whole has always been beta/experimental.

[rme]

OK, I just installed it and it says beta.
So is it the final release or a beta version?

This is the final version of Bitcoin 0.9.0 (its not a realase candidate).

All bitcoin realases have been beta since 2009, we will exit beta when Bitcoin reaches 1.0 version.

[S4VV4S]

OK, thank you both for your reply

[Meuh6879]

Is there a way to delete transaction history?

yes and no.

if you want "clear" the transaction history of bitcoin-QT ... you can send sum of bitcoin to your android wallet.
delete wallet.dat
restart bitcoin-QT
encrypt the new wallet
restart bitcoin-QT
test to create a new receive adress (to verifiy the password ...)
and then, tranfer the sum of bitcoin from the android wallet to the bitcoin-QT new wallet.

i do this every month to have no more than 10-15 line in bitcoin-QT.



and no, you can't delete the history in the "blockchain" worldwide bitcoin network.

[S4VV4S]

Is there a way to delete transaction history?

yes and no.

if you want "clear" the transaction history of bitcoin-QT ... you can send sum of bitcoin to your android wallet.
delete wallet.dat
restart bitcoin-QT
encrypt the new wallet
restart bitcoin-QT
test to create a new receive adress (to verifiy the password ...)
and then, tranfer the sum of bitcoin from the android wallet to the bitcoin-QT new wallet.

i do this every month to have no more than 10-15 line in bitcoin-QT.



and no, you can't delete the history in the "blockchain" worldwide bitcoin network.

It would be an interesting new feature.
Just export your transactions in a certain format and then delete the history.

[smoothrunnings]

There is something really different in 0.9.0 over 0.8.6, when I try to run either the 32bit or 64bit bin on my openSUSE 13.1 it refuses it work were as 0.8.6 binaries worked without any issues. (sigh)

Does anyone here use openSUSE?

Thanks

[ChuckBuck]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

I was just about to do this upgrade, what exactly is the problem you're referring to?

The receive list as we know it is fucked. This is what it used to look like https://bitbargain.co.uk/s/img/sign_message.png

The new one looks like you have to fill out a note from grandma evertime you want to receive coins,.

Is there any truth to what this user encountered with receive addresses after upgrading?

Any devs want to chime in on this?

[drrussellshane]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

I was just about to do this upgrade, what exactly is the problem you're referring to?

The receive list as we know it is fucked. This is what it used to look like https://bitbargain.co.uk/s/img/sign_message.png

The new one looks like you have to fill out a note from grandma evertime you want to receive coins,.

Is there any truth to what this user encountered with receive addresses after upgrading?

Any devs want to chime in on this?

The receiving addresses are still there, just in a different place, and that poster freaked out.

In the top left of the Bitcoin Core client, click "File", then "Receiving Addresses..."

[Luke-Jr]

Dont download this, the receive bitcoin address list is missing. And you have to start over.

I was just about to do this upgrade, what exactly is the problem you're referring to?

The receive list as we know it is fucked. This is what it used to look like https://bitbargain.co.uk/s/img/sign_message.png

The new one looks like you have to fill out a note from grandma evertime you want to receive coins,.

Is there any truth to what this user encountered with receive addresses after upgrading?

Any devs want to chime in on this?

The Receive page has been revamped to make it easier to use correctly.
If you're trying to use addresses wrong, it will be slightly less convenient as you go to the menu...

[merv77]

beat me to it guys, yes it is still there in 'file' menu.



and to sign address same place in 'file' menu

[ChuckBuck]

Thanks all, I feel much more at ease.

I'll backup my wallet.dat then give it whirl.

Appreciate all the time and hard work done by the core developers and the community.

[Newar]

That worked, thank you. Next stumbling block: It seems the data directories for the blocks and wallet have changed? The client starts with 270 weeks back. Where can I set the datadir?

I didn't have to set my directory but this may help as a terminal command option  -datadir=<dir>         Specify data directory

Edit: I don't know if this has anything to do with it but you may have to install Berkley DB 4.8 but others here will know better than me about that. Don't do it based on my advice. I did to avoid the error I was getting when compiling my own.

Code:

./bitcoin-qt -datadir=/home/xyz/.bitcoin &

Worked like a charm for me.

As an added bonus there are now several more bitcoins in my wallet. Not sure what happened there, but judging from the time it took to start bitcoin core it must have done a re-scan and found same additional tx. (?)

[CanaryInTheMine]

In this version, you can add a new receive addy without needing to enter wallet's pswd.
I actually liked having to enter pswd when creating a new receive addy before.
What was the reasoning behind this change?

[jsgayo]

Great job! Thanks

[GrapeApe]

That worked, thank you. Next stumbling block: It seems the data directories for the blocks and wallet have changed? The client starts with 270 weeks back. Where can I set the datadir?

I didn't have to set my directory but this may help as a terminal command option  -datadir=<dir>         Specify data directory

Edit: I don't know if this has anything to do with it but you may have to install Berkley DB 4.8 but others here will know better than me about that. Don't do it based on my advice. I did to avoid the error I was getting when compiling my own.

Code:

./bitcoin-qt -datadir=/home/xyz/.bitcoin &

Worked like a charm for me.

As an added bonus there are now several more bitcoins in my wallet. Not sure what happened there, but judging from the time it took to start bitcoin core it must have done a re-scan and found same additional tx. (?)

Hey glad I could help. Not sure what to tell about the extra coins but thanks for the tip.

[pandalion98]

I think I'll just stick to blockchain.info... It's because of block chain size and stuff.

[wumpus]

bitcoin-qt.exe -datadir=X:\BitCoin

That did the trick for me

No need for such wrapper scripts unless you have multiple copies of the block chain around.
Try passing -choosedatadir (once) to set the datadir in the registry.

I think I'll just stick to blockchain.info... It's because of block chain size and stuff.

If you don't use the software, please don't reply here.

[Newar]

bitcoin-qt.exe -datadir=X:\BitCoin

That did the trick for me

No need for such wrapper scripts unless you have multiple copies of the block chain around.
Try passing -choosedatadir (once) to set the datadir in the registry.

Sorted! Thank you!

[alphateam]

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

Win 8.1 64bits

OK created an issue
https://github.com/bitcoin/bitcoin/issues/3916

Thx 

[mmitech]

 One thing I would suggest for devs, while I like the feature of new addresses and change addresses I don't know why cant we make this as an option for advanced users only.

  For example I wanted to teach my parents about how to use Bitcoin, they think that they are Tech savvy, the truth is that my father manage to screw up the PC all the time, he thinks that he is a hardcore computer scientist and end up messing system files all the time. and then he go with a new installation without asking if anyone have important files on the PC, he also offers "help" to his friends...you can only imagine what can happen if they all have Bitcoin-qt.


 I can imagine how can he lose all the bitcoins just by making a transaction and not backing up the wallet, one approach is to introduce these users to Armory, but I think this can be implemented in Bitcoin-qt because usually this is the first software a newbie installs. I've also seen few users asking where their bitcoin went after system re-installation.

 The other kind of users rely on exchanges to save their coins, for them it is easier and less work to do, people are still used to the old fashion system when you leave your funds in a bank and they secure/manage them for you, this goes against some of the concepts of Bitcoin.

I don't know if this was brought up before, but I wish if Devs do look into it. 

[wumpus]

One thing I would suggest for devs, while I like the feature of new addresses and change addresses I don't know why cant we make this as an option for advanced users only.

Please don't recommend bitcoin-qt to non-tech-savvy users! To run it safely, you need enough backup discipline.

Ideally, deterministic wallets would be implemented and only a single backup would be needed at the beginning, but we're really short on developers that have deep enough knowledge about the wallet system and dare making changes to it.

[smoothrunnings]

I had a look at the *nix install notes for bitcoin-qt 0.9.0 and wasn't able to determine what I need to run to make / install bitcoin-qt from the source that I wonder if someone could help me?

I need to compile it under openSUSE 13.1, I currently have 0.8.6 which I downloaded from the software.opensuse.org site, there isn't an update yet, I suspect the people who have compiled 0.8.6 either haven't setup 0.9.0 on their systems or aren't bitcoin mining anymore.

Thanks

[rero2]

nice, thanks for the update bro

[halfawake]

I was using 0.8.4 before.I uninstalled it using windows uninstaller.restarted comp.Then installed  0.9.0..Its up and running already with all info from previous version.Is this normal?I thought It was suppose to install the blockchain again?

Yes that is normal you only need to redownload/reindex the blockchain if you were using 0.7.2 or earlier.

That has NOT been the case for me.  I was using 0.8.6 and I got a message this morning from bitcoin-qt that it's going to have to reindex the entire blockchain.  It's telling me now that it's 51 weeks behind, I'm really not happy about this being necessary.  I'm pretty sure 0.8.6 was the most recent stable version before 0.9.0, which would mean that everyone using Windows 7 is having to reindex. 

Granted, I did not uninstall the old version like this poster did, but it looked like the installer said all I had to do was turn off bitcoin-qt, not uninstalling it completely.  So I followed the directions.

[Meuh6879]

reindexing blockchain ... proove that you have many problem on your HDD.
i have installed the v0.9 on 2 computer (WinXP and Win8) = no indexing, no problem.

but, because of the 400Mo of RAM needed by the default setting of the CACHE (100Mo) ... i have decreased this setting to 10Mo.

[halfawake]

reindexing blockchain ... proove that you have many problem on your HDD.
i have installed the v0.9 on 2 computer (WinXP and Win8) = no indexing, no problem.

I suppose that's possible, it does take longer to boot up than it used to, although it's a 2.5 year old computer, so that's to be expected to some degree.  I did just run disk defragmenter the other day though, and it said my hard drive was only 1% fragmented.  Really the only program that's giving me occasional problems lately is a Firefox and I just figure that's because I have eight addons running, and probably about a thousand bookmarks by now.

Is anyone else having this problem with more recent version of bitcoin-qt?  It's up to 22 weeks behind now, so at the rate it's going, it should finish by the end of the day, so it's not the end of the world, just means the hard drive is getting a lot more activity than normal.

[smoothrunnings]

That worked, thank you. Next stumbling block: It seems the data directories for the blocks and wallet have changed? The client starts with 270 weeks back. Where can I set the datadir?

I didn't have to set my directory but this may help as a terminal command option  -datadir=<dir>         Specify data directory

Edit: I don't know if this has anything to do with it but you may have to install Berkley DB 4.8 but others here will know better than me about that. Don't do it based on my advice. I did to avoid the error I was getting when compiling my own.

Code:

./bitcoin-qt -datadir=/home/xyz/.bitcoin &

Worked like a charm for me.

As an added bonus there are now several more bitcoins in my wallet. Not sure what happened there, but judging from the time it took to start bitcoin core it must have done a re-scan and found same additional tx. (?)

Sorry does this mean that bitcoin-qt 0.9.0 doesn't automatically access the .bitcoin/bitcoin.conf file from the users home folder like 0.8.6 does?

Thanks,

[Radi777]

I was using 0.8.4 before.I uninstalled it using windows uninstaller.restarted comp.Then installed  0.9.0..Its up and running already with all info from previous version.Is this normal?I thought It was suppose to install the blockchain again?

Yes that is normal you only need to redownload/reindex the blockchain if you were using 0.7.2 or earlier.

That has NOT been the case for me.  I was using 0.8.6 and I got a message this morning from bitcoin-qt that it's going to have to reindex the entire blockchain.  It's telling me now that it's 51 weeks behind, I'm really not happy about this being necessary.  I'm pretty sure 0.8.6 was the most recent stable version before 0.9.0, which would mean that everyone using Windows 7 is having to reindex. 

Granted, I did not uninstall the old version like this poster did, but it looked like the installer said all I had to do was turn off bitcoin-qt, not uninstalling it completely.  So I followed the directions.

I have Windows 7...no problems here.
I turned it off, uninstalled it and then installed the new one...no problems, didn't index anything, it didn't even need to sync because I was already up to date on the 0.8.6.

[z0rr0]

It takes 18Gb already, am I right that to move data folder from C:\Users\User\AppData\Roaming to another disc or location I should add bitcoin-qt.exe -datadir=D:\ to a shortcut for example (on Win7)?
Thanks.

[arfeniel]

it seems that the new wallet not like folder with é or è 
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

Win 8.1 64bits

OK created an issue
https://github.com/bitcoin/bitcoin/issues/3916

I got the same issue but I'm on Windows 7 SP1 64bits.

[wumpus]

Sorry does this mean that bitcoin-qt 0.9.0 doesn't automatically access the .bitcoin/bitcoin.conf file from the users home folder like 0.8.6 does?

It does, but it doesn't parse -datadir specified in the configuration file currently (see issue https://github.com/bitcoin/bitcoin/issues/3905).

The recommended way to use another data directory is to use -choosedatadir, which will store the data directory in the registry.

[DubFX]

Downloading...will put on feedback.

[teukon]

It takes 18Gb already, am I right that to move data folder from C:\Users\User\AppData\Roaming to another disc or location I should add bitcoin-qt.exe -datadir=D:\ to a shortcut for example (on Win7)?
Thanks.

No need for such wrapper scripts unless you have multiple copies of the block chain around.
Try passing -choosedatadir (once) to set the datadir in the registry.

[hensi]

whats the benefit of v0.9.0? n do blockchain.info users need to do anything?

[wumpus]

it seems that the new wallet not like folder with é or è  
I have an é in my folder name, and unable to install the file of the first launch on it. Other folders no problem

Seems a problem with UTF8 in file names. Strange. What OS?

Win 8.1 64bits

OK created an issue
https://github.com/bitcoin/bitcoin/issues/3916

I got the same issue but I'm on Windows 7 SP1 64bits.

@alphateam, arfeniel:
Can anyone suffering from the 'datadir cannot contain special characters' (when choosing datadir through GUI) problem help testing: https://github.com/bitcoin/bitcoin/pull/3935 ? A test build is available.

[Tjopper]

whats the benefit of v0.9.0? n do blockchain.info users need to do anything?

NO, your bitcoin installation is being handled by blockchain.info. However you should be running your own software.

[dserrano5]

I'm unable to configure 0.9.0:

Code:

$ ./configure --with-incompatible-bdb --without-gui
[…]
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... no
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
configure: error: No working boost sleep implementation found. If on ubuntu 13.10 with libboost1.54-all-dev remove libboost.1.54-all-dev and use libboost1.53-all-dev

This seemed to be a problem in MacOS last year according to my searches, however I'm in linux amd64 so I'm not sure whether I'm finding the same problem or not. This is Debian wheezy, with boost 1.49. I'm working with bitcoin 0.9.0 as downloaded from https://github.com/bitcoin/bitcoin/archive/v0.9.0.tar.gz. config.log is here.

[Meuh6879]

whats the benefit of v0.9.0 ?

READ CHANGELOG ...  
i do this BEFORE installing anything.

you is in a BITCOIN-QT thread.

[chek2fire]

We will see an official ubuntu package from ppa? I see this ppa adress that has the previous version of bticoin-qt


https://launchpad.net/~bitcoin/+archive/bitcoin

[pdawg]

Does Armory play nice with this version?

[wumpus]

This seemed to be a problem in MacOS last year according to my searches, however I'm in linux amd64 so I'm not sure whether I'm finding the same problem or not. This is Debian wheezy, with boost 1.49. I'm working with bitcoin 0.9.0 as downloaded from https://github.com/bitcoin/bitcoin/archive/v0.9.0.tar.gz. config.log is

Main problem from config.log is:

Code:

/usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant

That line is probably:

Code:

    TIME_UTC=1,

This causes a symbol collision in some environments with a libc++ macro.
Later boost versions changed this to TIME_UTC_.

I'm not sure what the proper way to resolve this is, apart from upgrading boost.

In any case this is a boost issue, it also appears on Google various places outside the context of building bitcoin. There are some workarounds:
- https://bbs.archlinux.org/viewtopic.php?id=144593
- https://stackoverflow.com/questions/17599377/boost-error-trouble-compiling-xtime-hpp
- https://svn.boost.org/trac/boost/ticket/6940

[P_Shep]

The RC2 installed no problem, but on installing this release, Norton 360 threw this up:

Filename: uninstall.exe
Threat name: Suspicious.Cloud.9
Full Path: c:\program files\bitcoin\uninstall.exe

____________________________



Details
Unknown Community Usage,  Unknown Age,  Risk High





Origin
Downloaded from
 Unknown





Activity
Actions performed: Actions performed: 1



____________________________



On computers as of 
Not Available


Last Used 
3/23/2014 at 12:23:57 PM


Startup Item 
No


Launched 
No


____________________________


Unknown
It is unknown how many users in the Norton Community have used this file.

Unknown
This file release is currently not known.

High
This file risk is high.

Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.



____________________________



Source: External Media



____________________________

File Actions

File: c:\program files\bitcoin\ uninstall.exe Removed
____________________________


File Thumbprint - SHA:
f7ffc4002439c6f304e39704942a25b0d38588f22f64ea22117664b192d30f6b
File Thumbprint - MD5:
Not available

[dserrano5]

Main problem from config.log is:

Code:

/usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant

That line is probably:

Code:

    TIME_UTC=1,

This causes a symbol collision in some environments with a libc++ macro.
Later boost versions changed this to TIME_UTC_.

Thank you. Temporarily editing xtime.hpp as suggested in your first link did the trick for me.

[Tjopper]

Does Armory play nice with this version?

It plays nice if I put it in your words, however you need to change the installation dir manually because its not recognised because of the name change

[Tjopper]

The RC2 installed no problem, but on installing this release, Norton 360 threw this up:

Filename: uninstall.exe
Threat name: Suspicious.Cloud.9
Full Path: c:\program files\bitcoin\uninstall.exe

____________________________



Details
Unknown Community Usage,  Unknown Age,  Risk High





Origin
Downloaded from
 Unknown





Activity
Actions performed: Actions performed: 1



____________________________



On computers as of 
Not Available


Last Used 
3/23/2014 at 12:23:57 PM


Startup Item 
No


Launched 
No


____________________________


Unknown
It is unknown how many users in the Norton Community have used this file.

Unknown
This file release is currently not known.

High
This file risk is high.

Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.



____________________________



Source: External Media



____________________________

File Actions

File: c:\program files\bitcoin\ uninstall.exe Removed
____________________________


File Thumbprint - SHA:
f7ffc4002439c6f304e39704942a25b0d38588f22f64ea22117664b192d30f6b
File Thumbprint - MD5:
Not available

Correct this is probably a WS.Reputation error ?
Thats pretty common with new realeases or new coins, because they were never used before

Always check what the "virus" is and google it. If you got it from the offcial location it is probably ok

[Meuh6879]

what is the problem

Suspicious.Cloud.9

It's simply the "security product" that it can't recognize the "technical network tool" that you have installed.
Not a very surprise for this branch ... 

even a P2P file sharing software is view as a suspicious network tool ...  even a "viewer software for imagingé is recognize wrongly by a free antiviral tool.




ONLY THINKING ... and use the EXCLUSION on your antivirus (or change it...)

[crazy987]

Seems to me that every time i make a payment when i still have 1 inbound transfer with less then 6 confirms.
It throws my balance back to pending.

anyone else having this issue?

[5ick3uffalo]

Hi,

I´m running QT v0.8.6-beta Client and want upgrade.

 In the description it says just uninstall older version  and install new version

How does it work? Without backup up anything (wallet.dat?)

[DeathAndTaxes]

Hi,

I´m running QT v0.8.6-beta Client and want upgrade.

 In the description it says just uninstall older version  and install new version

How does it work? Without backup up anything (wallet.dat?)

The uninstall and install does not remove or modify the existing wallet.dat.

However you should ALWAYS have an up to date backup (this is money we are talking about).  This is especially true when upgrading, installing, uninstalling, etc.

Make periodic backups even when you aren't upgrading.

[chek2fire]

Today to ubuntu ppa we have the last version of bitcoin-qt

https://launchpad.net/~bitcoin/+archive/bitcoin

if someone with ubuntu want to upgrade he just need to add the ppa address to his system repositories

[lateblooming]

Starting the client takes waaaay more time than before...is it just me or is it normal to wait 40-60 minutes till u can see the client?

[durrrr]

Starting the client takes waaaay more time than before...is it just me or is it normal to wait 40-60 minutes till u can see the client?

my client also takes a very long time to start. I actually questioned it at first but then it popped up and my wallet was good to go

[DeathAndTaxes]

Starting the client takes waaaay more time than before...is it just me or is it normal to wait 40-60 minutes till u can see the client?

Take a look at the debug.log.  No it isn't normal.  It may have been a one time reindexing.  If it happens each time then likely there is a problem where the db is getting corrupted and rebuilt every time you run the client.

[Jr.peng]

thanks for the updates

[lateblooming]

Starting the client takes waaaay more time than before...is it just me or is it normal to wait 40-60 minutes till u can see the client?

Take a look at the debug.log.  No it isn't normal.  It may have been a one time reindexing.  If it happens each time then likely there is a problem where the db is getting corrupted and rebuilt every time you run the client.

Thanks for the Hint! I will have a look!

[davispuh]

I totally love Bitcoin Core 0.9.0 it's just so awesome!!!
Especially I really like Coin Control as that's what I've been wishing for a while.

Congrats to all devs and everyone who helped developing it. And I can't wait what next version will bring!

[wumpus]

Seems to me that every time i make a payment when i still have 1 inbound transfer with less then 6 confirms.
It throws my balance back to pending.

anyone else having this issue?

[snip]

Did you perhaps disable the "Spend unconfirmed change" option?

[xiaohuolv]

Double spend handling in the wallet was improved?

[Tammy Chan]

Double spend handling in the wallet was improved?

If you are talking about the issue "transaction malleability", the new version handle it better.

Transaction malleability-related fixes
--------------------------------------

This release contains a few fixes for transaction ID (TXID) malleability
issues:

- -nospendzeroconfchange command-line option, to avoid spending
  zero-confirmation change
- IsStandard() transaction rules tightened to prevent relaying and mining of
  mutated transactions
- Additional information in listtransactions/gettransaction output to
  report wallet transactions that conflict with each other because
  they spend the same outputs.
- Bug fixes to the getbalance/listaccounts RPC commands, which would report
  incorrect balances for double-spent (or mutated) transactions.
- New option: -zapwallettxes to rebuild the wallet's transaction information

[Velkro]

happy with release, but kinda buggy
important is that there is progress

[Meuh6879]

Starting the client takes waaaay more time than before...is it just me or is it normal to wait 40-60 minutes till u can see the client?

decrease cache to 10Mo (instead of 100Mo).

[CryptoCurrencyInc.com]

When it saids: Bitcoin 0.9 FINAL
does it mean there won't be any more update to the wallet?

[merv77]

When it saids: Bitcoin 0.9 FINAL
does it mean there won't be any more update to the wallet?

this would mean final for version 0.9.0, and next update will become version 0.9.1

[Jovan97]

Need too much time to sync whit network.. 

[btcpay86]

Ok, I have installed it, but how to refer to the data path? such as "D:\Coins\Bitcoin". When i installed it, i did not see this option. It was been installed in Disk C.

[marcus_of_augustus]

The doc/build-unix.md instructions say:

To Build
---------------------

        ./autogen.sh
        ./configure
        make

yet the supplied tarball for linux (https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-linux.tar.gz)has no autogen.sh script supplied in src.

Is it expected to generate that script locally (which would be unorthodox)? But if so it should say so in the documentation.

[David M]

Ok, I have installed it, but how to refer to the data path? such as "D:\Coins\Bitcoin". When i installed it, i did not see this option. It was been installed in Disk C.

What OS?

I'll take a punt and say windows...

1) Right-Click the Bitcoin Icon from the desktop and select "Properties"
2) In the "Shortcut" tab look for the "Target" field.  It should say something like "C:\Program Files\Bitcoin\bitcoin-qt.exe"
3) Edit this field and after the last quote add the following: -datadir=D:\Coins\Bitcoin

The target should now look like this:

"C:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir=D:\Coins\Bitcoin

NB:  Notice the quotes

4) Press OK.

There are a whole bunch of switches (arguments) that can be used.
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments

[MysteryMiner]

Uninstalled 0.8.6 and installed 0.9.0 without any problems at all. Windows XP Professional SP3

I think the requirement to uninstall previous version are because of renaming to Bitcoin Core. The files are in same place with only difference in start menu shortcuts.

0.9.0 have some useful improvements over previous version, coin control is the best and most important one! Upgrade safely because it is not more fucked up than previous Qt versions starting with 0.5.0

[wumpus]

Ok, I have installed it, but how to refer to the data path? such as "D:\Coins\Bitcoin". When i installed it, i did not see this option. It was been installed in Disk C.

When bitcoin core is not running, move the data directory to the place you want it (make sure to backup your wallet).

At the next start it will notice that the data directory no longer exists, and you can select where it is.

The doc/build-unix.md instructions say:

To Build
---------------------

        ./autogen.sh
        ./configure
        make

yet the supplied tarball for linux (https://bitcoin.org/bin/0.9.0/bitcoin-0.9.0-linux.tar.gz)has no autogen.sh script supplied in src.

Is it expected to generate that script locally (which would be unorthodox)? But if so it should say so in the documentation.

Just skip the autogen.sh step. It has been done for you in tarball builds, ./configure will already exist.

Though it's probably wrong that the tarballs don't package that.

[DubFX]

Great job devs downloading it now, btw congratz on 420 activity

[ycl1059847]

Have downloaded

[DeathAndTaxes]

When the bitcoin core client is launched on a windows machine with no established data directory, it will prompt the user for the location of a data directory.  Where is this value set?  Nothing is set in the bitcoin.conf. Registry?  Magic?

I like the feature I just don't like not knowing how it works.

Also bitcoind doesn't seem to use the same "data directory" discovery.  I have to add a datadir line to the config and point bitcoind to the config file to ensure it uses the same directory.

Looks like it might write it to the registry?

[HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt]
"bImportFinished"="true"
"nWindowPos"="@Point(323 217)"
"nWindowSize"="@Size(1581 785)"
"nTransactionFee"=hex(b):12,27,00,00,00,00,00,00
"fUseUPnP"="false"
"fUseProxy"="false"
"addrProxy"="127.0.0.1:9050"
"nSocksVersion"=dword:00000005
"fMinimizeToTray"="true"
"fMinimizeOnClose"="true"
"language"="en"
"nDisplayUnit"=dword:00000000
"bDisplayAddresses"="true"
"fRestartRequired"="false"
"fCoinControlFeatures"="false"
"bSpendZeroConfChange"="true"
"nDatabaseCache"=hex(b):64,00,00,00,00,00,00,00
"nThreadsScriptVerif"=dword:00000000
"nRPCConsoleWindowPos"="@Point(591 338)"
"nRPCConsoleWindowSize"="@Size(968 621)"
"nHelpMessageDialogWindowPos"="@Point(560 400)"
"nHelpMessageDialogWindowSize"="@Size(800 400)"
"nOptionsDialogWindowPos"="@Point(680 400)"
"nOptionsDialogWindowSize"="@Size(560 400)"
"strDataDir"="E:\\bitcoin\\data"

I wonder why bitcoind doesn't check for the existence of the same registry key for consistency?

[romang]

Better then sliced bread.

[shortpocket]

Do you know where i can get help with copying wallet + datafiles to USB, maybe from terminal cus i cant find the bitcoin wallet folder. My wallet is installed on one ubuntu and cgminer on the other, as long as i use my wallet i cant use cgminer. My wallet is syncing right now and i have to use it asap, but it wont finish the next couple of days if it continues at the speed it's at now.

[C. Bergmann]

Hi there,

with bitcoin-qt I used -datadir in the .conf file to redirect the blockchain-sync in another directory. With 0.9.0 I want to add the -mintxfee option to reduce fee to 0.00001.

But with the new version it doesn't work and I have to build a .bat file to start bitcoin core automatically with this options. Can somebody help?

[wumpus]

When the bitcoin core client is launched on a windows machine with no established data directory, it will prompt the user for the location of a data directory.  Where is this value set?  Nothing is set in the bitcoin.conf. Registry?  Magic?

I like the feature I just don't like not knowing how it works.

Also bitcoind doesn't seem to use the same "data directory" discovery.  I have to add a datadir line to the config and point bitcoind to the config file to ensure it uses the same directory.

Looks like it might write it to the registry?

It uses QSettings, which indeed uses the registry on Windows.

I wonder why bitcoind doesn't check for the existence of the same registry key for consistency?

Because QSettings is a Qt-only feature. Bitcoind cannot do anything with the registry at all, it doesn't link to Qt.

with bitcoin-qt I used -datadir in the .conf file to redirect the blockchain-sync in another directory. With 0.9.0 I want to add the -mintxfee option to reduce fee to 0.00001.

But with the new version it doesn't work and I have to build a .bat file to start bitcoin core automatically with this options. Can somebody help?

This is currently broken (should be fixed in next release).

You can start bitcoin-qt with -choosedatadir to choose a new data directory. Don't forget to move the bitcoin.conf with custom settings to there as well.

[dreamspark]

Thanks for the update guys.

 Can anyone explain the thinking with new receive tab? I much prefer just generating a new address and then maybe adding a label. With the new tab you request a payment and that generates an address, the only way to distinguish between addresses is by an almost compulsory label (due to not seeing the address itself) why the change?

[DeathAndTaxes]

It uses QSettings, which indeed uses the registry on Windows.

Thanks for the confirmation.  In future versions shouldn't the Keys be under Bitcoin-core not Bitcoin-Qt for consistency?

I wonder why bitcoind doesn't check for the existence of the same registry key for consistency?

Because QSettings is a Qt-only feature. Bitcoind cannot do anything with the registry at all, it doesn't link to Qt.

Good to know.  

I wonder though if this could be refactored to provide a more consistent behavior between the two clients.  For non-windows specific options wouldn't it make more sense to just write those to the bitcoin.conf.  The GUI client already reads the conf file for the presence of these options.

As an example, setting the pay tx fee option in the bitcoin-core to 0.1 mBTC GUI client adds nTransactionFee key to the registry however if the same user now starts up bitcoind it will use the default fee (0) because there is no entry in the bitcoin.conf.  Since an RPC call can be made against either bitcoind or bitcoin-core (w/server=1 option) the outcome of an RPC call will depend on where it is made.  Likewise if a fee of 0.2 mBTC is indicated in the bitcoin.conf then the client will still display 0.1 mBTC however the actual fee paid will be 0.2 mBTC.  The client does provide a warning that the setting has been overriden but this isn't exactly user friendly or intuitive.

Do you agree that keeping it DRY would be better?  Refactor bitcoin-core so that both bitcoind and bitcoin-core use the bitcoin.conf to store non client specific settings (i.e. data directory, tx fee, dbcache, proxy, etc).  The registry would only be used for client specific settings (location of windows, units to display, minimize handling, etc).

To be consistent that would also include the data directory however the registry can still be used indirectly by providing the location to the configuration file itself.
1) User launches bitcoin-core with no data directory created.
2) Wizard prompts user for location of data directory.
3) Create bitcoin.conf in directory is needed.
4) Set data directory in bitcoin.conf.
5) Add registry entry pointing to the bitcoin.conf

On startup the client would check for existance of "ConfigFile" registry key and if present load the bitcoin.conf to determine the data directory and other non-client specific settings.

Just something to think about to make the behavior of the GUI and deamon consistent.  The other option is to simply stop bundling the two and treat them like independent applications.

[wumpus]

Can anyone explain the thinking with new receive tab? I much prefer just generating a new address and then maybe adding a label. With the new tab you request a payment and that generates an address, the only way to distinguish between addresses is by an almost compulsory label (due to not seeing the address itself) why the change?

Did it become any more difficult? You can (optionally) enter a label then click "Request payment". The new address is immediately shown in the window that appears. You can quickly copy the address with the "Copy address" button.

It is also still perfectly possible to create new addresses the old way in the receiving addresses window, if you insist on doing that.

Thanks for the confirmation.  In future versions shouldn't the Keys be under Bitcoin-core not Bitcoin-Qt for consistency?

Personally I think that's not worth the trouble of migrating. Though if you'd submit a pull request to do that and make sure that all the potential migration scenarios are covered, it would of course be accepted.

I wonder though if this could be refactored to provide a more consistent behavior between the two clients.  For non-windows specific options wouldn't it make more sense to just write those to the bitcoin.conf.  The GUI client already reads the conf file for the presence of these options.

Writing to the bitcoin.conf would be inconsistent from a user viewpoint.

It is a user-created configuration file and should only be touched by the user.
Rewriting it, or any other tricks, would lose comments and formatting (or you'd have to go through a lot of trouble to preserve them, but it's fighting windmills). You don't see other daemons like apache suddenly rewriting their configuration...

It would be an idea to generate an extra configuration file "bitcoin.conf.generated" which is read in addition to the main bitcoind.conf, but I'm not sure how that would help.

The extra step registry -> generated config file -> bitcoind could introduce bugs.

I do just realize that when the wallet is split off to a seperate executable (ie SPV mode), and we want to run a bitcoind in the background, we will have to do something with generated config files.

[dreamspark]

Can anyone explain the thinking with new receive tab? I much prefer just generating a new address and then maybe adding a label. With the new tab you request a payment and that generates an address, the only way to distinguish between addresses is by an almost compulsory label (due to not seeing the address itself) why the change?

Did it become any more difficult? You can (optionally) enter a label then click "Request payment". The new address is immediately shown in the window that appears. You can quickly copy the address with the "Copy address" button.

It is also still perfectly possible to create new addresses the old way in the receiving addresses window, if you insist on doing that.

Thanks for replying. My point was not about difficulty it was about the thinking behind the change, yes the label is optional but there is no way to quickly distinguish between addresses (without clicking them) without a label.

There isn't, as far as I can see, a way to do it the old way? I would consider the old way creating an address and then having those listed in the receiving tab with the address visible. From what I can see with the new release there is no way to have the address visible and thus my question.

[awesomeami]

https://bitcointalk.org/index.php?topic=562388.new#new
0.9.1 already released
update ASAP pls - just for sure