Topic: Bitcoin Core version 0.11.2 released - page 3. (Read 18782 times)
I really dont know how to earn Bitcoin with this program :/
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 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.
thanks for the great work!
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.
I have gone through the post. It helps to know the features of newly developed version of Bitcoin.
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.
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.
What would this mean for pools that update? Any adverse effect for the miners on the pool?
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.
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.
updated to 0.11.2 x64
Thanks!
Thanks!
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
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. what are the advantages Bitcoin Core version 0.11.2
compared to the previous ?
?? thanks
compared to the previous ?
?? thanksOnly 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.
what are the advantages Bitcoin Core version 0.11.2
compared to the previous ? ?? thanks
compared to the previous ?
?? thanks 
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:
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:
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.
It decided it was going to rescan the whole blockchain:
Quote
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)...
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:
Quote
if (walletdb.ReadBestBlock(locator))
pindexRescan = FindForkInGlobalIndex(chainActive, 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.
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.
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.
Jump to: