Bitcoin Core 0.19.0.1 Released

[MysteryMiner]

Just recently upgraded to latest version and the US English or simply English language options are gone! Selecting Default gives me some English mixed with partially translated Latvian and best working option now is UK English.

Why there is not one option for one language? I know there is like 7+ Spanish options and English in various parts of world have different dialects. But why? And if so, why there is no at least 4 versions of Russian (for each country where Russian have official status) or U.S. East Coast, U.S. West Coast and Texass English?

[1714594974]

1714594974

[1714594974]

1714594974

[1714594974]

1714594974

[achow101]

Just recently upgraded to latest version and the US English or simply English language options are gone!

Looks like it was removed, probably accidentally. I've opened a PR to restore it.

Selecting Default gives me some English mixed with partially translated Latvian and best working option now is UK English.

Default will use your systems local language settings, which I guess is Latvian. It looks like there isn't a full Latvian translation yet, so Core will fallback to using the original English strings.

Why there is not one option for one language? I know there is like 7+ Spanish options and English in various parts of world have different dialects. But why?

Because there are multiple regional dialects. Bitcoin Core uses [Transifex](https://www.transifex.com/bitcoin/bitcoin/) for translations which allows people to translate for a ton of languages and their regional dialects. Some of those people will choose to translate for the various dialects, so those translations end up in the software.

And if so, why there is no at least 4 versions of Russian (for each country where Russian have official status) or U.S. East Coast, U.S. West Coast and Texass English?

Either because no one has bothered with translating for those dialects, or Transifex does not give those dialects as options to translate to.

[konfuzius5278]

I need to say I waited long for set Bech32 as standart adress definition in Bitcoin core and hope it will solve some problems in next hype

[Tolosi]

I am running my own full node as suggested. Can somebody explain to me why solo mining in not allowed directly from Bitcoin Core as it was possible in the early days.
I understand that it is not going to mine any blocks but the PC is already on and connected to the network - no reason not to allow solo mining and support Bitcoin at the same time.

[OmegaStarScream]

I am running my own full node as suggested. Can somebody explain to me why solo mining in not allowed directly from Bitcoin Core as it was possible in the early days.
I understand that it is not going to mine any blocks but the PC is already on and connected to the network - no reason not to allow solo mining and support Bitcoin at the same time.

Because mining using CPU/GPU won't do anything. It would be a waste of resources.

You can either buy ASIC if you want to get into mining or just continue running a full node, that helps the network as well.

[MysteryMiner]

Still, I also do not understand why the CPU mining was disabled. Users must have a choice and removing option what once was available is evil. This is exactly like removing PRIME95 stress test option because of waste of resources. Some people still have free electricity or want to use computer as a heat source.

[Tolosi]

You can either buy ASIC if you want to get into mining or just continue running a full node, that helps the network as well.

Still, I also do not understand why the CPU mining was disabled. Users must have a choice and removing option what once was available is evil. This is exactly like removing PRIME95 stress test option because of waste of resources. Some people still have free electricity or want to use computer as a heat source.

I stopped ASIC mining in 2013.

[achow101]

Still, I also do not understand why the CPU mining was disabled. Users must have a choice and removing option what once was available is evil. This is exactly like removing PRIME95 stress test option because of waste of resources. Some people still have free electricity or want to use computer as a heat source.

Because it would be dead code and dead weight in the codebase. IIRC the CPU miner got fairly complex because it was using different CPU instructions and extensions and various tricks to make computing SHA256 hashes faster. This means that it was complex. If the CPU miner was still in Core, it would still have to be maintained which adds additional burden on developers. It means that refactors are a bit harder. It means that we would needs tests for it. Because it would be consensus related, it means that people have to review it more carefully, and if there are bugs, those have to be fixed. There would be feature requests related to the miner to do things like make it support Stratum and pool mining. In general, more work is required to maintain it, but it is a feature that few, if any, people would use at all. It was eventually decided that it was not worth maintaining a feature that basically no one used, so the CPU miner was removed.

Even so, there were other mining software that had more efficient CPU miners and more mining features than Core even when it still had a miner built in. So people who wanted to CPU mine weren't using Core anyways.

[MysteryMiner]

Still, I also do not understand why the CPU mining was disabled. Users must have a choice and removing option what once was available is evil. This is exactly like removing PRIME95 stress test option because of waste of resources. Some people still have free electricity or want to use computer as a heat source.

Because it would be dead code and dead weight in the codebase. IIRC the CPU miner got fairly complex because it was using different CPU instructions and extensions and various tricks to make computing SHA256 hashes faster. This means that it was complex. If the CPU miner was still in Core, it would still have to be maintained which adds additional burden on developers. It means that refactors are a bit harder. It means that we would needs tests for it. Because it would be consensus related, it means that people have to review it more carefully, and if there are bugs, those have to be fixed. There would be feature requests related to the miner to do things like make it support Stratum and pool mining. In general, more work is required to maintain it, but it is a feature that few, if any, people would use at all. It was eventually decided that it was not worth maintaining a feature that basically no one used, so the CPU miner was removed.

Even so, there were other mining software that had more efficient CPU miners and more mining features than Core even when it still had a miner built in. So people who wanted to CPU mine weren't using Core anyways.

What if developers decide maintaining blockchain code is too much of burden and move to centralized ledger hosted on MtGox servers or vacant OneCoin database? I know this is joke but You got my point.

I am not a programmer but I have no idea why a subroutine that does not need to be touched is a burden. Just do not modify the code lines responsible for CPU mining, problem solved!

Bitcoin was goatsed in various ways in its lifetime. Worst thing that happened to Bitcoin was moving from original interface to Qt crap still making my eyes bleed today. I never successfully mined block using CPU miner in past, but I turned it on to get the idea how things happen.

[pooya87]

What if developers decide maintaining blockchain code is too much of burden and move to centralized ledger hosted on MtGox servers or vacant OneCoin database? I know this is joke but You got my point.

I am not a programmer but I have no idea why a subroutine that does not need to be touched is a burden. Just do not modify the code lines responsible for CPU mining, problem solved!

Bitcoin was goatsed in various ways in its lifetime. Worst thing that happened to Bitcoin was moving from original interface to Qt crap still making my eyes bleed today. I never successfully mined block using CPU miner in past, but I turned it on to get the idea how things happen.

you are confusing Bitcoin (the protocol) with bitcoin core (the client). there is a big difference between what the protocol defines and is a part of consensus and what kind of features a client offers.
the CPU mining was just a feature that the client had and got removed, it doesn't change anything. there is a lot of other features that bitcoin core doesn't have. if you don't like it then either use another client (ie. some other implementation of Bitcoin) or you can fork it and add the feature and maintain it yourself (or pay some programmer to do it for your use).

[TheBeardedBaby]

What is Bitcoin halving?

Every 4 year (actually every 210,000 blocks) the reward for mining a block is divided by two in other words the miners get 50% less for verifying transactions on the blockchain.
It will be reduced from 12.5 to 6.25 bitcoins per block.

[Husna QA]

What is Bitcoin halving?

Maybe the following link can give a more detailed explanation about Bitcoin halving:
https://www.bitcoinclock.com/

New bitcoins are issued by the Bitcoin network every 10 minutes. For the first four years of Bitcoin's existence, the amount of new bitcoins issued every 10 minutes was 50. Every four years, this number is cut in half. The day the amount halves is called a "halving".

Maybe you can continue the discussion about it in the following threads discussing bitcoin halving:
https://bitcointalk.org/index.php?topic=1935505.0
https://bitcointalk.org/index.php?topic=5117140.0
https://bitcointalk.org/index.php?topic=5221215.0

[Husna QA]

Previously I managed to make a signature on Console of the Bitcoin Core using the Legacy Address, but when trying with the SegWit Address the following message appears:

Code:

Address does not refer to key (code -3)

Please explain and the solution.
Thanks.

[achow101]

Previously I managed to make a signature on Console of the Bitcoin Core using the Legacy Address, but when trying with the SegWit Address the following message appears:

Code:

Address does not refer to key (code -3)

Please explain and the solution.
Thanks.

There is no solution and you cannot sign a message with a segwit address. This has been the case since segwit was introduced. See https://github.com/bitcoin/bitcoin/issues/10542

[Chikito]

I see Bitcoin core was updated to 0.19.1
https://bitcoincore.org/en/2020/03/09/release-0.19.1/

[achow101]

Bitcoin Core 0.19.1 is now available