Bitcoin Core version 0.11.2 released

[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.

[1714719603]

1714719603

[1714719603]

1714719603

[1714719603]

1714719603

[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!