Bitcoin Core 0.14.1 Released

[masterbt]

I am upgrading from 0.8 to new version. Already downloaded 35 Gb's, Still more blocks left. Is it absolutely necessary to download all blocks.

 is it safe to activate prune? how much data size will be, when in prune mode?

[Meuh6879]

from 500Mb to 140Gb.

[Amph]

so i'm struggling to get my coins back, there anything that i can do to reverse the transaction and send it again with proper fee? i tried with abandon but it don't work

i need something like -zapwallettxes but that work with prune mode, i can't redownload the entire blockchain now, because i have no space currently i have some games installed

[masterbt]

from 500Mb to 140Gb.

Are you saying this size for prune mode? Also, it is very slow today for the blockchain downloading.

[Meuh6879]

Yes.

https://bitcoincore.org/en/releases/0.12.0/

With 0.12 it is possible to use wallet functionality in pruned mode.
This can reduce the disk usage from currently around 60 GB to around 2 GB.

However, rescans as well as the RPCs importwallet, importaddress, importprivkey are disabled.

To enable block pruning set prune=<N> on the command line or in bitcoin.conf,
where N is the number of MiB to allot for raw block & undo data.

A value of 0 disables pruning. The minimal value above 0 is 550.

Your wallet is as secure with high values as it is with low ones. Higher values merely ensure that your node will not shut down upon blockchain reorganizations of more than 2 days - which are unlikely to happen in practice. In future releases, a higher value may also help the network as a whole: stored blocks could be served to other nodes.

For further information about pruning, you may also consult the release notes of v0.11.0.

[flappycoinrevive]

I recently started a bitcoin node to support the network. I opened the port 8333 on my router and have set my firewall to accept incoming connections from my bitcoin client, but It still doesn't show any incoming connections. I even visited the bitcode page to check my node status and it states that it is inaccessible. Please help!

[yohananaomi]

I also do not really understand about all that, if all those things can be useful I will also do that. And of course I will also ask because I also do not know it yet
Thank you

Same as you, i am currently only listening first, because i am still new to something like this, although i have tried to download bitcoin-0.14.1-win32-setup samai is done. But there are still obstacles where the program does not arise in the computer.
Therefore I try again and see the others. thank you

[Meuh6879]

use primary download site : https://bitcoin.org/bin/

[Quietstorm]

Hey guys, I am new and was looking for something for CPU mining.


Why we can't use this new version for mining?

[-ck]

Hey guys, I am new and was looking for something for CPU mining.


Why we can't use this new version for mining?

Because bitcoin mining difficulty is so high that CPU mining isn't even guaranteed to solve one block on average before the end of the known universe. We don't want to encourage people to waste time and energy doing something completely futile and furthermore encourage them to create illegal botnets stealing power for something futile (that's usually why people ask about CPU mining.)

[Meuh6879]

Why we can't use this new version for mining?

GPU card = 400w = 35MH/s
GekkoScience ASIC USB = 10w = 10 000 MH/s
CPU = 190w = 2MH/s
Cheap ASIC USB = 5w = 333 MH/s

so, you can mine with an USB key that it contain 1 ASIC chip. 

[Icon]

Why we can't use this new version for mining?

GPU card = 400w = 35MH/s
GekkoScience ASIC USB = 10w = 10 000 MH/s
CPU = 190w = 2MH/s
Cheap ASIC USB = 5w = 333 MH/s

so, you can mine with an USB key that it contain 1 ASIC chip. 

lol i got 69 of those 333 mh/s if anyone is interested

Icon

[Amph]

Why we can't use this new version for mining?

GPU card = 400w = 35MH/s
GekkoScience ASIC USB = 10w = 10 000 MH/s
CPU = 190w = 2MH/s
Cheap ASIC USB = 5w = 333 MH/s

so, you can mine with an USB key that it contain 1 ASIC chip. 

uh where those number come from? a 1080 can do 1giga, and consume less than 200watt, that number are surely based on old gpu or they are wrong as fuck

still useless to mine but at least with a farm you can expect something, with 1000 gpu you have one tera already, not going to match the asic but still relevant at least

[romanPolansky00]

hi all!!!
this wallet version seem to have a fee calculator.
there are other wallets who give you the right fee to confirm transaction in 1H or less?

[johndoe784r]

...not just to enforce the rules, but to get the extra privacy and security you get when using the blockchain directly...

Good Evening Carlton Banks,

I am fairly well informed but perhaps you could elaborate further. Could you please explain how one goes about using the blockchain directly, not only for me but also for those listening/watching/reading but also for the benefit of future lurkers/searchers of these forums.

Especially interested in the privacy and security part. These are messed up times...

Thanks in advance,

-jd

[Carlton Banks]

@jd

just install and run Bitcoin Core, then your Bitcoin Core node will add another brick of strength to Satoshi's Fortress of rules (or another watt to Satoshi's cryptographic force-field, whatever metaphor you prefer )


The privacy and security do not necessarily come for free. The best setup involves, in order:

• Most secure hardware you can get
• Most secure Operating System running on that hardware (macOS and Windows are, of course, not secure)
• Get connected to the Bitcoin network over Tor

Anyone who has anything to add to that, feel free.

[Peeter2007]

Is it possible and ok when Bitcoin core remove and dont keep some of oldest period blockchain info in PC

[johndoe784r]

@jd

The privacy and security do not necessarily come for free. The best setup involves, in order:

• Most secure hardware you can get
• Most secure Operating System running on that hardware (macOS and Windows are, of course, not secure)
• Get connected to the Bitcoin network over Tor

Thank you Carlton Banks 

[superhelper]

Bitcoin Core version 0.14.1 is now available from:

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

This is a new minor version release, including various bugfixes and performance improvements, as well as updated translations.

Please report bugs using the issue tracker at github:

https://github.com/bitcoin/bitcoin/issues

To receive security and update notifications, please subscribe to:

https://bitcoincore.org/en/list/announcements/join/

Compatibility

Bitcoin Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later.

Microsoft ended support for Windows XP on April 8th, 2014, No attempt is made to prevent installing or running the software on Windows XP, you can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker.

Bitcoin Core should also work on most other Unix-like systems but is not frequently tested on them.

Notable changes
RPC changes

• The first positional argument of createrawtransaction was renamed from   transactions to inputs.
  
• The argument of disconnectnode was renamed from node to address.
  

These interface changes break compatibility with 0.14.0, when the named arguments functionality, introduced in 0.14.0, is used. Client software using these calls with named arguments needs to be updated.

Mining

In previous versions, getblocktemplate required segwit support from downstream clients/miners once the feature activated on the network. In this version, it now supports non-segwit clients even after activation, by removing all segwit transactions from the returned block template. This allows non-segwit miners to continue functioning correctly even after segwit has activated.

Due to the limitations in previous versions, getblocktemplate also recommended non-segwit clients to not signal for the segwit version-bit. Since this is no longer an issue, getblocktemplate now always recommends signalling segwit for all miners. This is safe because ability to enforce the rule is the only required criteria for safe activation, not actually producing segwit-enabled blocks.

UTXO memory accounting

Memory usage for the UTXO cache is being calculated more accurately, so that the configured limit (-dbcache) will be respected when memory usage peaks during cache flushes.  The memory accounting in prior releases is estimated to only account for half the actual peak utilization.

The default -dbcache has also been changed in this release to 450MiB.  Users who currently set -dbcache to a high value (e.g. to keep the UTXO more fully cached in memory) should consider increasing this setting in order to achieve the same cache performance as prior releases.  Users on low-memory systems (such as systems with 1GB or less) should consider specifying a lower value for this parameter.

Additional information relating to running on low-memory systems can be found here: reducing-bitcoind-memory-usage.md.

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

RPC and other APIs

• #10084 142fbb2 Rename first named arg of createrawtransaction (MarcoFalke)
  
• #10139 f15268d Remove auth cookie on shutdown (practicalswift)
  
• #10146 2fea10a Better error handling for submitblock (rawodb, gmaxwell)
  
• #10144 d947afc Prioritisetransaction wasn't always updating ancestor fee (sdaftuar)
  
• #10204 3c79602 Rename disconnectnode argument (jnewbery)
  

Block and transaction handling

• #10126 0b5e162 Compensate for memory peak at flush time (sipa)
  
• #9912 fc3d7db Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
  
• #10133 ab864d3 Clean up calculations of pcoinsTip memory usage (morcos)
  

P2P protocol and network code

• #9953/#10013 d2548a4 Fix shutdown hang with >= 8 -addnodes set (TheBlueMatt)
  
• #10176 30fa231 net: gracefully handle NodeId wrapping (theuni)
  

Build system

• #9973 e9611d1 depends: fix zlib build on osx (theuni)
  

GUI

• #10060 ddc2dd1 Ensure an item exists on the rpcconsole stack before adding (achow101)
  

Mining

• #9955/#10006 569596c Don't require segwit in getblocktemplate for segwit signalling or mining (sdaftuar)
  
• #9959/#10127 b5c3440 Prevent slowdown in CreateNewBlock on large mempools (sdaftuar)
  

Tests and QA

• #10157 55f641c Fix the mempool_packages.py test (sdaftuar)
  

Miscellaneous

• #10037 4d8e660 Trivial: Fix typo in help getrawtransaction RPC (keystrike)
  
• #10120 e4c9a90 util: Work around (virtual) memory exhaustion on 32-bit w/ glibc (laanwj)
  
• #10130 ecc5232 bitcoin-tx input verification (awemany, jnewbery)
  

Credits

Thanks to everyone who directly contributed to this release:

• Alex Morcos
  
• Andrew Chow
  
• Awemany
  
• Cory Fields
  
• Gregory Maxwell
  
• James Evans
  
• John Newbery
  
• MarcoFalke
  
• Matt Corallo
  
• Pieter Wuille
  
• practicalswift
  
• rawodb
  
• Suhas Daftuar
  
• Wladimir J. van der Laan
  

As well as everyone that helped translating on Transifex.

I don't know clearly that what is the main benefit of Bitcoin Core. Please make me clear!

[Meuh6879]

I don't know clearly that what is the main benefit of Bitcoin Core. Please make me clear!

it's the base of Bitcoin network.
when others wallets have problems, Bitcoin Core don't.