Bitcoin Forum
December 17, 2017, 12:19:31 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 3 4 5 »  All
  Print  
Author Topic: Bitcoin Core 0.15.1 Released  (Read 18124 times)
achow101
Staff
Legendary
*
Offline Offline

Activity: 1246


17kKQppUsngUiByDsce4JXoZEjjpvX9bpR


View Profile WWW
November 11, 2017, 05:06:31 PM
 #1

Bitcoin Core version *0.15.1* is now available from:

  https://bitcoincore.org/bin/bitcoin-core-0.15.1

or

  https://bitcoin.org/bin/bitcoin-core-0.15.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/

How to Upgrade
==============

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on Mac)
or `bitcoind`/`bitcoin-qt` (on Linux).

The first time you run version 0.15.0 or higher, your chainstate database will
be converted to a new format, which will take anywhere from a few minutes to
half an hour, depending on the speed of your machine.

The file format of `fee_estimates.dat` changed in version 0.15.0. Hence, a
downgrade from version 0.15 or upgrade to version 0.15 will cause all fee
estimates to be discarded.

Note that the block database format also changed in version 0.8.0 and there is no
automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
directly from 0.7.x and earlier without redownloading the blockchain is not supported.
However, as usual, old wallet versions are still supported.

Downgrading warning
-------------------

The chainstate database for this release is not compatible with previous
releases, so if you run 0.15 and then decide to switch back to any
older version, you will need to run the old release with the `-reindex-chainstate`
option to rebuild the chainstate data structures in the old format.

If your node has pruning enabled, this will entail re-downloading and
processing the entire blockchain.

Compatibility
==============

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

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


Notable changes
===============

Network fork safety enhancements
--------------------------------

A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks
have been made, as a safety precaution against blockchain forks and misbehaving peers.

- Unrequested blocks with less work than the minimum-chain-work are now no longer processed even
if they have more work than the tip (a potential issue during IBD where the tip may have low-work).
This prevents peers wasting the resources of a node.

- Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.

- For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it
doesn't, and if we still haven't heard about a block with sufficient work after a 20 minute timeout, then we send
a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient
work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent
excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable
number of nodes not known to be on bogus chains.

- Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact
block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them)
will now be disconnected.

- If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect
to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect
the peer that least recently announced a new block.

- The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be
invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that
descends from an invalid block is marked as such.


Miner block size limiting deprecated
------------------------------------

Though blockmaxweight has been preferred for limiting the size of blocks returned by
getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished
to limit their block size directly. Using this option resulted in a few UI issues as
well as non-optimal fee selection and ever-so-slightly worse performance, and has thus
now been deprecated. Further, the blockmaxsize option is now used only to calculate an
implied blockmaxweight, instead of limiting block size directly. Any miners who wish
to limit their blocks by size, instead of by weight, will have to do so manually by
removing transactions from their block template directly.


GUI settings backed up on reset
-------------------------------

The GUI settings will now be written to `guisettings.ini.bak` in the data directory before wiping them when
the `-resetguisettings` argument is used. This can be used to retroactively troubleshoot issues due to the
GUI settings.


Duplicate wallets disallowed
----------------------------

Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing
issues when both were opened simultaneously. It is no longer possible to open copies of the same wallet.


Debug `-minimumchainwork` argument added
----------------------------------------

A hidden debug argument `-minimumchainwork` has been added to allow a custom minimum work value to be used
when validating a chain.


Low-level RPC changes
----------------------

- The "currentblocksize" value in getmininginfo has been removed.

- `dumpwallet` no longer allows overwriting files. This is a security measure
  as well as prevents dangerous user mistakes.

- `backupwallet` will now fail when attempting to backup to source file, rather than
  destroying the wallet.

- `listsinceblock` will now throw an error if an unknown `blockhash` argument
  value is passed, instead of returning a list of all wallet transactions since
  the genesis block. The behaviour is unchanged when an empty string is provided.

0.15.1 Change log
=================

### Mining
- #11100 `7871a7d` Fix confusing blockmax{size,weight} options, dont default to throwing away money (TheBlueMatt)

### RPC and other APIs
- #10859 `2a5d099` gettxout: Slightly improve doc and tests (jtimon)
- #11267 `b1a6c94` update cli for estimate\*fee argument rename (laanwj)
- #11483 `20cdc2b` Fix importmulti bug when importing an already imported key (pedrobranco)
- #9937 `a43be5b` Prevent `dumpwallet` from overwriting files (laanwj)
- #11465 `405e069` Update named args documentation for importprivkey (dusty-wil)
- #11131 `b278a43` Write authcookie atomically (laanwj)
- #11565 `7d4546f` Make listsinceblock refuse unknown block hash (ryanofsky)
- #11593 `8195cb0` Work-around an upstream libevent bug (theuni)

### P2P protocol and network code
- #11397 `27e861a` Improve and document SOCKS code (laanwj)
- #11252 `0fe2a9a` When clearing addrman clear mapInfo and mapAddr (instagibbs)
- #11527 `a2bd86a` Remove my testnet DNS seed (schildbach)
- #10756 `0a5477c` net processing: swap out signals for an interface class (theuni)
- #11531 `55b7abf` Check that new headers are not a descendant of an invalid block (more effeciently) (TheBlueMatt)
- #11560 `49bf090` Connect to a new outbound peer if our tip is stale (sdaftuar)
- #11568 `fc966bb` Disconnect outbound peers on invalid chains (sdaftuar)
- #11578 `ec8dedf` Add missing lock in ProcessHeadersMessage(...) (practicalswift)
- #11456 `6f27965` Replace relevant services logic with a function suite (TheBlueMatt)
- #11490 `bf191a7` Disconnect from outbound peers with bad headers chains (sdaftuar)

### Validation
- #10357 `da4908c` Allow setting nMinimumChainWork on command line (sdaftuar)
- #11458 `2df65ee` Don't process unrequested, low-work blocks (sdaftuar)

### Build system
- #11440 `b6c0209` Fix validationinterface build on super old boost/clang (TheBlueMatt)
- #11530 `265bb21` Add share/rpcuser to dist. source code archive (MarcoFalke)

### GUI
- #11334 `19d63e8` Remove custom fee radio group and remove nCustomFeeRadio setting (achow101)
- #11198 `7310f1f` Fix display of package name on 'open config file' tooltip (esotericnonsense)
- #11015 `6642558` Add delay before filtering transactions (lclc)
- #11338 `6a62c74` Backup former GUI settings on `-resetguisettings` (laanwj)
- #11335 `8d13b42` Replace save|restoreWindowGeometry with Qt functions (MeshCollider)
- #11237 `2e31b1d` Fixing division by zero in time remaining (MeshCollider)
- #11247 `47c02a8` Use IsMine to validate custom change address (MarcoFalke)

### Wallet
- #11017 `9e8aae3` Close DB on error (kallewoof)
- #11225 `6b4d9f2` Update stored witness in AddToWallet (sdaftuar)
- #11126 `2cb720a` Acquire cs_main lock before cs_wallet during wallet initialization (ryanofsky)
- #11476 `9c8006d` Avoid opening copied wallet databases simultaneously (ryanofsky)
- #11492 `de7053f` Fix leak in CDB constructor (promag)
- #11376 `fd79ed6` Ensure backupwallet fails when attempting to backup to source file (tomasvdw)
- #11326 `d570aa4` Fix crash on shutdown with invalid wallet (MeshCollider)

### Tests and QA
- #11399 `a825d4a` Fix bip68-sequence rpc test (jl2012)
- #11150 `847c75e` Add getmininginfo test (mess110)
- #11407 `806c78f` add functional test for mempoolreplacement command line arg (instagibbs)
- #11433 `e169349` Restore bitcoin-util-test py2 compatibility (MarcoFalke)
- #11308 `2e1ac70` zapwallettxes: Wait up to 3s for mempool reload (MarcoFalke)
- #10798 `716066d` test bitcoin-cli (jnewbery)
- #11443 `019c492` Allow "make cov" out-of-tree; Fix rpc mapping check (MarcoFalke)
- #11445 `51bad91` 0.15.1 Backports (MarcoFalke)
- #11319 `2f0b30a` Fix error introduced into p2p-segwit.py, and prevent future similar errors (sdaftuar)
- #10552 `e4605d9` Tests for zmqpubrawtx and zmqpubrawblock (achow101)
- #11067 `eeb24a3` TestNode: Add wait_until_stopped helper method (MarcoFalke)
- #11068 `5398f20` Move wait_until to util (MarcoFalke)
- #11125 `812c870` Add bitcoin-cli -stdin and -stdinrpcpass functional tests (promag)
- #11077 `1d80d1e` fix timeout issues from TestNode (jnewbery)
- #11078 `f1ced0d` Make p2p-leaktests.py more robust (jnewbery)
- #11210 `f3f7891` Stop test_bitcoin-qt touching ~/.bitcoin (MeshCollider)
- #11234 `f0b6795` Remove redundant testutil.cpp|h files (MeshCollider)
- #11215 `cef0319` fixups from set_test_params() (jnewbery)
- #11345 `f9cf7b5` Check connectivity before sending in assumevalid.py (jnewbery)
- #11091 `c276c1e` Increase initial RPC timeout to 60 seconds (laanwj)
- #10711 `fc2aa09` Introduce TestNode (jnewbery)
- #11230 `d8dd8e7` Fixup dbcrash interaction with add_nodes() (jnewbery)
- #11241 `4424176` Improve signmessages functional test (mess110)
- #11116 `2c4ff35` Unit tests for script/standard and IsMine functions (jimpo)
- #11422 `a36f332` Verify DBWrapper iterators are taking snapshots (TheBlueMatt)
- #11121 `bb5e7cb` TestNode tidyups (jnewbery)
- #11521 `ca0f3f7` travis: move back to the minimal image (theuni)
- #11538 `adbc9d1` Fix race condition failures in replace-by-fee.py, sendheaders.py (sdaftuar)
- #11472 `4108879` Make tmpdir option an absolute path, misc cleanup (MarcoFalke)
- #10853 `5b728c8` Fix RPC failure testing (again) (jnewbery)
- #11310 `b6468d3` Test listwallets RPC (mess110)

### Miscellaneous
- #11377 `75997c3` Disallow uncompressed pubkeys in bitcoin-tx [multisig] output adds (TheBlueMatt)
- #11437 `dea3b87` [Docs] Update Windows build instructions for using WSL and Ubuntu 17.04 (fanquake)
- #11318 `8b61aee` Put back inadvertently removed copyright notices (gmaxwell)
- #11442 `cf18f42` [Docs] Update OpenBSD Build Instructions for OpenBSD 6.2 (fanquake)
- #10957 `50bd3f6` Avoid returning a BIP9Stats object with uninitialized values (practicalswift)
- #11539 `01223a0` [verify-commits] Allow revoked keys to expire (TheBlueMatt)


Credits
=======

Thanks to everyone who directly contributed to this release:

- Andreas Schildbach
- Andrew Chow
- Chris Moore
- Cory Fields
- Cristian Mircea Messel
- Daniel Edgecumbe
- Donal OConnor
- Dusty Williams
- fanquake
- Gregory Sanders
- Jim Posen
- John Newbery
- Johnson Lau
- João Barbosa
- Jorge Timón
- Karl-Johan Alm
- Lucas Betschart
- MarcoFalke
- Matt Corallo
- Paul Berg
- Pedro Branco
- Pieter Wuille
- practicalswift
- Russell Yanofsky
- Samuel Dobson
- Suhas Daftuar
- Tomas van der Wansem
- Wladimir J. van der Laan

As well as everyone that helped translating on Transifex.

1513513171
Hero Member
*
Offline Offline

Posts: 1513513171

View Profile Personal Message (Offline)

Ignore
1513513171
Reply with quote  #2

1513513171
Report to moderator
1513513171
Hero Member
*
Offline Offline

Posts: 1513513171

View Profile Personal Message (Offline)

Ignore
1513513171
Reply with quote  #2

1513513171
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
kellogsblocks
Jr. Member
*
Online Online

Activity: 51


View Profile
November 12, 2017, 02:12:34 PM
 #2

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley

you like? 3LxhgT22gKWbxxfHcQ9Js6j16VqqdjkMEh :-)
MeshCollider
Jr. Member
*
Offline Offline

Activity: 52

GitHub.com/MeshCollider


View Profile WWW
November 14, 2017, 08:56:37 AM
 #3

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley

Other things will probably be added to the 0.15.2 milestone closer to when it is released. Generally releases of bitcoin are based on time rather than features Smiley

Cryptography & Bitcoin enthusiast | Programmer
Cordillera
Member
**
Offline Offline

Activity: 70

John 3:16/John 14:6


View Profile
November 14, 2017, 10:37:33 AM
 #4

thanks for the update info new release with bug fixed this is what i expected
Glendale
Jr. Member
*
Offline Offline

Activity: 42


View Profile
November 14, 2017, 05:55:16 PM
 #5

Hoping transactions will be more faster
kellogsblocks
Jr. Member
*
Online Online

Activity: 51


View Profile
November 14, 2017, 09:18:48 PM
 #6

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley

Other things will probably be added to the 0.15.2 milestone closer to when it is released. Generally releases of bitcoin are based on time rather than features Smiley
Thank you very much Smiley

P.S. I really like your work in the bitcoin github Smiley

you like? 3LxhgT22gKWbxxfHcQ9Js6j16VqqdjkMEh :-)
akash15785
Jr. Member
*
Online Online

Activity: 56


View Profile WWW
November 15, 2017, 06:37:12 AM
 #7

Thank you for the updated news. I see several bugs is fixed. Means faster and secure transactions ever. Hope upcoming releases will bring us more security features..
Congratulations..

Cryptelo
Newbie
*
Offline Offline

Activity: 14

Secure KeyManagement for the Blockchain Generation


View Profile WWW
November 15, 2017, 11:27:06 AM
 #8

Really hope transactions will be more faster

Cryptelo║Upcoming ICO║ ▰ ▰Cryptelo.com ▰ ▰
diwataluna
Member
**
Offline Offline

Activity: 98

ETH: 0xF6bb1DfbF6d668176feA4176B054a4D9cdc37763


View Profile
November 15, 2017, 04:17:30 PM
 #9

Kudos to the contributors! Expecting improvement in the following weeks.

◨▬▬▬▬▬◧   HACKEN   ◨▬▬▬▬▬◧
■  DEDICATED CRYPTOCURRENCY FOR WHITE HAT HACKERS
RDDRocket
Sr. Member
****
Offline Offline

Activity: 268


View Profile
November 15, 2017, 11:51:49 PM
 #10

Very fast and smooth sync on x86_64 linux. Looks really good. What might be the time frame on 0.15.2 and might that fully support running lnd on top of that build?
Ealex
Jr. Member
*
Offline Offline

Activity: 42


View Profile
November 16, 2017, 12:22:13 PM
 #11

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley

Other things will probably be added to the 0.15.2 milestone closer to when it is released. Generally releases of bitcoin are based on time rather than features Smiley
I agree! Love the new update.
Amph
Legendary
*
Offline Offline

Activity: 1722


Zabercoin – An Asset Backed Cryptocurrency


View Profile
November 17, 2017, 02:14:22 PM
 #12

not mandatory from 15.0 right?

THE FUTURE OF
REAL ESTATE
..

║║
║║
║║
▬▬ ● ● ▬▬▬▬▬▬▬ ● ● ▬▬▬▬▬▬▬ ● ● ▬▬▬▬▬▬ ● ● ▬▬

║║
║║
║║
MeshCollider
Jr. Member
*
Offline Offline

Activity: 52

GitHub.com/MeshCollider


View Profile WWW
November 17, 2017, 05:50:28 PM
 #13

not mandatory from 15.0 right?

No, the upgrade brings a number of improvements but there is nothing stopping you from continuing to use 15.0 instead Smiley

Cryptography & Bitcoin enthusiast | Programmer
shahead720
Newbie
*
Offline Offline

Activity: 28


View Profile
November 19, 2017, 06:05:23 PM
 #14

Absoulately very good project .
Hope quietly transactions will be more faster and also will bring us more security features.
Really I agree!!
A Feeder
Full Member
***
Offline Offline

Activity: 126


Don't Invite me into Games cuz I'll Feed the enemy


View Profile
November 20, 2017, 03:35:18 PM
 #15

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley
Wow a very astonishing new release. With this new model I can mine more efficiently with a greater profit.

EasyCrypto
Member
**
Offline Offline

Activity: 73

CryptoSuisse


View Profile WWW
November 22, 2017, 09:23:30 AM
 #16

how long take to synch all the blockchain? (connection 20Mo/bits

.crypto
Member
**
Offline Offline

Activity: 86


View Profile
November 22, 2017, 02:12:14 PM
 #17

What I found irritating is that the latest version 0.15.1 was already available for download on bitcoin.org, but on bitcoincore.org the latest version was still 0.15.0.1 for a couple of days.

So, I downloaded the latest version from bitcoin.org, installed it and then discovered the discrepancy and rolled back to the old version and three days later (when it was listed on bitcoincore.org) upgraded to 0.15.1 again  Cheesy

nur1labs
Sr. Member
****
Offline Offline

Activity: 266


Founder Nur1Labs


View Profile WWW
November 23, 2017, 06:16:27 AM
 #18

will this security more tight than old. since my money not wanna steal~

Nur1Labs @ Project 2009-2017
UAE Seasider
Full Member
***
Offline Offline

Activity: 140


“Best IoT Platform Based on Blockchain”


View Profile
November 23, 2017, 08:15:47 AM
 #19

How is it working for people, anybody notice a marked improvement before I try it for myself?

nur1labs
Sr. Member
****
Offline Offline

Activity: 266


Founder Nur1Labs


View Profile WWW
November 23, 2017, 09:36:27 AM
 #20

don't spam guys. when i think old one good. but this one better. and remove estimate thing. nice team  Grin

geez i become double post

How is it working for people, anybody notice a marked improvement before I try it for myself?

more fast when sync good~ Cool

remove up. and stable block chain download nice guys[added]

Nur1Labs @ Project 2009-2017
Pages: [1] 2 3 4 5 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!