Bitcoin Core 0.10.1 has been released

[HostFat]

Bitcoin Core version 0.10.1 is now available from:

https://bitcoin.org/bin/bitcoin-core-0.10.1/

This is a new minor version release, bringing bug fixes and translation
updates. It is recommended to upgrade to this version.

Please report bugs using the issue tracker at github:

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

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

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

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

Downgrade warning
------------------

Because release 0.10.0 and later makes use of headers-first synchronization and
parallel block download (see further), the block files and databases are not
backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:

* Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.

* The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.

If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.

This does not affect wallet forward or backward compatibility.

Notable changes
===============

This is a minor release and hence there are no notable changes.
For the notable changes in 0.10, refer to the release notes for the
0.10.0 release at https://github.com/bitcoin/bitcoin/blob/v0.10.0/doc/release-notes.md

0.10.1 Change log
=================

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.

RPC:
- `7f502be` fix crash: createmultisig and addmultisigaddress
- `eae305f` Fix missing lock in submitblock

Block (database) and transaction handling:
- `1d2cdd2` Fix InvalidateBlock to add chainActive.Tip to setBlockIndexCandidates
- `c91c660` fix InvalidateBlock to repopulate setBlockIndexCandidates
- `002c8a2` fix possible block db breakage during re-index
- `a1f425b` Add (optional) consistency check for the block chain data structures
- `1c62e84` Keep mempool consistent during block-reorgs
- `57d1f46` Fix CheckBlockIndex for reindex
- `bac6fca` Set nSequenceId when a block is fully linked

P2P protocol and network code:
- `78f64ef` don't trickle for whitelisted nodes
- `ca301bf` Reduce fingerprinting through timestamps in 'addr' messages.
- `200f293` Ignore getaddr messages on Outbound connections.
- `d5d8998` Limit message sizes before transfer
- `aeb9279` Better fingerprinting protection for non-main-chain getdatas.
- `cf0218f` Make addrman's bucket placement deterministic (countermeasure 1 against eclipse attacks, see http://cs-people.bu.edu/heilman/eclipse/)
- `0c6f334` Always use a 50% chance to choose between tried and new entries (countermeasure 2 against eclipse attacks)
- `214154e` Do not bias outgoing connections towards fresh addresses (countermeasure 2 against eclipse attacks)
- `aa587d4` Scale up addrman (countermeasure 6 against eclipse attacks)
- `139cd81` Cap nAttempts penalty at 8 and switch to pow instead of a division loop

Validation:
- `d148f62` Acquire CCheckQueue's lock to avoid race condition

Build system:
- `8752b5c` 0.10 fix for crashes on OSX 10.6

Wallet:
- N/A

GUI:
- `2c08406` some mac specifiy cleanup (memory handling, unnecessary code)
- `81145a6` fix OSX dock icon window reopening
- `786cf72` fix a issue where "command line options"-action overwrite "Preference"-action (on OSX)

Tests:
- `1117378` add RPC test for InvalidateBlock

Miscellaneous:
- `c9e022b` Initialization: set Boost path locale in main thread
- `23126a0` Sanitize command strings before logging them.
- `323de27` Initialization: setup environment before starting QT tests
- `7494e09` Initialization: setup environment before starting tests
- `df45564` Initialization: set fallback locale as environment variable

Credits
=======

Thanks to everyone who directly contributed to this release:

- Alex Morcos
- Cory Fields
- dexX7
- fsb4000
- Gavin Andresen
- Gregory Maxwell
- Ivan Pustogarov
- Jonas Schnelli
- Matt Corallo
- mrbandrews
- Pieter Wuille
- Ruben de Vries
- Suhas Daftuar
- Wladimir J. van der Laan

And all those who contributed additional code review and/or security research:
- 21E14
- Alison Kendler
- Aviv Zohar
- Ethan Heilman
- Evil-Knievel
- fanquake
- Jeff Garzik
- Jonas Nick
- Luke Dashjr
- Patrick Strateman
- Philip Kaufmann
- Sergio Demian Lerner
- Sharon Goldberg

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

[1714941696]

1714941696

[1714941696]

1714941696

[1714941696]

1714941696

[manselr]

Is it recommended to delete your blockchain and download a fresh one even if it works just ok with your current one? It would be pretty annoying since it's very slow to download the whole thing, but even then, im pretty paranoid and i want a correctly working blockchain.

[basementdweller]

Great! I didn't upgrade to 0.10.0, but after no serious problems reported with 0.10.0 and these fixes I now feel the urge to do it.

Is it recommended to delete your blockchain and download a fresh one even if it works just ok with your current one? It would be pretty annoying since it's very slow to download the whole thing, but even then, im pretty paranoid and i want a correctly working blockchain.

I don't think so. Why should you? What I understand is that blockchain issues should only be expected when downgrading.

[Mikestang]

Great, hopefully this version will fix the problem where my Core closes randomly with no error and nothing shown in the logs.

[Supercrypt]

when i have downloaded this new version it started reindexing whole blockchain, it there any option to stop reindexing

[shorena]

when i have downloaded this new version it started reindexing whole blockchain, it there any option to stop reindexing

If its reindexing its because it needs to rebuild the index from the block files in order to work properly. You can stop it by closing the client, but you wont be able to use it without it finishing first.

btw: I did not have any problem when updating.

[unamis76]

So apparently this was a bug indeed: https://bitcointalk.org/index.php?topic=944369.0 Glad it was fixed

[BitcoinINV]

awsome, i think its better now , bugs are fixed, liked the wroked done keep it up

[Amph]

nothing changed on my side, 0.1 was wokring flawless, i think that some bugs are not only client related, in the sense that they come out with a bad os configuration/corrupted os

[Mikestang]

Great, hopefully this version will fix the problem where my Core closes randomly with no error and nothing shown in the logs.

Nah it probably won't.

You were right, had 0.10.1 close itself silently on me today.

[M95]

I haven't noticed much difference from the update though 

[zip420]

Awesome, will have to upgrade soon 

[EarthcoinThinker]

  am still sync it on my networks waiting how does it works

[PremiumCodeX]

You may upgrade since the users I have discussed it with reported no serious problems and I neither experienced such thing. If the previous version works well at you, why would you not upgrade? And if the previous version was bugged at you, the new one may solve your problems. Anyway, enjoy and feel free to write a feedback how the process went! It was just fine at me.

[knight22]

Upgrading 

[TurdHurdur]

Having a build issue on Debian Squeeze-LTS:

Code:

CXX    libbitcoin_util_a-util.o
util.cpp: In function ‘void ShrinkDebugFile()’:
util.cpp:636: warning: ignoring return value of ‘size_t fwrite(const void*, size_t, size_t, FILE*)’, declared with attribute warn_unused_result
util.cpp: In function ‘void SetupEnvironment()’:
util.cpp:728: error: ‘imbue’ is not a member of ‘boost::filesystem::path’
make[2]: *** [libbitcoin_util_a-util.o] Error 1
make[2]: Leaving directory `/usr/local/src/bitcoin-core-0.10.1/bitcoin-0.10.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/bitcoin-core-0.10.1/bitcoin-0.10.1/src'
make: *** [all-recursive] Error 1

[Jsynnthegr8]

Wish me luck about to try!! will update

[AngelLox]

Hi, i'm new around here, i was wondering if using wallets that don't require downloading the whole blockchain (multibit) is less safe than Bitcoin Core.

[shorena]

Hi, i'm new around here, i was wondering if using wallets that don't require downloading the whole blockchain (multibit) is less safe than Bitcoin Core.

No. SPV clients that allow you control over your private keys (like Multibit or Electrum) are for all general purposes as safe as a full node.

[BTC_Superman]

updating, give feedback later. Hope, all bugs issue are solved.