Bitcoin Core version 0.12.1 released

[tuvok007]

I"ll just try the new version and see if it is faster in syncing

Again, you don't have to 'try to see' anything. 0.12 and 0.12.1 should sync equally fast as there are no improvements in that area between those two versions.

Ok,I understand now tnx!

[DanDan]

It's still too slow to open and slower to verify blocks. They haven't solved this issue yet, it's been a long time.
Regular users can't use this program as a wallet, even though it's the most secure, it's not suitable for daily use.

[Lauda]

It's still too slow to open and slower to verify blocks. They haven't solved this issue yet, it's been a long time.

This depends on your configuration. I don't see this as an issue, especially not one that could be 'solved' easily.

Regular users can't use this program as a wallet, even though it's the most secure, it's not suitable for daily use.

The wallet was not designed for the average user. This is why there are lightweight clients.

[dumbfbrankings]

This April segwit release seems to be running really smoothly.

There has been no Segwit release yet, what are you talking about? This version does not contain Segwit.

I red that segwit was already running fine on testnet for months and was going to be coming in april so I taught this release wood halve it. Does Bitcoin Team do more than one client release in april?

Sorry for confucions.

[thejaytiesto]

It's still too slow to open and slower to verify blocks. They haven't solved this issue yet, it's been a long time.

This depends on your configuration. I don't see this as an issue, especially not one that could be 'solved' easily.

Regular users can't use this program as a wallet, even though it's the most secure, it's not suitable for daily use.

The wallet was not designed for the average user. This is why there are lightweight clients.

But ideally, we should encourage the average user to run nodes too. If you make a software having in mind only a small niche of people, it will never have tons of users.

I think we could achieve something that is attractive for the average user, that at the same time runs a node. Then you can unlock a "power user" mode with tons of extra options. But we must somehow get more and more people running nodes, this is the #1 priority to keep Bitcoin healthy.

[achow101]

I red that segwit was already running fine on testnet for months and was going to be coming in april so I taught this release wood halve it.

It has been running fine in its own test network (segnet) for several months, but it has not actually been deployed on testnet yet.

Does Bitcoin Team do more than one client release in april?

Probably not.

[shorena]

-snip-

Regular users can't use this program as a wallet, even though it's the most secure, it's not suitable for daily use.

The wallet was not designed for the average user. This is why there are lightweight clients.

But ideally, we should encourage the average user to run nodes too. If you make a software having in mind only a small niche of people, it will never have tons of users.

I think we could achieve something that is attractive for the average user, that at the same time runs a node. Then you can unlock a "power user" mode with tons of extra options. But we must somehow get more and more people running nodes, this is the #1 priority to keep Bitcoin healthy.

The current number of nodes is perfectly fine, but why do you think that "regular users" cant run bitcoin core?

[Lauda]

The current number of nodes is perfectly fine, but why do you think that "regular users" cant run bitcoin core?

Well, I would say that the 'average user' can't bother with downloading so much data in addition to the constant need to sync and waiting when opening the wallet. I know a lot of people but only a few use Core like myself.

[Carlton Banks]

Well, all I can say is that the above posts in respect of regular users running a full node as a wallet: thank god the blocksize isn't increasing.

Just another 18-24 months could make a huge difference in perception of how much of a burden it is downloading the ~75GB blockchain. "Fibre to the premises" domestic connections and 4G/LTE cellular networks are still in a state of low rollout across the areas where Bitcoin use is popular. And once regular people in those places consider FTTP/LTE as normal, they'll be saying "100GB? That'll take a few hours, but I guess it might be worth it".

[vinaha]

I just want to point out (I don't think it's been mentioned in this thread) that for upgrading you don't need to synchronize the whole blockchain again. It uses the blockchain files you already had before updating. 

[shorena]

The current number of nodes is perfectly fine, but why do you think that "regular users" cant run bitcoin core?

Well, I would say that the 'average user' can't bother with downloading so much data in addition to the constant need to sync and waiting when opening the wallet. I know a lot of people but only a few use Core like myself.

In this case youtube or netflix isnt for the 'average user' either. Anyway, I was hoping for a statement of thejaytiesto since they seemed to have something in mind that should be done.

[Lauda]

In this case youtube or netflix isnt for the 'average user' either.

I disagree. You don't have to wait for any types of synchronization time nor wait while loading the videos (unless you have a really bad connection).

Anyway, I was hoping for a statement of thejaytiesto since they seemed to have something in mind that should be done.

I don't see much that can be done though. Even if Core added a SPV mode it seems rather redundant as there are a few SPV wallets as well.

[Mikestang]

Anyone using XP and know if 0.12.1 fixes the crashing issue present in 0.12.0?

The problem is XP. There are known problems with 0.12 with XP. See https://github.com/bitcoin/bitcoin/issues/7674 and https://github.com/bitcoin/bitcoin/issues/7639. However i don't think it will be fixed since XP support from Microsoft has ended and thus fixing an XP only problem is not worth it to the core devs. See https://github.com/bitcoin/bitcoin/issues/7681 for the discussion about that.

So v0.12 is a total bust for me.  It crashed once more and I cannot get it to start up no matter what.  It sometimes makes it to "checking addresses" on the loading screen, but never any further.  Sometimes it crashes as soon as the loading screen appears.  I went back to 0.11.2 and it loads just find so it is a bug specific to 0.12.

Here are a few of my logs from the crashes, you can see the program just stops with no indication of any sort of error.

Code:

2016-02-26 15:14:47 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100)
2016-02-26 15:14:47 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-02-26 15:14:47 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2016-02-26 15:14:48 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-02-26 15:14:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-02-26 15:14:48 Default data directory [editted out]
2016-02-26 15:14:48 Using data directory [editted out]
2016-02-26 15:14:48 Using config file [editted out]
2016-02-26 15:14:48 Using at most 125 connections (2048 file descriptors available)
2016-02-26 15:14:48 Using 2 threads for script verification
2016-02-26 15:14:48 Using wallet wallet.dat
2016-02-26 15:14:48 scheduler thread start
2016-02-26 15:14:48 init message: Verifying wallet...
2016-02-26 15:14:48 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out]
2016-02-26 15:14:48 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used.  (10047))
2016-02-26 15:14:48 Bound to 0.0.0.0:8333
2016-02-26 15:14:48 Cache configuration:
2016-02-26 15:14:48 * Using 2.0MiB for block index database
2016-02-26 15:14:48 * Using 32.5MiB for chain state database
2016-02-26 15:14:48 * Using 65.5MiB for in-memory UTXO set
2016-02-26 15:14:48 init message: Loading block index...
2016-02-26 15:14:48 Opening LevelDB in [editted out]
2016-02-26 15:14:48 Opened LevelDB successfully
2016-02-26 15:14:48 Using obfuscation key for [editted out]: 0000000000000000
2016-02-26 15:14:48 Opening LevelDB in [editted out]
2016-02-26 15:14:48 Opened LevelDB successfully
2016-02-26 15:14:48 Using obfuscation key for [editted out]: 72046a1e7622fad5
2016-02-26 15:14:57 LoadBlockIndexDB: last block file = 197
2016-02-26 15:14:57 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=365, size=131274522, heights=330521...330993, time=2014-11-18...2014-11-21)
2016-02-26 15:14:57 Checking all blk files are present...
2016-02-26 15:14:58 LoadBlockIndexDB: transaction index disabled
2016-02-26 15:14:58 LoadBlockIndexDB: hashBestChain=00000000000000001639f0ef7eb082b57e48f33baeb9082a7ab07ef3ef7df130 height=330922 date=2014-11-21 00:37:07 progress=0.450084
2016-02-26 15:14:58 init message: Verifying blocks...
2016-02-26 15:14:58 Verifying last 288 blocks at level 3
2016-02-26 15:15:14 No coin database inconsistencies in last 36 blocks (26535 transactions)
2016-02-26 15:15:14  block index           26188ms
2016-02-26 15:15:14 init message: Loading wallet...
2016-02-26 15:15:15 nFileVersion = 120000
2016-02-26 15:15:15 Keys: 0 plaintext, 265 encrypted, 265 w/ metadata, 265 total
2016-02-26 15:15:15  wallet                  281ms
2016-02-26 15:15:15 init message: Activating best chain...
2016-02-26 15:15:16 UpdateTip: new best=000000000000000012e7c144fc1c1038c2e7826033b8c9739e5e690b8bf40b91  height=330923  log2_work=81.519843  tx=51953838  date=2014-11-21 00:49:03 progress=0.450093  cache=0.4MiB(1228tx)
2016-02-26 15:15:19 UpdateTip: new best=00000000000000001acb1484131a0b69c7666e1a9b94e483babae59adf1fe160  height=330924  log2_work=81.519915  tx=51954895  date=2014-11-21 01:02:32 progress=0.450110  cache=15.2MiB(4216tx)
2016-02-26 15:15:22 UpdateTip: new best=000000000000000005357156756d6576017e084a6ad8505fd2721feb79773b6c  height=330925  log2_work=81.519987  tx=51956910  date=2014-11-21 01:56:55 progress=0.450152  cache=17.7MiB(8185tx)
2016-02-26 15:15:24 UpdateTip: new best=00000000000000001062194213863dab2ef62cb1f7715329927c6d24dc0dc0fd  height=330926  log2_work=81.520059  tx=51957644  date=2014-11-21 01:57:29 progress=0.450160  cache=21.0MiB(9680tx)
2016-02-26 15:15:26 UpdateTip: new best=00000000000000000a99e0837981a3ffb45b20b14a4f30e6be51eb014a69a850  height=330927  log2_work=81.520131  tx=51959086  date=2014-11-21 02:14:09 progress=0.450182  cache=22.4MiB(11784tx)
2016-02-26 15:15:29 UpdateTip: new best=0000000000000000178e4ae780a4e48f28c1cf6e061167b92e3ee1f75e166a37  height=330928  log2_work=81.520203  tx=51960689  date=2014-11-21 02:40:51 progress=0.450210  cache=25.6MiB(14222tx)
2016-02-26 15:15:29 mapBlockIndex.size() = 400090
2016-02-26 15:15:29 nBestHeight = 330928
2016-02-26 15:15:29 setKeyPool.size() = 98
2016-02-26 15:15:29 mapWallet.size() = 307
2016-02-26 15:15:29 mapAddressBook.size() = 64
2016-02-26 15:15:29 init message: Loading addresses...
2016-02-26 15:15:29 torcontrol thread start
2016-02-26 15:15:29 ERROR: Read: Failed to open file [editted out]
2016-02-26 15:15:29 Invalid or missing banlist.dat; recreating
2016-02-26 15:15:29 Loaded 158 addresses from peers.dat  32ms

Code:

2016-02-26 15:11:32 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100)
2016-02-26 15:11:32 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-02-26 15:11:32 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2016-02-26 15:11:33 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-02-26 15:11:33 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-02-26 15:11:33 Default data directory [editted out]
2016-02-26 15:11:33 Using data directory [editted out]
2016-02-26 15:11:33 Using config file [editted out]
2016-02-26 15:11:33 Using at most 125 connections (2048 file descriptors available)
2016-02-26 15:11:33 Using 2 threads for script verification
2016-02-26 15:11:33 Using wallet wallet.dat
2016-02-26 15:11:33 init message: Verifying wallet...
2016-02-26 15:11:33 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out]
2016-02-26 15:11:37 

Code:

2016-02-26 15:11:37 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100)
2016-02-26 15:11:37 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-02-26 15:11:38 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2016-02-26 15:11:39 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-02-26 15:11:39 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-02-26 15:11:39 Default data directory [editted out]
2016-02-26 15:11:39 Using data directory [editted out]
2016-02-26 15:11:39 Using config file [editted out]
2016-02-26 15:11:39 Using at most 125 connections (2048 file descriptors available)
2016-02-26 15:11:39 Using 2 threads for script verification
2016-02-26 15:11:39 Using wallet wallet.dat
2016-02-26 15:11:39 init message: Verifying wallet...
2016-02-26 15:11:39 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out]
2016-02-26 15:11:39 scheduler thread start
2016-02-26 15:11:39 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used.  (10047))
2016-02-26 15:11:39 Bound to 0.0.0.0:8333
2016-02-26 15:11:39 Cache configuration:
2016-02-26 15:11:39 * Using 2.0MiB for block index database
2016-02-26 15:11:39 * Using 32.5MiB for chain state database
2016-02-26 15:11:39 * Using 65.5MiB for in-memory UTXO set
2016-02-26 15:11:39 init message: Loading block index...
2016-02-26 15:11:39 Opening LevelDB in [editted out]
2016-02-26 15:11:39 Opened LevelDB successfully
2016-02-26 15:11:39 Using obfuscation key for [editted out]: 0000000000000000
2016-02-26 15:11:39 Opening LevelDB in [editted out]
2016-02-26 15:11:39 Opened LevelDB successfully
2016-02-26 15:11:39 Using obfuscation key for [editted out]: 72046a1e7622fad5
2016-02-26 15:11:48 LoadBlockIndexDB: last block file = 197
2016-02-26 15:11:48 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=365, size=131274522, heights=330521...330993, time=2014-11-18...2014-11-21)
2016-02-26 15:11:48 Checking all blk files are present...
2016-02-26 15:11:48 LoadBlockIndexDB: transaction index disabled
2016-02-26 15:11:48 LoadBlockIndexDB: hashBestChain=00000000000000001639f0ef7eb082b57e48f33baeb9082a7ab07ef3ef7df130 height=330922 date=2014-11-21 00:37:07 progress=0.450085
2016-02-26 15:11:48 init message: Verifying blocks...
2016-02-26 15:11:48 Verifying last 288 blocks at level 3
2016-02-26 15:12:05 No coin database inconsistencies in last 36 blocks (26535 transactions)
2016-02-26 15:12:05  block index           25562ms
2016-02-26 15:12:05 init message: Loading wallet...
2016-02-26 15:12:05 nFileVersion = 120000
2016-02-26 15:12:05 Keys: 0 plaintext, 265 encrypted, 265 w/ metadata, 265 total
2016-02-26 15:12:05  wallet                  203ms
2016-02-26 15:12:05 init message: Activating best chain...
2016-02-26 15:12:06 UpdateTip: new best=000000000000000012e7c144fc1c1038c2e7826033b8c9739e5e690b8bf40b91  height=330923  log2_work=81.519843  tx=51953838  date=2014-11-21 00:49:03 progress=0.450095  cache=0.4MiB(1228tx)
2016-02-26 15:12:08 UpdateTip: new best=00000000000000001acb1484131a0b69c7666e1a9b94e483babae59adf1fe160  height=330924  log2_work=81.519915  tx=51954895  date=2014-11-21 01:02:32 progress=0.450111  cache=15.2MiB(4216tx)
2016-02-26 15:12:11 UpdateTip: new best=000000000000000005357156756d6576017e084a6ad8505fd2721feb79773b6c  height=330925  log2_work=81.519987  tx=51956910  date=2014-11-21 01:56:55 progress=0.450153  cache=17.7MiB(8185tx)
2016-02-26 15:12:13 UpdateTip: new best=00000000000000001062194213863dab2ef62cb1f7715329927c6d24dc0dc0fd  height=330926  log2_work=81.520059  tx=51957644  date=2014-11-21 01:57:29 progress=0.450161  cache=21.0MiB(9680tx)
2016-02-26 15:12:15 UpdateTip: new best=00000000000000000a99e0837981a3ffb45b20b14a4f30e6be51eb014a69a850  height=330927  log2_work=81.520131  tx=51959086  date=2014-11-21 02:14:09 progress=0.450183  cache=22.4MiB(11784tx)
2016-02-26 15:12:17 UpdateTip: new best=0000000000000000178e4ae780a4e48f28c1cf6e061167b92e3ee1f75e166a37  height=330928  log2_work=81.520203  tx=51960689  date=2014-11-21 02:40:51 progress=0.450211  cache=25.6MiB(14222tx)
2016-02-26 15:12:17 mapBlockIndex.size() = 400090
2016-02-26 15:12:17 nBestHeight = 330928
2016-02-26 15:12:17 setKeyPool.size() = 98
2016-02-26 15:12:17 mapWallet.size() = 307
2016-02-26 15:12:17 mapAddressBook.size() = 64
2016-02-26 15:12:17 torcontrol thread start
2016-02-26 15:12:53 

[bloom08]

congrats for releasing a new version..

[Mikestang]

Anyone using XP and know if 0.12.1 fixes the crashing issue present in 0.12.0?

Well I tried 0.12.1 and the XP crash is still there, so I guess this means that XP will not be supported by bitcoin core past 0.11.2.

[Lauda]

Anyone using XP and know if 0.12.1 fixes the crashing issue present in 0.12.0?

As far as I know XP is no longer supported. However, I'm not 100% sure of this. Someone else would have to confirm.

[Carlton Banks]

Anyone using XP and know if 0.12.1 fixes the crashing issue present in 0.12.0?

As far as I know XP is no longer supported. However, I'm not 100% sure of this. Someone else would have to confirm.

I think a "drop XP support" issue was opened at github.com/bitcoin/bitcoin, not sure what the outcome was right now.

[ecashpay123]

dear sir please tell me how to use this bitcoin core.I have no idea becuase its first time for me to use this.please tell me tips about how to use this and earn money.

[Lauda]

dear sir please tell me how to use this bitcoin core.I have no idea becuase its first time for me to use this.please tell me tips about how to use this and earn money.

You just install the software and run it. You can't use Core to earn any kind of money. That is not the way that it works.

[Twilight Equinox]

Trying it out right now. So far don't see any obvious bugs.