Bitcoin Core version 0.11.2 released

[HostFat]

Bitcoin Core version 0.11.2 is now available from:

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

This is a new minor version release, bringing bug fixes, the BIP65
(CLTV) consensus change, and relay policy preparation for BIP113. It is
recommended to upgrade to this version as soon as possible.

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. There are no
known problems when downgrading from 0.11.x to 0.10.x.

Notable changes since 0.11.1
============================

BIP65 soft fork to enforce OP_CHECKLOCKTIMEVERIFY opcode
--------------------------------------------------------

This release includes several changes related to the [BIP65][] soft fork
which redefines the existing OP_NOP2 opcode as OP_CHECKLOCKTIMEVERIFY
(CLTV) so that a transaction output can be made unspendable until a
specified point in the future.

1. This release will only relay and mine transactions spending a CLTV
   output if they comply with the BIP65 rules as provided in code.

2. This release will produce version 4 blocks by default. Please see the
   *notice to miners* below.

3. Once 951 out of a sequence of 1,001 blocks on the local node's best block
   chain contain version 4 (or higher) blocks, this release will no
   longer accept new version 3 blocks and it will only accept version 4
   blocks if they comply with the BIP65 rules for CLTV.

For more information about the soft-forking change, please see
https://github.com/bitcoin/bitcoin/pull/6351

Graphs showing the progress towards block version 4 adoption may be
found at the URLs below:

- Block versions over the last 50,000 blocks as progress towards BIP65
  consensus enforcement: http://bitcoin.sipa.be/ver-50k.png

- Block versions over the last 2,000 blocks showing the days to the
  earliest possible BIP65 consensus-enforced block: http://bitcoin.sipa.be/ver-2k.png

**Notice to miners:** Bitcoin Core’s block templates are now for
version 4 blocks only, and any mining software relying on its
getblocktemplate must be updated in parallel to use libblkmaker either
version 0.4.3 or any version from 0.5.2 onward.

- If you are solo mining, this will affect you the moment you upgrade
  Bitcoin Core, which must be done prior to BIP65 achieving its 951/1001
  status.

- If you are mining with the stratum mining protocol: this does not
  affect you.

- If you are mining with the getblocktemplate protocol to a pool: this
  will affect you at the pool operator’s discretion, which must be no
  later than BIP65 achieving its 951/1001 status.

[BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki

BIP113 mempool-only locktime enforcement using GetMedianTimePast()
----------------------------------------------------------------

Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block.  Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.

Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future.  This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
hours.

The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks.  This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.

[BIP113][] specifies a soft fork (**not enforced in this release**) that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.

Mempool inclusion rules currently require transactions to be valid for
immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP113 rule to received transactions,
so transaction whose time is greater than the GetMedianTimePast() will
no longer be accepted into the mempool.

**Implication for miners:** you will begin rejecting transactions that
would not be valid under BIP113, which will prevent you from producing
invalid blocks if/when BIP113 is enforced on the network. Any
transactions which are valid under the current rules but not yet valid
under the BIP113 rules will either be mined by other miners or delayed
until they are valid under BIP113. Note, however, that time-based
locktime transactions are more or less unseen on the network currently.

**Implication for users:** GetMedianTimePast() always trails behind the
current time, so a transaction locktime set to the present time will be
rejected by nodes running this release until the median time moves
forward. To compensate, subtract one hour (3,600 seconds) from your
locktimes to allow those transactions to be included in mempools at
approximately the expected time.

[BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki

Windows bug fix for corrupted UTXO database on unclean shutdowns
----------------------------------------------------------------

Several Windows users reported that they often need to reindex the
entire blockchain after an unclean shutdown of Bitcoin Core on Windows
(or an unclean shutdown of Windows itself). Although unclean shutdowns
remain unsafe, this release no longer relies on memory-mapped files for
the UTXO database, which significantly reduced the frequency of unclean
shutdowns leading to required reindexes during testing.

For more information, see: https://github.com/bitcoin/bitcoin/pull/6917

Other fixes for database corruption on Windows are expected in the
next major release.

0.11.2 Change log
=================

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

- #6124 `684636b` Make CScriptNum() take nMaxNumSize as an argument
- #6124 `4fa7a04` Replace NOP2 with CHECKLOCKTIMEVERIFY (BIP65)
- #6124 `6ea5ca4` Enable CHECKLOCKTIMEVERIFY as a standard script verify flag
- #6351 `5e82e1c` Add CHECKLOCKTIMEVERIFY (BIP65) soft-fork logic
- #6353 `ba1da90` Show softfork status in getblockchaininfo
- #6351 `6af25b0` Add BIP65 to getblockchaininfo softforks list
- #6688 `01878c9` Fix locking in GetTransaction
- #6653 `b3eaa30` [Qt] Raise debug window when requested
- #6600 `1e672ae` Debian/Ubuntu: Include bitcoin-tx binary
- #6600 `2394f4d` Debian/Ubuntu: Split bitcoin-tx into its own package
- #5987 `33d6825` Bugfix: Allow mining on top of old tip blocks for testnet
- #6852 `21e58b8` build: make sure OpenSSL heeds noexecstack
- #6846 `af6edac` alias `-h` for `--help`
- #6867 `95a5039` Set TCP_NODELAY on P2P sockets.
- #6856 `dfe55bd` Do not allow blockfile pruning during reindex.
- #6566 `a1d3c6f` Add rules--presently disabled--for using GetMedianTimePast as end point for lock-time calculations
- #6566 `f720c5f` Enable policy enforcing GetMedianTimePast as the end point of lock-time constraints
- #6917 `0af5b8e` leveldb: Win32WritableFile without memory mapping
- #6948 `4e895b0` Always flush block and undo when switching to new file

Credits
=======

Thanks to everyone who directly contributed to this release:

- Alex Morcos
- ฿tcDrak
- Chris Kleeschulte
- Daniel Cousens
- Diego Viola
- Eric Lombrozo
- Esteban Ordano
- Gregory Maxwell
- Luke Dashjr
- Marco Falke
- Mark Friedenbach
- Matt Corallo
- Micha
- Mitchell Cash
- Peter Todd
- Pieter Wuille
- Wladimir J. van der Laan
- Zak Wilcox

And those who contributed additional code review and/or security research.

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

[1713592764]

1713592764

[1713592764]

1713592764

[1713592764]

1713592764

[1713592764]

1713592764

[1713592764]

1713592764

[1713592764]

1713592764

[Amph]

not on bitcoin.org yet, if it's not mandatory to upgrade i'll wait

[OmegaStarScream]

Good job for the developers , wondering how much it would like take us to reach at least bitcoin 1.0v with this speed of development progress

not on bitcoin.org yet, if it's not mandatory to upgrade i'll wait

and what is this ? https://bitcoin.org/bin/bitcoin-core-0.11.2/ , the fact that it got added here means that it will eventually get added on the download page .

[camponez]

Looking at the latest 1001 blocks, I'm already seeing 200+ v4 blocks.

[Carlton Banks]

not on bitcoin.org yet, if it's not mandatory to upgrade i'll wait

They always tend to wait about 24 hours while the github users who provide Gitian signatures for the build throw up their own personal signature for that release in the Bitcoin repo on github.

If that sounds like nonsense, they're essentially proving that the installation packages on bitcoin.org were built from the source code they're supposed to be from, by providing a signed copy of some verifiable aspect of the build output.

Not sure how reassuring all that it is if you can't build it yourself to compare, but I guess the idea is that all the devs who contribute signatures keep themselves in check. The alternative is that every single one of them is contributing sigs for a compromised build, which is always going to get discovered by some public user anyway. So it's like a chain of trust: if you know someone personally that does build Bitcoin themselves, that should add further reassurance if they can confirm the bitcoin.org downloads are good.

Edit: 0.11.2 is up on bitcoin.org/bin and bitcoin.org/en/download now

[rupy]

When is pruning with wallet planned for?

[frank0929]

I think it's not mandatory to download this version. I don't want to change my Core in every update, it's updated too often.
Maybe next versions we have auto-update options built inside of the Core, just like Windows Updates.

[OmegaStarScream]

I think it's not mandatory to download this version. I don't want to change my Core in every update, it's updated too often.
Maybe next versions we have auto-update options built inside of the Core, just like Windows Updates.

That's not going to happen , not now and not ever probably . Because this means that someone will be controlling the network and this will be dangerous .
See here few words from one of the developers of Bitcoin Core : https://bitcointalk.org/index.php?topic=293824.msg3148582#msg3148582

[saturn643]

When is pruning with wallet planned for?

0.12 which is planned for December

[frank0929]

I think it's not mandatory to download this version. I don't want to change my Core in every update, it's updated too often.
Maybe next versions we have auto-update options built inside of the Core, just like Windows Updates.

That's not going to happen , not now and not ever probably . Because this means that someone will be controlling the network and this will be dangerous .
See here few words from one of the developers of Bitcoin Core : https://bitcointalk.org/index.php?topic=293824.msg3148582#msg3148582

I mean built-in update button, not auto-update without having my permission. I know that would be dangerous.

[Kprawn]

I think it's not mandatory to download this version. I don't want to change my Core in every update, it's updated too often.
Maybe next versions we have auto-update options built inside of the Core, just like Windows Updates.

I would prefer to make that choice on my own. Can you imagine if someone push a malicious update and it get automatically updates to the majority, and they infect the whole

network? That would not be very smart... The updates has always been manual. The Windows bug fix is a good addition, because I have some friends, who said they struggled

with that.  I am just glad the changes are less often, and not as often as Tor. 

[frank0929]

I would prefer to make that choice on my own. Can you imagine if someone push a malicious update and it get automatically updates to the majority, and they infect the whole network? That would not be very smart... The updates has always been manual.

Did you even read my previous post?

[Carlton Banks]

I would prefer to make that choice on my own. Can you imagine if someone push a malicious update and it get automatically updates to the majority, and they infect the whole network? That would not be very smart... The updates has always been manual.

Did you even read my previous post?

It's not going to happen, read OmegaStarScream's link.

[moli]

LOL... I kept waiting for this version because it has the windows bug fix but couldn't wait any longer so I installed v.11.1 yesterday. My wallet is still at "17 weeks behind..."  I suppose it shouldn't matter if I close the wallet now and get this new version?   

[shorena]

LOL... I kept waiting for this version because it has the windows bug fix but couldn't wait any longer so I installed v.11.1 yesterday. My wallet is still at "17 weeks behind..."  I suppose it shouldn't matter if I close the wallet now and get this new version?   

Nope, it will continue where you closed it.

[Ankara]

LOL... I kept waiting for this version because it has the windows bug fix but couldn't wait any longer so I installed v.11.1 yesterday. My wallet is still at "17 weeks behind..."  I suppose it shouldn't matter if I close the wallet now and get this new version?  

Yeah, you don't have any problems. You can update it. Just in case something happens don't forget to backup your wallet.dat file.

[moli]

Yes.  Thank you. 

[oblivi]

I think it's not mandatory to download this version. I don't want to change my Core in every update, it's updated too often.
Maybe next versions we have auto-update options built inside of the Core, just like Windows Updates.

Yeah, what a hassle. Let's NOT update (because it only takes like 2 minutes) and get exposed to some bugs instead.
Cmon man just update the thing, it takes no time. It's not like you have to download the entire blockchain from scratch.

[mb300sd]

That windows bug has definitely been a PITA. Takes nearly 24 hours to reindex with the CPU fan screaming in my ear since I usually sleep with my laptop next to my head.

[Carlton Banks]

That windows bug has definitely been a PITA. Takes nearly 24 hours to reindex with the CPU fan screaming in my ear since I usually sleep with my laptop next to my head.

lol you must be very dedicated to Windows and Bitcoin. I often wonder if it'll take Windows 365 before people switch to something else.  

[mb300sd]

That windows bug has definitely been a PITA. Takes nearly 24 hours to reindex with the CPU fan screaming in my ear since I usually sleep with my laptop next to my head.

lol you must be very dedicated to Windows and Bitcoin. I often wonder if it'll take Windows 365 before people switch to something else. 

Windows 7 or 8.1 max here, will never be switching to 10 and have the spyware updates blacklisted in my WSUS server, as well as blackholeing the IPs in my router.

[Carlton Banks]

That windows bug has definitely been a PITA. Takes nearly 24 hours to reindex with the CPU fan screaming in my ear since I usually sleep with my laptop next to my head.

lol you must be very dedicated to Windows and Bitcoin. I often wonder if it'll take Windows 365 before people switch to something else. 

Windows 7 or 8.1 max here, will never be switching to 10 and have the spyware updates blacklisted in my WSUS server, as well as blackholeing the IPs in my router.

Yeah, I heard about that. No use resisting, you will be assimilated!

[rocks]

Where is the 95% consensus to implement an OP code change? Or right we don't need consensus for Blockstream projects.

[saturn643]

Where is the 95% consensus to implement an OP code change? Or right we don't need consensus for Blockstream projects.

The developers agreed and there was consensus to include OP_CHECKLOCKTIMEVERIFY in this version and on. The actual enforcement of BIP65 for this will only occur after 951 out of the last 1001 blocks have version 4 or higher. Read the info about it in the release notes in the OP.

[mezzomix]

If you don't want BIP65, do not mine V4 blocks and do not relay V4 blocks. For me BIP65 has some advantages and no big drawbacks so I relay and accept V4 blocks.

[Febo]

i still have 0.9 , so last time for me to update. 

[Soros Shorts]

That windows bug has definitely been a PITA. Takes nearly 24 hours to reindex with the CPU fan screaming in my ear since I usually sleep with my laptop next to my head.

lol you must be very dedicated to Windows and Bitcoin. I often wonder if it'll take Windows 365 before people switch to something else.  

Windows 7 or 8.1 max here, will never be switching to 10 and have the spyware updates blacklisted in my WSUS server, as well as blackholeing the IPs in my router.

Yeah, I heard about that. No use resisting, you will be assimilated!

If you have a need to run a current Windows O/S consider running Windows Server. I have been running Windows Server 2012R2 instead of 8.1 and I will soon upgrade to Windows Server 2016 (Windows 10 equivalent). They are meant to be run in air-gapped environments and spyware is disabled by default or easy to turn off. The default server install is also way more hardened than the default desktop Windows install.

[BillyBobZorton]

I can't update my blockchain since updating to 0.11.2 (I had 0.11.1 and was working fine). I am stuck in "activating best chain" with the intro splash screen window thing with the BTC logo for some reason.

[Carlton Banks]

I can't update my blockchain since updating to 0.11.2 (I had 0.11.1 and was working fine). I am stuck in "activating best chain" with the intro splash screen window thing with the BTC logo for some reason.

I've had this issue, but not since 0.11.2 (not upgraded yet). It took maybe 20 minutes, but it works through it.

[oblivi]

Just wait until it's done. This happened to me as well, but it turn out that it was loading blocks.You can go to the bitcoin folder and refresh the "blocks" folder to see if it's downloading something.

[rupy]

When is pruning with wallet planned for?

0.12 which is planned for December

Thx!

[hogwild]

I downloaded the source and compiled as normal. I see on bitnodes that it shows my version as 0.11.99.  Does it matter?

[Carlton Banks]

I downloaded the source and compiled as normal. I see on bitnodes that it shows my version as 0.11.99.  Does it matter?

Presumably, you had "master" selected as the branch for that to happen. Select the code for the "0.11.2" tag to compile instead.

[hogwild]

I downloaded the source and compiled as normal. I see on bitnodes that it shows my version as 0.11.99.  Does it matter?

Presumably, you had "master" selected as the branch for that to happen. Select the code for the "0.1y1.2" tag to compile instead.

Thanks. Will do. Before I would click the github link from the download page and then click the download zip button.  I'll look for the tag.

[dooglus]

I just checked out the v0.11.2 tag, rebuilt, and ran the bitcoin-qt executable.

It decided it was going to rescan the whole blockchain:

2015-11-17 05:01:15 init message: Verifying blocks...
2015-11-17 05:01:15 Verifying last 288 blocks at level 2
2015-11-17 05:01:18 No coin database inconsistencies in last 0 blocks (0 transactions)
2015-11-17 05:01:18  block index            5497ms
2015-11-17 05:01:18 init message: Loading wallet...
2015-11-17 05:01:18 nFileVersion = 119900
2015-11-17 05:01:18 Keys: 0 plaintext, 2514 encrypted, 160 w/ metadata, 2514 total
2015-11-17 05:01:18  wallet                  309ms
2015-11-17 05:01:18 init message: Rescanning...
2015-11-17 05:01:18 Rescanning last 383899 blocks (from block 0)...

Any idea why it did that?

As I remember, the last time I rebuilt the same thing happened. I think the last version I built was v0.11.

Edit: it appears that this code:

            if (walletdb.ReadBestBlock(locator))
                pindexRescan = FindForkInGlobalIndex(chainActive, locator);

is running, but the locator vector is empty, so FindForkInGlobalIndex() is returning chain.Genesis().

I don't know why ReadBestBlock() isn't working for me between rebuilds.

[indahkfi]

what are the advantages Bitcoin Core version 0.11.2
compared to the previous ? ?? thanks

[Carlton Banks]

what are the advantages Bitcoin Core version 0.11.2
compared to the previous ? ?? thanks

Only substantial advantages right now over 0.11.1 are for Windows users (partial fix of the problem where Windows users needed constant re-indexing of the blockchain database). This version is more a backwards compatibility fix for the future.... if that makes any sense.

The reason is that from 0.11.2 onwards, version 4 blocks are being promoted instead of version 3 blocks. This is to add a new feature to bitcoin that enables time delayed transactions directly on the blockchain. It could take 6-12 weeks for all the miners to upgrade, and actual version 4 blocks don't start getting made until after enough "version 4 ready" blocks get made in a given window (951 out of the last 1001 blocks IIRC).

After that, anyone not using at least 11.2 or 10.4 won't be able to make use of the new transcation features (and all the new services that will spring up making use of them), and anyone mining will have to upgrade or all their work will go to waste.

[saturn643]

The reason is that from 0.11.2 onwards, version 4 blocks are being promoted instead of version 3 blocks. This is to add a new feature to bitcoin that enables time delayed transactions directly on the blockchain. It could take 6-12 weeks for all the miners to upgrade, and actual version 4 blocks don't start getting made until after enough "version 4 ready" blocks get made in a given window (951 out of the last 1001 blocks IIRC).

Technically version 4 blocks are being made (they have to be in order for the forking mechanism to know when to fork). According to the BIP, when 750 out of the last 1000 blocks are version 4 or greater, then the new rules will go into affect and OP_CLTV will work. After 950 out of the last 1000 blocks are version 4 or greater, then all new blocks that have a version number less than 4 are invalid.

[Carlton Banks]

The reason is that from 0.11.2 onwards, version 4 blocks are being promoted instead of version 3 blocks. This is to add a new feature to bitcoin that enables time delayed transactions directly on the blockchain. It could take 6-12 weeks for all the miners to upgrade, and actual version 4 blocks don't start getting made until after enough "version 4 ready" blocks get made in a given window (951 out of the last 1001 blocks IIRC).

Technically version 4 blocks are being made (they have to be in order for the forking mechanism to know when to fork). According to the BIP, when 750 out of the last 1000 blocks are version 4 or greater, then the new rules will go into affect and OP_CLTV will work. After 950 out of the last 1000 blocks are version 4 or greater, then all new blocks that have a version number less than 4 are invalid.

Yeah, that sounds a bit more convincing. Was trying to remember off the top of my head, so much for that lol 

[dlb76]

updated to 0.11.2 x64
Thanks!

[Mikestang]

I have upgraded my node to 0.11.2, I still get the random crashes sometimes when I receive incoming transactions, but seeing as I have had this error for a while now I think it is related to my hardware and not the application.

[crazyearner]

Bitcoin core needs a serious overhaul in order to get it working smooth since the 0.10 version I have stopped using because of all the crashes and massive amounts of data downloaded. Maybe when they re work it to run smooth without crashes and works with far less data to download then maybe I might just start using Bitcoin Core or client once again.

[Laviathon]

What would this mean for pools that update?  Any adverse effect for the miners on the pool?

[Mikestang]

All pools must update to produce v4 blocks by a certain time, but it doesn't have any affect on miners - as long as the pool is updated in time.   

[Laviathon]

All pools must update to produce v4 blocks by a certain time, but it doesn't have any affect on miners - as long as the pool is updated in time.   

Thanks for the reply.

[LeeVelazquez]

I have gone through the post. It helps to know the features of newly developed version of Bitcoin.

[crazyearner]

Going to give Bitcoin core one last try and update and see where it leads me to as have some old wallets in it with some change so going to update and if this time it crashes just going to grab keys and forget core is even around due to the data it uses and crashes a lot of the time. Hoping for some joy or its back and ongoing use of bither.

[noinken]

thanks for the great work!

[Hannu]

Bitcoin Core version 0.11.2 is now available from:

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

This is a new minor version release, bringing bug fixes, the BIP65
(CLTV) consensus change, and relay policy preparation for BIP113. It is
recommended to upgrade to this version as soon as possible.

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. There are no
known problems when downgrading from 0.11.x to 0.10.x.

Notable changes since 0.11.1
============================

BIP65 soft fork to enforce OP_CHECKLOCKTIMEVERIFY opcode
--------------------------------------------------------

This release includes several changes related to the [BIP65][] soft fork
which redefines the existing OP_NOP2 opcode as OP_CHECKLOCKTIMEVERIFY
(CLTV) so that a transaction output can be made unspendable until a
specified point in the future.

1. This release will only relay and mine transactions spending a CLTV
   output if they comply with the BIP65 rules as provided in code.

2. This release will produce version 4 blocks by default. Please see the
   *notice to miners* below.

3. Once 951 out of a sequence of 1,001 blocks on the local node's best block
   chain contain version 4 (or higher) blocks, this release will no
   longer accept new version 3 blocks and it will only accept version 4
   blocks if they comply with the BIP65 rules for CLTV.

For more information about the soft-forking change, please see
https://github.com/bitcoin/bitcoin/pull/6351

Graphs showing the progress towards block version 4 adoption may be
found at the URLs below:

- Block versions over the last 50,000 blocks as progress towards BIP65
  consensus enforcement: http://bitcoin.sipa.be/ver-50k.png

- Block versions over the last 2,000 blocks showing the days to the
  earliest possible BIP65 consensus-enforced block: http://bitcoin.sipa.be/ver-2k.png

**Notice to miners:** Bitcoin Core’s block templates are now for
version 4 blocks only, and any mining software relying on its
getblocktemplate must be updated in parallel to use libblkmaker either
version 0.4.3 or any version from 0.5.2 onward.

- If you are solo mining, this will affect you the moment you upgrade
  Bitcoin Core, which must be done prior to BIP65 achieving its 951/1001
  status.

- If you are mining with the stratum mining protocol: this does not
  affect you.

- If you are mining with the getblocktemplate protocol to a pool: this
  will affect you at the pool operator’s discretion, which must be no
  later than BIP65 achieving its 951/1001 status.

[BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki

BIP113 mempool-only locktime enforcement using GetMedianTimePast()
----------------------------------------------------------------

Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block.  Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.

Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future.  This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
hours.

The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks.  This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.

[BIP113][] specifies a soft fork (**not enforced in this release**) that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.

Mempool inclusion rules currently require transactions to be valid for
immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP113 rule to received transactions,
so transaction whose time is greater than the GetMedianTimePast() will
no longer be accepted into the mempool.

**Implication for miners:** you will begin rejecting transactions that
would not be valid under BIP113, which will prevent you from producing
invalid blocks if/when BIP113 is enforced on the network. Any
transactions which are valid under the current rules but not yet valid
under the BIP113 rules will either be mined by other miners or delayed
until they are valid under BIP113. Note, however, that time-based
locktime transactions are more or less unseen on the network currently.

**Implication for users:** GetMedianTimePast() always trails behind the
current time, so a transaction locktime set to the present time will be
rejected by nodes running this release until the median time moves
forward. To compensate, subtract one hour (3,600 seconds) from your
locktimes to allow those transactions to be included in mempools at
approximately the expected time.

[BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki

Windows bug fix for corrupted UTXO database on unclean shutdowns
----------------------------------------------------------------

Several Windows users reported that they often need to reindex the
entire blockchain after an unclean shutdown of Bitcoin Core on Windows
(or an unclean shutdown of Windows itself). Although unclean shutdowns
remain unsafe, this release no longer relies on memory-mapped files for
the UTXO database, which significantly reduced the frequency of unclean
shutdowns leading to required reindexes during testing.

For more information, see: https://github.com/bitcoin/bitcoin/pull/6917

Other fixes for database corruption on Windows are expected in the
next major release.

0.11.2 Change log
=================

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

- #6124 `684636b` Make CScriptNum() take nMaxNumSize as an argument
- #6124 `4fa7a04` Replace NOP2 with CHECKLOCKTIMEVERIFY (BIP65)
- #6124 `6ea5ca4` Enable CHECKLOCKTIMEVERIFY as a standard script verify flag
- #6351 `5e82e1c` Add CHECKLOCKTIMEVERIFY (BIP65) soft-fork logic
- #6353 `ba1da90` Show softfork status in getblockchaininfo
- #6351 `6af25b0` Add BIP65 to getblockchaininfo softforks list
- #6688 `01878c9` Fix locking in GetTransaction
- #6653 `b3eaa30` [Qt] Raise debug window when requested
- #6600 `1e672ae` Debian/Ubuntu: Include bitcoin-tx binary
- #6600 `2394f4d` Debian/Ubuntu: Split bitcoin-tx into its own package
- #5987 `33d6825` Bugfix: Allow mining on top of old tip blocks for testnet
- #6852 `21e58b8` build: make sure OpenSSL heeds noexecstack
- #6846 `af6edac` alias `-h` for `--help`
- #6867 `95a5039` Set TCP_NODELAY on P2P sockets.
- #6856 `dfe55bd` Do not allow blockfile pruning during reindex.
- #6566 `a1d3c6f` Add rules--presently disabled--for using GetMedianTimePast as end point for lock-time calculations
- #6566 `f720c5f` Enable policy enforcing GetMedianTimePast as the end point of lock-time constraints
- #6917 `0af5b8e` leveldb: Win32WritableFile without memory mapping
- #6948 `4e895b0` Always flush block and undo when switching to new file

Credits
=======

Thanks to everyone who directly contributed to this release:

- Alex Morcos
- ฿tcDrak
- Chris Kleeschulte
- Daniel Cousens
- Diego Viola
- Eric Lombrozo
- Esteban Ordano
- Gregory Maxwell
- Luke Dashjr
- Marco Falke
- Mark Friedenbach
- Matt Corallo
- Micha
- Mitchell Cash
- Peter Todd
- Pieter Wuille
- Wladimir J. van der Laan
- Zak Wilcox

And those who contributed additional code review and/or security research.

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

Hello =)

How i can install new core to raspberry newest version? I think new version is better then old one. Windows Server is much easyer to configure then rasbian jessie.

[ausbit]

thanks for the great work!

Wow ,I will sure check this out of this Bitcoin core version 0.11.2, I hope this will be nice, there is various new facilities there to short out the problems for windows bugs fixing ,and will upgrade it too.

[ausbit]

All pools must update to produce v4 blocks by a certain time, but it doesn't have any affect on miners - as long as the pool is updated in time.   

yeah we all should update this new version of Bitcoins core 0.11.2 , its really help for the required support needed at the time of any issues. But we don't know the time of misfortune. Any thing good or bad can happen at any time. Thanks for the post. It will help us to make the future at its best. Congratulations to all the users

[lethalethereal]

I really dont know how to earn Bitcoin with this program :/

[saturn643]

I really dont know how to earn Bitcoin with this program :/

This is a wallet, not a program to earn bitcoin. You earn Bitcoin elsewhere and send it to this wallet.

[avon69]

Should try it out.

[yun9999]

Does this program require a full download of the blockchain?  I need another wallet that is light.

[saturn643]

Does this program require a full download of the blockchain?  I need another wallet that is light.

It downloads the full blockchain. If you want a light wallet I recommend you checkout Electrum or MultiBit HD

[iamluan]

thank you! 

[Rama Krishna]

Greetings

Hi I would like to run BitCoin Full node in my system.

My system Conf are as follow

4 GB Ram
500GB hard Disk
System is in very good condition
Is this is enough for the run a full node..../...Is it problem for the System running BitCoin Node

Pls let me know.....
Cheers....

[shorena]

Greetings

Hi I would like to run BitCoin Full node in my system.

My system Conf are as follow

4 GB Ram
500GB hard Disk
System is in very good condition
Is this is enough for the run a full node..../...Is it problem for the System running BitCoin Node

Pls let me know.....
Cheers....

Ram and disk space is enough, if you have a slow CPU or internet connection syncing might take some time. I suggest you just give it a try and see how it goes. The initial sync might take a few days. Thats enough time to see if the system can handle it, before you use it as your actual wallet.

[James100t]

Good to know this.Useful blog for all.Good job Mr.HostFat. Thanks you very much for this.

[Smita]

do you guys advice me to upgrade to 0.11.2 or should i stick to 0.10.2 ?

[shorena]

do you guys advice me to upgrade to 0.11.2 or should i stick to 0.10.2 ?

Upgrade if not to 0.11.2 at least to 0.10.3 -> https://bitcoin.org/bin/bitcoin-core-0.10.3/

[Lethn]

I don't know how it's working for everybody else, but this new version is absolutely fantastic for me at least. Everything is loading up a lot faster so I don't have to worry about restarting my PC and having to wait forever for the blocks to verify or the wallet crashing while it's verifying if I'm doing something else.

Good work devs! Now let's hope you can solve the blocksize problem as well and give the central bankers a kick in the crotch!

[bitstampclone]

Great to hear this latest bitcoin core version. Definitely this new version make some best advantage while comparing with older version.

[Laviathon]

do you guys advice me to upgrade to 0.11.2 or should i stick to 0.10.2 ?

So far 0.11.2 has been bullet proof for me.  After running it for a month or so now I have had 0 crashes.  What everyone else is saying is absolutely true also, loads so much quicker.

[Mikestang]

I have had a couple crashes with 0.11.2, twice now I have had to rebuild the entire block chain.  I wish there was some way it could isolate just "the bad part" of the chain when a crash happens rather than taking a week to resync the whole thing.

[Za1n]

Updated both a Windows and Linux Mint installation to 0.11.2 and both are working great so far. Had to move the block-chain folder off the SSD boot drives to 1 TB spinners I added on both machines as well. I am trying to be proactive to get in front of the growth seeing how it has jumped in the past few months.

[MAX99]

How to upgrade to 0.11.2?

I'm running ubuntu and have following the instructions here https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin.

However when I restart the bitcoin core application I'm still at the older version.

[shorena]

How to upgrade to 0.11.2?

I'm running ubuntu and have following the instructions here https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin.

However when I restart the bitcoin core application I'm still at the older version.

Code:

sudo apt-get update
sudo apt-get upgrade

should do it.

[MAX99]

Code:

sudo apt-get update
sudo apt-get upgrade

should do it.

I ran both commands but unfortunately I'm still at the old version, when I start bitcoin core it still says I'm on 10.2

[shorena]

Code:

sudo apt-get update
sudo apt-get upgrade

should do it.

I ran both commands but unfortunately I'm still at the old version, when I start bitcoin core it still says I'm on 10.2

What does

Code:

cat /etc/apt/sources.list

show?

[mjp80]

I am new user here and don't understand about it what is the use of this software can anyone tell me in simple explanation about it ?

[shorena]

I am new user here and don't understand about it what is the use of this software can anyone tell me in simple explanation about it ?

Bitcoin core is the reference implementation for bitcoin. Its the software that makes bitcoin possible as it provides the network for transactions and blocks.

[Mikestang]

I have had a couple crashes with 0.11.2, twice now I have had to rebuild the entire block chain.  I wish there was some way it could isolate just "the bad part" of the chain when a crash happens rather than taking a week to resync the whole thing.

My core finally finished resyninc on Friday, again, and then it crashed this morning and now has to resync... again!  Holy crap this is frustrating.  All 50gigs of the block chain cannot be corrupted, I don't understand why the software can't just replace the bad piece of data rather than having to sync the whole chain...

[saturn643]

I have had a couple crashes with 0.11.2, twice now I have had to rebuild the entire block chain.  I wish there was some way it could isolate just "the bad part" of the chain when a crash happens rather than taking a week to resync the whole thing.

My core finally finished resyninc on Friday, again, and then it crashed this morning and now has to resync... again!  Holy crap this is frustrating.  All 50gigs of the block chain cannot be corrupted, I don't understand why the software can't just replace the bad piece of data rather than having to sync the whole chain...

Because it doesn't know where the bad piece of data is. The crash makes it unable to read the database, and since it can't read the database, it has to rebuild the whole thing.

[Mikestang]

Because it doesn't know where the bad piece of data is. The crash makes it unable to read the database, and since it can't read the database, it has to rebuild the whole thing.

And that's my complaint, it should be able to pin down the error to a specific block or something.  Having 1 small error corrupt 50 gigs of data requiring it to all be downloaded again is terrible design, there should be a better way to code it.

[shorena]

Because it doesn't know where the bad piece of data is. The crash makes it unable to read the database, and since it can't read the database, it has to rebuild the whole thing.

And that's my complaint, it should be able to pin down the error to a specific block or something.  Having 1 small error corrupt 50 gigs of data requiring it to all be downloaded again is terrible design, there should be a better way to code it.

Its not the 50GB that are corrupted and you dont need to redownload anything.

[Mikestang]

Its not the 50GB that are corrupted and you dont need to redownload anything.

Uh, what?  Once the blockchain is corrupt core has to redownload the whole thing again.  I actually have to delete everything in my bitcoin folder or core simply crashes right away again.  Provide some explanation for your statement, please.

[shorena]

Its not the 50GB that are corrupted and you dont need to redownload anything.

Uh, what?  Once the blockchain is corrupt core has to redownload the whole thing again.  I actually have to delete everything in my bitcoin folder or core simply crashes right away again.  Provide some explanation for your statement, please.

Its more common that not the actual block files are corrupted but rather the database. If the blockfiles are corrupted you can usually delete the file in question to avoid redownloading everything. Which file is corrupted can be found in the debug.log. At least thats the overal experience from users reporting in tech support, its certainly possible that your case is different, but I guess you just deleted all files without trying other options first.

[Mikestang]

Its more common that not the actual block files are corrupted but rather the database. If the blockfiles are corrupted you can usually delete the file in question to avoid redownloading everything. Which file is corrupted can be found in the debug.log. At least thats the overal experience from users reporting in tech support, its certainly possible that your case is different, but I guess you just deleted all files without trying other options first.

Thanks for the additional explanation, I didn't know the debug.log would show the corrupted file.  When core crashes on me there is no indication in the log at all what happened, it always looks like the program is running fine if you just looked at the debug log, but next time corruption strikes I'll try your method, thanks.

[shorena]

Its more common that not the actual block files are corrupted but rather the database. If the blockfiles are corrupted you can usually delete the file in question to avoid redownloading everything. Which file is corrupted can be found in the debug.log. At least thats the overal experience from users reporting in tech support, its certainly possible that your case is different, but I guess you just deleted all files without trying other options first.

Thanks for the additional explanation, I didn't know the debug.log would show the corrupted file.  When core crashes on me there is no indication in the log at all what happened, it always looks like the program is running fine if you just looked at the debug log, but next time corruption strikes I'll try your method, thanks.

If there is no entry in the debug.log you might have to look at OS log files to find the reason for the crash. Lets hope its not needed.

[MAX99]

Code:

sudo apt-get update
sudo apt-get upgrade

should do it.

I ran both commands but unfortunately I'm still at the old version, when I start bitcoin core it still says I'm on 10.2

What does

Code:

cat /etc/apt/sources.list

show?

Hi shorena I ran a ubuntu software update and it updated the bitcoin core to 11.2, thanks for you assistance

[brain brain]

Hi forum,
My Bitcoin Core v.11 is stuck at 269069 blocks and hasn't updated in 18 hours, despite upgrading from v.09 to v.10 to v.11 on the same machine in the past 18 hours.  It's an older machine that I've been upgrading to keep as part of supporting the Bitcoin Network, which I believe in as a consumer and a technology advocate.

I've restarted Bitcoin Core v.11 many times, restarted the entire computer multiple times...I can't seen to get it to continue to update past blocks after block 269069 which is like 2.25 years ago...

Help!

==Brain brain

[brain brain]

Hi all,
I'm currently reindexing using

/Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -reindex

and will see how that goes.  Should take about 12 hours but that'll give me time to cure this hangover...

Any other ideas to speed it up would be appreciated, or any other tips to not have this problem again!!!  (not the hangover)

==brain brain

Hi forum,
My Bitcoin Core v.11 is stuck at 269069 blocks and hasn't updated in 18 hours, despite upgrading from v.09 to v.10 to v.11 on the same machine in the past 18 hours.  It's an older machine that I've been upgrading to keep as part of supporting the Bitcoin Network, which I believe in as a consumer and a technology advocate.

I've restarted Bitcoin Core v.11 many times, restarted the entire computer multiple times...I can't seen to get it to continue to update past blocks after block 269069 which is like 2.25 years ago...

Help!

==Brain brain

[Mikestang]

If there is no entry in the debug.log you might have to look at OS log files to find the reason for the crash. Lets hope its not needed.

Hopefully not, it's almost done syncing the blockchain... again...

Funny thing it, core crashes very rarely while it's syncing, crashes much more often when it's up and running up-to-date.  And never has a crash while syncing resulted in a corrupted file.

[ekoice]

Code:

sudo apt-get update
sudo apt-get upgrade

should do it.

I ran both commands but unfortunately I'm still at the old version, when I start bitcoin core it still says I'm on 10.2

What does

Code:

cat /etc/apt/sources.list

show?

Hi shorena I ran a ubuntu software update and it updated the bitcoin core to 11.2, thanks for you assistance

I do agree that updates and new versions are always better with smart and smooth ways of operations but I need to know more about how to update this and what is the benefit of this new version of Bitcoin.

[shorena]

-snip-
I need to know more about how to update this and what is the benefit of this new version of Bitcoin.

The change log from 0.11.1 to 0.11.2 is in the OP. Which core version do you run currently and what do you use it for?

[srinikethan]

This is a new minor version release, bringing bug fixes, the BIP65 (CLTV) consensus change, and relay policy preparation for BIP113. It is recommended to upgrade to this version as soon as possible.

[vane91]

Bitcoin core needs a serious overhaul in order to get it working smooth since the 0.10 version I have stopped using because of all the crashes and massive amounts of data downloaded. Maybe when they re work it to run smooth without crashes and works with far less data to download then maybe I might just start using Bitcoin Core or client once again.

This crashes are mostly due to hard disk failure like it's full or a corrupt sector. Running out of memory can also crash it.

I'm actually waiting for a lite option on the software installer, that connect to other peers to get the info and just keep the latest x blocks. That would be great, i don't care about privacy or sybil attacks because no-one is sending me coins, just myself.

[Mikestang]

I'm actually waiting for a lite option on the software installer, that connect to other peers to get the info and just keep the latest x blocks. That would be great, i don't care about privacy or sybil attacks because no-one is sending me coins, just myself.

Pruned mode is available, and I think that will do what you are looking for.  Otherwise you'll have to look at other "lightweight" wallets, because core really needs the full blockchain and peer connections to function at its full potential and to work as a full node (which is why most people run it, at least why I do).

[HostFat]

Bitcoin Core version 0.12.0 released
https://bitcointalk.org/index.php?topic=1374377.0

[Mikestang]

Bitcoin Core version 0.12.0 released
https://bitcointalk.org/index.php?topic=1374377.0

I had to go back to using 0.11.2 after "upgrading" to 0.12 caused core to always crash at the loading screen.  More details here: https://bitcointalk.org/index.php?topic=1374377.msg14018039#msg14018039