Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: achow101 on April 22, 2017, 01:45:29 PM



Title: Bitcoin Core 0.14.1 Released
Post by: achow101 on April 22, 2017, 01:45:29 PM
Bitcoin Core version 0.14.1 is now available from:

https://bitcoin.org/bin/bitcoin-core-0.14.1/ (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 (https://github.com/bitcoin/bitcoin/issues)

To receive security and update notifications, please subscribe to:

https://bitcoincore.org/en/list/announcements/join/ (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 (https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), 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 (https://gist.github.com/laanwj/efe29c7661ce9b6620a7).

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 (https://www.transifex.com/projects/p/bitcoin/).


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Amph on April 28, 2017, 06:27:19 AM
i didnt notice it before but there is a way to allow remote connection based on a ip range? like 192.168.1.*, because rotation like 192.168.1.0/24 or 192.168.1.0/255.255.255.0 don't work


Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on April 28, 2017, 01:24:16 PM
i didnt notice it before but there is a way to allow remote connection based on a ip range? like 192.168.1.*, because rotation like 192.168.1.0/24 or 192.168.1.0/255.255.255.0 don't work
The 192.168.1.0/24 and 192.168.1.0/255.255.255.0 notation should work. According to the command line option help:
Quote
-rpcallowip=<ip>
Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Amph on April 29, 2017, 05:44:01 AM
i didnt notice it before but there is a way to allow remote connection based on a ip range? like 192.168.1.*, because rotation like 192.168.1.0/24 or 192.168.1.0/255.255.255.0 don't work
The 192.168.1.0/24 and 192.168.1.0/255.255.255.0 notation should work. According to the command line option help:
Quote
-rpcallowip=<ip>
Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times

why is the xxx.xxx.x.* not allowed? i understand that =* is dangerous, but the rotation with 192.168.1.* is still about private address and should not do any harm in theory, what i'm missing?


Title: Re: Bitcoin Core 0.14.1 Released
Post by: novabitz on April 29, 2017, 02:27:31 PM
Downloading it now, lets see how it goes


Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on April 29, 2017, 03:25:52 PM
i didnt notice it before but there is a way to allow remote connection based on a ip range? like 192.168.1.*, because rotation like 192.168.1.0/24 or 192.168.1.0/255.255.255.0 don't work
The 192.168.1.0/24 and 192.168.1.0/255.255.255.0 notation should work. According to the command line option help:
Quote
-rpcallowip=<ip>
Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times

why is the xxx.xxx.x.* not allowed? i understand that =* is dangerous, but the rotation with 192.168.1.* is still about private address and should not do any harm in theory, what i'm missing?
Using the * wildcard is not part of the standard CIDR notation. Core supports the standard CIDR notation and not other non-standard notation. Notation like 1xxx.xxx.xxx.* is not standard. There is no standard which defines what * means in an IP address.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: zigoter on May 09, 2017, 03:10:02 AM
can this version 0.14.1 allow the import/export the wallet HD seed yet? And if so how... :)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on May 09, 2017, 03:23:51 AM
can this version 0.14.1 allow the import/export the wallet HD seed yet? And if so how... :)
No.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: coinvest727 on May 11, 2017, 07:52:56 AM
When you sending a bitcoin, one of the two wallets produced by the bitcoin core. The send amount and the remaining amount. but one of the remaining amount has been disappeared with the coins. I am looking for someone to present a solution for this matter.




Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on May 11, 2017, 01:32:06 PM
When you sending a bitcoin, one of the two wallets produced by the bitcoin core. The send amount and the remaining amount. but one of the remaining amount has been disappeared with the coins. I am looking for someone to present a solution for this matter.
Your question is very hard to understand. Your post is off topic for this thread. Make a post in the Technical Support forum and include the transaction ids involved.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Argon2 on May 15, 2017, 01:29:07 PM
can this version 0.14.1 allow the import/export the wallet HD seed yet? And if so how... :)
Not yet. Prob should be able to export the hex representation of the seed (ecc key) and then import that to regenerate a wallet (getnewaddress to generate any used keys).


Title: Re: Bitcoin Core 0.14.1 Released
Post by: muchoman on May 15, 2017, 03:37:23 PM
Downloaded 4 days ago and i am on 52%, unbelievable, nodes must have isdn connection.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Real-Duke on May 15, 2017, 09:08:24 PM
Downloaded 4 days ago and i am on 52%, unbelievable, nodes must have isdn connection.
Did you already open Port 8333 TCP and what kind of hardware do you use?


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Amph on May 17, 2017, 05:23:27 AM
Downloaded 4 days ago and i am on 52%, unbelievable, nodes must have isdn connection.

it's note about other nodes, it's your fault, you probably have a slow ssd and connection speed, next time it's better if you save the whole blockchain as a backup, will be easy to restart the whole process



Title: Re: Bitcoin Core 0.14.1 Released
Post by: Foremast on May 22, 2017, 05:28:06 PM
Hi guys can someone explain please what is the point of downloading all of those 126gb data? i participated yesterday bitcoin core and it took just 18 hours till synch complete. if anyone interest i can create a torrent file and share the 126gb of data folder with the last synch.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: leminerale on May 23, 2017, 12:18:29 PM
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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Carlton Banks on May 23, 2017, 01:49:34 PM
When you have that 130 GB database file (also known as "the blockchain"), you're stopping people from cheating the rules of the Bitcoin system.

It's really important that people download the blockchain to use Bitcoin, not just to enforce the rules, but to get the extra privacy and security you get when using the blockchain directly. If regular people weren't running the Bitcoin blockchain, there would be no Bitcoin, and no $2000+ price. When more people use the blockchain directly (with their own +130GB copy on their computer), Bitcoin is more resilient and secure, and hence more valuable.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Ayers on May 23, 2017, 03:15:04 PM
When you have that 130 GB database file (also known as "the blockchain"), you're stopping people from cheating the rules of the Bitcoin system.

It's really important that people download the blockchain to use Bitcoin, not just to enforce the rules, but to get the extra privacy and security you get when using the blockchain directly. If regular people weren't running the Bitcoin blockchain, there would be no Bitcoin, and no $2000+ price. When more people use the blockchain directly (with their own +130GB copy on their computer), Bitcoin is more resilient and secure, and hence more valuable.

are you saying that we should avoid using prune? or maybe i misunderstand, because for now i really can't run 130gb of data that keep getting bigger each year by 50gb, you need a 1 tera ssd and they cost a lot for normal people, HDD are not an option they are too slower for other task like gaming, i don't like them anymore


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Carlton Banks on May 23, 2017, 05:21:06 PM
In reality, people can't do something that's currently out of reach for them. The ideal is to keep a full blockchain, but if you don't have the disk space at this time, sure, use prune. You're still helping to enforce Bitcoin's rules, it's just that you can't help new Bitcoin nodes onto the network to download the blockchain, as you don't have the full blockchain to upload to them.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: revelacaogr on May 24, 2017, 03:58:02 PM
When you have that 130 GB database file (also known as "the blockchain"), you're stopping people from cheating the rules of the Bitcoin system.

It's really important that people download the blockchain to use Bitcoin, not just to enforce the rules, but to get the extra privacy and security you get when using the blockchain directly. If regular people weren't running the Bitcoin blockchain, there would be no Bitcoin, and no $2000+ price. When more people use the blockchain directly (with their own +130GB copy on their computer), Bitcoin is more resilient and secure, and hence more valuable.

are you saying that we should avoid using prune? or maybe i misunderstand, because for now i really can't run 130gb of data that keep getting bigger each year by 50gb, you need a 1 tera ssd and they cost a lot for normal people, HDD are not an option they are too slower for other task like gaming, i don't like them anymore

u can use yr ssd for gaming & download and store the blockchain in an external HDD.......
https://en.bitcoin.it/wiki/Data_directory
EASY...


Title: Re: Bitcoin Core 0.14.1 Released
Post by: masterbt on May 25, 2017, 03:59:49 PM
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?



Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on May 25, 2017, 09:39:45 PM
from 500Mb to 140Gb.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Amph on May 26, 2017, 01:31:21 PM
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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: masterbt on May 26, 2017, 01:58:43 PM
from 500Mb to 140Gb.

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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on May 26, 2017, 04:13:43 PM
Yes.

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

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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: flappycoinrevive on May 27, 2017, 04:13:56 AM
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!


Title: Re: Bitcoin Core 0.14.1 Released
Post by: yohananaomi on May 27, 2017, 10:58:31 PM
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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on May 28, 2017, 04:03:51 PM
use primary download site : https://bitcoin.org/bin/


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Quietstorm on May 28, 2017, 11:03:38 PM
Hey guys, I am new and was looking for something for CPU mining.


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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: -ck on May 28, 2017, 11:10:35 PM
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.)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on May 29, 2017, 01:21:02 AM
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.  :)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Icon on May 29, 2017, 10:19:28 PM
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





Title: Re: Bitcoin Core 0.14.1 Released
Post by: Amph on May 31, 2017, 05:24:31 AM
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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: romanPolansky00 on May 31, 2017, 11:22:04 AM
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?


Title: Re: Bitcoin Core 0.14.1 Released
Post by: johndoe784r on June 01, 2017, 02:58:07 AM
...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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Carlton Banks on June 02, 2017, 04:23:45 AM
@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 :D)


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.




Title: Re: Bitcoin Core 0.14.1 Released
Post by: Peeter2007 on June 02, 2017, 11:13:22 AM
Is it possible and ok when Bitcoin core remove and dont keep some of oldest period blockchain info in PC


Title: Re: Bitcoin Core 0.14.1 Released
Post by: johndoe784r on June 03, 2017, 01:16:43 AM
@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  8)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: superhelper on June 03, 2017, 04:38:17 PM
Bitcoin Core version 0.14.1 is now available from:

https://bitcoin.org/bin/bitcoin-core-0.14.1/ (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 (https://github.com/bitcoin/bitcoin/issues)

To receive security and update notifications, please subscribe to:

https://bitcoincore.org/en/list/announcements/join/ (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 (https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), 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 (https://gist.github.com/laanwj/efe29c7661ce9b6620a7).

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 (https://www.transifex.com/projects/p/bitcoin/).


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


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 03, 2017, 05:04:21 PM
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.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Peeter2007 on June 04, 2017, 01:18:15 PM
Please next version add option to change this line -prune=<n> or someelse what user can change if need


Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on June 04, 2017, 03:32:51 PM
Please next version add option to change this line -prune=<n> or someelse what user can change if need
What are you asking for? The prune option can already be changed by the user.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 04, 2017, 03:40:32 PM
in the GUI, i think ...  ;)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Ciccotelligc on June 05, 2017, 04:36:06 PM
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

I think some wallets have the option of replacing the fee, but I'm not sure.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Peeter2007 on June 07, 2017, 01:30:49 PM
In debug window seems no work memory pool info stats in information window for me at least I use windows10


Title: Re: Bitcoin Core 0.14.1 Released
Post by: mmfiore on June 08, 2017, 03:28:52 PM
I am wondering something that concerns the bitcoin blockchain. It is over 100GB now. eventually we will not be able to run wallets on PCs because the blockchain will become to large to fit on a PC. Will the blockchain be truncated at some point?


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 08, 2017, 08:12:38 PM
how cost an 500GB SSD ... ?
nothing.

 :) solved.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: mmfiore on June 09, 2017, 05:10:16 PM
What happens when it reaches a terabyte in size. What happens when it reaches 2 and then 10 terabyte. At some point the problem is not solvable. Surely someone is working on a way to truncate the block chain or some sort of solution. What if someone new wants to get the bitcoin wallet and load it from scratch. Its going to take a 6 months to load it into the PC. This is crazy...


Title: Re: Bitcoin Core 0.14.1 Released
Post by: achow101 on June 09, 2017, 08:53:25 PM
What happens when it reaches a terabyte in size. What happens when it reaches 2 and then 10 terabyte. At some point the problem is not solvable. Surely someone is working on a way to truncate the block chain or some sort of solution. What if someone new wants to get the bitcoin wallet and load it from scratch. Its going to take a 6 months to load it into the PC. This is crazy...
First of all, technology isn't stagnant. Better computing power and storage will come even as the blockchain grows larger. There certainly are ideas for shrinking the blockchain, but they all require a hard fork and research is still being done about that.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 09, 2017, 10:54:26 PM
hint : complete local blockchain is only needed to mine (and for others tools, too).
pruning is possible since a long time on Bitcoin Core.

you can stop the local blockchain to 10GB if you want ...

http://imagizer.imageshack.us/a/img924/708/CA3SF0.png


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Peeter2007 on June 10, 2017, 01:20:42 PM
One suggest and idea.. Can add info how much data (MB or in GB) has left download if syncing


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Icon on June 10, 2017, 06:41:21 PM
hint : complete local blockchain is only needed to mine (and for others tools, too).
pruning is possible since a long time on Bitcoin Core.

you can stop the local blockchain to 10GB if you want ...

http://imagizer.imageshack.us/a/img924/708/CA3SF0.png

That's true if you only own 1 wallet, but if you keep an offline wallet/cold wallet a full node is needed that or redownload (cant resync with a prune node) the complete chain again (depending how long the wallet.dat was offline or making a new wallet.

Icon



Title: Re: Bitcoin Core 0.14.1 Released
Post by: Andre_Goldman on June 11, 2017, 10:02:25 AM
hint : complete local blockchain is only needed to mine (and for others tools, too).
pruning is possible since a long time on Bitcoin Core.

you can stop the local blockchain to 10GB if you want ...

http://imagizer.imageshack.us/a/img924/708/CA3SF0.png

That's true if you only own 1 wallet, but if you keep an offline wallet/cold wallet a full node is needed that or redownload (cant resync with a prune node) the complete chain again (depending how long the wallet.dat was offline or making a new wallet.

Icon



thinking of data rest


Title: Re: Bitcoin Core 0.14.1 Released
Post by: johndoe784r on June 13, 2017, 04:25:27 AM
What happens when it reaches a terabyte in size. What happens when it reaches 2 and then 10 terabyte. At some point the problem is not solvable. Surely someone is working on a way to truncate the block chain or some sort of solution. What if someone new wants to get the bitcoin wallet and load it from scratch. Its going to take a 6 months to load it into the PC. This is crazy...

I just picked up a couple of 5 terabyte Seagate portable drives. They don't require an external power source and fit in my pocket. That's 10 terabytes right there.

Haha by the time the block chain is that big we'll have 10 tb USB drives ;-)

Ahh technology.... I can remember When the 107MB on my old Tandy seemed huge - I spent so many hours playing doom on floppy disk on that thing!

I DEFINITELY did not know what a terabyte even was, and that I'd have ten of them sitting in my pants pocket like a wallet someday..

No worries on the size front :-))))


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 15, 2017, 10:18:23 PM
0.14.2 available : https://github.com/bitcoin/bitcoin/releases




with the -bip148 command line : https://github.com/bitcoin/bitcoin/pull/10532
http://imagizer.imageshack.us/a/img922/4129/SGpYnB.jpg
Bioshock Infinite Propaganda.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: -ck on June 15, 2017, 10:34:30 PM
0.14.2 available : https://github.com/bitcoin/bitcoin/releases
with the -bip148 command line : https://github.com/bitcoin/bitcoin/pull/10532
Release note link for what's new for those trying to find the details:
https://github.com/bitcoin/bitcoin/blob/v0.14.2/doc/release-notes.md


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Meuh6879 on June 15, 2017, 11:43:04 PM
 :-\ so, it's not merged in the code ?


Title: Re: Bitcoin Core 0.14.1 Released
Post by: -ck on June 16, 2017, 12:33:05 AM
:-\ so, it's not merged in the code ?
What's not merged, BIP148? Of course not, there isn't remotely universal acceptance by core devs.


Title: Re: Bitcoin Core 0.14.1 Released
Post by: Carlton Banks on June 16, 2017, 01:30:49 PM
:-\ so, it's not merged in the code ?
What's not merged, BIP148? Of course not, there isn't remotely universal acceptance by core devs.

I understand BarryCoin is having the same problem ;)

Still a Barrycoin supporter, ck? :)


Title: Re: Bitcoin Core 0.14.1 Released
Post by: -ck on June 16, 2017, 10:05:35 PM
:-\ so, it's not merged in the code ?
What's not merged, BIP148? Of course not, there isn't remotely universal acceptance by core devs.

I understand BarryCoin is having the same problem ;)

Still a Barrycoin supporter, ck? :)
Who's barry?

I certainly did not support his agreement's proposal in the form they agreed to, only the concept of 2MB+segwit, but that's all offtopic here.