Bitcoin Core 0.13.2 Released

[gmaxwell]

0.13.2 is out and here is the release announcement:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Bitcoin Core version 0.13.2 is now available from:

  <https://bitcoin.org/bin/bitcoin-core-0.13.2/>

Or by bittorrent:

  magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-core-0.13.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2F

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
==============

Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
an OS initially released in 2001. This means that not even critical security
updates will be released anymore. Without security updates, using a bitcoin
wallet on a XP machine is irresponsible at least.

In addition to that, with 0.12.x there have been varied reports of Bitcoin Core
randomly crashing on Windows XP. It is [not clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-217439891)
what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.

We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an alternative OS
that is supported.

No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.

- From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended to work on 10.7+,
but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.

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

Change to wallet handling of mempool rejection
- -----------------------------------------------

When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error.  The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.

This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.

Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).


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

### Consensus
- - #9293 `e591c10` [0.13 Backport #9053] IBD using chainwork instead of height and not using header timestamp (gmaxwell)
- - #9053 `5b93eee` IBD using chainwork instead of height and not using header timestamps (gmaxwell)

### RPC and other APIs
- - #8845 `1d048b9` Don't return the address of a P2SH of a P2SH (jnewbery)
- - #9041 `87fbced` keypoololdest denote Unix epoch, not GMT (s-matthew-english)
- - #9122 `f82c81b` fix getnettotals RPC description about timemillis (visvirial)
- - #9042 `5bcb05d` [rpc] ParseHash: Fail when length is not 64 (MarcoFalke)
- - #9194 `f26dab7` Add option to return non-segwit serialization via rpc (instagibbs)
- - #9347 `b711390` [0.13.2] wallet/rpc backports (MarcoFalke)
- - #9292 `c365556` Complain when unknown rpcserialversion is specified (sipa)
- - #9322 `49a612f` [qa] Don't set unknown rpcserialversion (MarcoFalke)

### Block and transaction handling
- - #8357 `ce0d817` [mempool] Fix relaypriority calculation error (maiiz)
- - #9267 `0a4aa87` [0.13 backport #9239] Disable fee estimates for a confirm target of 1 block (morcos)
- - #9196 `0c09d9f` Send tip change notification from invalidateblock (ryanofsky)

### P2P protocol and network code
- - #8995 `9ef3875` Add missing cs_main lock to ::GETBLOCKTXN processing (TheBlueMatt)
- - #9234 `94531b5` torcontrol: Explicitly request RSA1024 private key (laanwj)
- - #8637 `2cad5db` Compact Block Tweaks (rebase of #8235) (sipa)
- - #9058 `286e548` Fixes for p2p-compactblocks.py test timeouts on travis (#8842) (ryanofsky)
- - #8865 `4c71fc4` Decouple peer-processing-logic from block-connection-logic (TheBlueMatt)
- - #9117 `6fe3981` net: don't send feefilter messages before the version handshake is complete (theuni)
- - #9188 `ca1fd75` Make orphan parent fetching ask for witnesses (gmaxwell)
- - #9052 `3a3bcbf` Use RelevantServices instead of node_network in AttemptToEvict (gmaxwell)
- - #9048 `9460771` [0.13 backport #9026] Fix handling of invalid compact blocks (sdaftuar)
- - #9357 `03b6f62` [0.13 backport #9352] Attempt reconstruction from all compact block announcements (sdaftuar)
- - #9189 `b96a8f7` Always add default_witness_commitment with GBT client support (sipa)
- - #9253 `28d0f22` Fix calculation of number of bound sockets to use (TheBlueMatt)
- - #9199 `da5a16b` Always drop the least preferred HB peer when adding a new one (gmaxwell)

### Build system
- - #9169 `d1b4da9` build: fix qt5.7 build under macOS (theuni)
- - #9326 `a0f7ece` Update for OpenSSL 1.1 API (gmaxwell)
- - #9224 `396c405` Prevent FD_SETSIZE error building on OpenBSD (ivdsangen)

### GUI
- - #8972 `6f86b53` Make warnings label selectable (jonasschnelli) (MarcoFalke)
- - #9185 `6d70a73` Fix coincontrol sort issue (jonasschnelli)
- - #9094 `5f3a12c` Use correct conversion function for boost::path datadir (laanwj)
- - #8908 `4a974b2` Update bitcoin-qt.desktop (s-matthew-english)
- - #9190 `dc46b10` Plug many memory leaks (laanwj)

### Wallet
- - #9290 `35174a0` Make RelayWalletTransaction attempt to AcceptToMemoryPool (gmaxwell)
- - #9295 `43bcfca` Bugfix: Fundrawtransaction: don't terminate when keypool is empty (jonasschnelli)
- - #9302 `f5d606e` Return txid even if ATMP fails for new transaction (sipa)
- - #9262 `fe39f26` Prefer coins that have fewer ancestors, sanity check txn before ATMP (instagibbs)

### Tests and QA
- - #9159 `eca9b46` Wait for specific block announcement in p2p-compactblocks (ryanofsky)
- - #9186 `dccdc3a` Fix use-after-free in scheduler tests (laanwj)
- - #9168 `3107280` Add assert_raises_message to check specific error message (mrbandrews)
- - #9191 `29435db` 0.13.2 Backports (MarcoFalke)
- - #9077 `1d4c884` Increase wallet-dump RPC timeout (ryanofsky)
- - #9098 `ecd7db5` Handle zombies and cluttered tmpdirs (MarcoFalke)
- - #8927 `387ec9d` Add script tests for FindAndDelete in pre-segwit and segwit scripts (jl2012)
- - #9200 `eebc699` bench: Fix subtle counting issue when rescaling iteration count (laanwj)

### Miscellaneous
- - #8838 `094848b` Calculate size and weight of block correctly in CreateNewBlock() (jnewbery)
- - #8920 `40169dc` Set minimum required Boost to 1.47.0 (fanquake)
- - #9251 `a710a43` Improvement of documentation of command line parameter 'whitelist' (wodry)
- - #8932 `106da69` Allow bitcoin-tx to create v2 transactions (btcdrak)
- - #8929 `12428b4` add software-properties-common (sigwo)
- - #9120 `08d1c90` bug: Missed one "return false" in recent refactoring in #9067 (UdjinM6)
- - #9067 `f85ee01` Fix exit codes (UdjinM6)
- - #9340 `fb987b3` [0.13] Update secp256k1 subtree (MarcoFalke)
- - #9229 `b172377` Remove calls to getaddrinfo_a (TheBlueMatt)

Credits
=======

Thanks to everyone who directly contributed to this release:

- - Alex Morcos
- - BtcDrak
- - Cory Fields
- - fanquake
- - Gregory Maxwell
- - Gregory Sanders
- - instagibbs
- - Ivo van der Sangen
- - jnewbery
- - Johnson Lau
- - Jonas Schnelli
- - Luke Dashjr
- - maiiz
- - MarcoFalke
- - Masahiko Hyuga
- - Matt Corallo
- - matthias
- - mrbandrews
- - Pavel Janík
- - Pieter Wuille
- - randy-waterhouse
- - Russell Yanofsky
- - S. Matthew English
- - Steven
- - Suhas Daftuar
- - UdjinM6
- - Wladimir J. van der Laan
- - wodry

As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCgAGBQJYa2IbAAoJEHSBCwEjRsmmiQsIALbkHVVwO7nViQKH1Ub2qpD4
TplOuAP0/4vYotizuI12Gqdnu8SjPmhKwAgIXhVinE6TS4OzGNjy+6LtWGzpcpud
B1pcziZ72Mlfxdbdd1UhDMWEjoBumS9RmXMSqzTlMVlHRv4iiISzdaAROu1jHvdF
YTsnmKXB8OvcXOecxRMY9LrnpSzLALM2MYTDmYwlhhExHIA8ZqI2niky6GCfyfDi
KD7bgfIFJzlgFTpAdhQXOXtWoRV5iHqN7T29ot8Y+yIhVCRhHYXS93Z50GKbkqYV
MXsVAkpZF3qqcKYSPFjbif7faMdrMqcEiII6QhXdDTRGI/35IfuTDbWzzQlnVyY=
=ncCY
-----END PGP SIGNATURE-----

[1714818321]

1714818321

[1714818321]

1714818321

[1714818321]

1714818321

[1714818321]

1714818321

[1714818321]

1714818321

[tygeade]

Thanks for information
But forum news is still displaying notification for older version 0.13.1

News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].

ask theymos to update it

[Carlton Banks]

Thanks for information
But forum news is still displaying notification for older version 0.13.1

News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].

ask theymos to update it

There's a tendency to wait until most or all of the developers have released signed digests from their individual gitian builds before a new version is stickied/generally promoted. Won't be long now, the final source for 13.2 was set yesterday, 24 hours is roughly how long it takes for all that to happen.

[achow101]

Here are the hashes for the binaries:

Code:

eda24dcf0b9fae606eb9811f74ddba69a3287316950f3f02b3000b6b1c02b65f  bitcoin-0.13.2-aarch64-linux-gnu.tar.gz
3c460784d3ab64645d48389c467336a38da473706a69f22f39cfcce5e0f33780  bitcoin-0.13.2-arm-linux-gnueabihf.tar.gz
790e4c7ebf9f4a734d1d2b6bb5e9f5fb3f613f6f93da30fd1420c5b4115dd72f  bitcoin-0.13.2-i686-pc-linux-gnu.tar.gz
8037b25310966127c589eb419534d7763ad62c2c29b94e0a37a5c5f5d96f541a  bitcoin-0.13.2-osx64.tar.gz
dac105b49c159a3d8c9463d1f05afe4cf29ec40bbd145e8961132693b7eff953  bitcoin-0.13.2-osx.dmg
621201189c0409cb17a5073278872dcdcfff1ea147ead6958b55e94416b896d7  bitcoin-0.13.2.tar.gz
27c4be7f571050f6c361e44ca70553d4d2b555b69d568306b676734100d929e1  bitcoin-0.13.2-win32-setup.exe
4d1c26675088219d8e2204b5a9f028916d5982db860298a70b6ed08e30af2a53  bitcoin-0.13.2-win32.zip
8960defc12287dd9248b99bab02a0854c072e6a3850757036c585cbd628217bf  bitcoin-0.13.2-win64-setup.exe
e07ce2a8cc0913fb253a42073fd3b94921da7f916366dd0534f3b24cad7a733e  bitcoin-0.13.2-win64.zip
29215a7fe7430224da52fc257686d2d387546eb8acd573a949128696e8761149  bitcoin-0.13.2-x86_64-linux-gnu.tar.gz

Don't forget to verify the binaries. If you need help, follow the instructions here: https://bitcointalk.org/index.php?topic=1588906.0

[BillyBobZorton]

How can I know if im using the HD wallet or not? I forgot if I finally stopped being lazy and created a new wallet and sent my coins over the new wallet or finally stuck with the same wallet.dat that i have had since years ago... im confused because I remember seeing some screenshots of the Core wallet that had an "HD" market on the bottom right and it was greyed out when the wallet was not HD and black when the wallet is HD mode activated.
I guess there is a command to put on the console and it will tell you if its HD or not but what is that command?

Also how do I send my coins to the new HD wallet? wouldn't I need 2 computers for that?

[achow101]

How can I know if im using the HD wallet or not?
..
I guess there is a command to put on the console and it will tell you if its HD or not but what is that command?

Go into the console and type getwalletinfo. If there is a field named hdmasterkeyid then you are using an HD wallet. Otherwise you are not.

I forgot if I finally stopped being lazy and created a new wallet and sent my coins over the new wallet or finally stuck with the same wallet.dat that i have had since years ago... im confused because I remember seeing some screenshots of the Core wallet that had an "HD" market on the bottom right and it was greyed out when the wallet was not HD and black when the wallet is HD mode activated.

That icon is in the master (development) branch and will be available for the 0.14 release.

Also how do I send my coins to the new HD wallet? wouldn't I need 2 computers for that?

You do not need two computers.

First backup your wallet.dat file. Then move it out of the data directory. Bitcoin Core will create a new HD wallet by default. Grab an address (or however many you want to send to) from the new wallet and copy them somewhere. Then stop Bitcoin Core and backup your new wallet.dat file. Move the old one back into the data directory and start up Bitcoin Core again. Now send all of your Bitcoin from this old wallet to the addresses from your new wallet. Once the transaction confirms, stop Bitcoin Core, replace the wallet file with the backup of the new wallet file and restart. You will now be using an HD wallet.

[Amph]

can the core handle in the future an embedded blockexplorer, so we don't need to go to blockchaininfo and akin?

[achow101]

can the core handle in the future an embedded blockexplorer, so we don't need to go to blockchaininfo and akin?

Core already has a block explorer of sorts built in. If you enable the transaction index with -txindex in the startup command, then you will be able to use the debug console to lookup the details of any transaction and block that your node has received and accepted.

If you want a nice looking GUI and all, that probably won't happen.

[Amph]

can the core handle in the future an embedded blockexplorer, so we don't need to go to blockchaininfo and akin?

Core already has a block explorer of sorts built in. If you enable the transaction index with -txindex in the startup command, then you will be able to use the debug console to lookup the details of any transaction and block that your node has received and accepted.

If you want a nice looking GUI and all, that probably won't happen.

interesting, but apparently it's incompatible with the prune mode for clear reasons, so i need to dl the blockchain again

[shorena]

can the core handle in the future an embedded blockexplorer, so we don't need to go to blockchaininfo and akin?

Core already has a block explorer of sorts built in. If you enable the transaction index with -txindex in the startup command, then you will be able to use the debug console to lookup the details of any transaction and block that your node has received and accepted.

If you want a nice looking GUI and all, that probably won't happen.

interesting, but apparently it's incompatible with the prune mode for clear reasons, so i need to dl the blockchain again

When you enable txindex for the first time it causes core to reindex. Which on a pruned node, requires you to redownload all missing blocks. It might work just fine after that, but I havent tried it.

[achow101]

When you enable txindex for the first time it causes core to rescan. A rescan on a pruned node, requires you to redownload all missing blocks. It might work just fine after that, but I havent tried it.

It actually reindexes not rescans.

[Icon]

can this version .13.2 allow the import/export the wallet HD seed yet? And if so how...


Icon

[Lauda]

can this version .13.2 allow the import/export the wallet HD seed yet? And if so how...

No, a tool / option for this has not been yet developed / released.

[dervil]

Hello
I am in the process of integration BitcoinCore 0.13.2
Until the end there was still some.
With pleasure Support Bitcoin Be the network.
What better???
1. Wait until the end of Integration before I open port 8333?
2. Or now open port and continue integration?
3. Or uninstall BitcoinCore delete all files and blocks, then open port and start all over again?

[achow101]

Hello
I am in the process of integration BitcoinCore 0.13.2
Until the end there was still some.
With pleasure Support Bitcoin Be the network.
What better???
1. Wait until the end of Integration before I open port 8333?
2. Or now open port and continue integration?
3. Or uninstall BitcoinCore delete all files and blocks, then open port and start all over again?

Your question is entirely incomprehensible. Please ask your question in your native language in the appropriate local board.

[bitwab]

Where can details about  "#8357 `ce0d817` [mempool] Fix relaypriority calculation error (maiiz)" can be found?
thanks

[achow101]

Where can details about  "#8357 `ce0d817` [mempool] Fix relaypriority calculation error (maiiz)" can be found?
thanks

https://github.com/bitcoin/bitcoin/pull/8357

[Lauda]

can this version .13.2 allow the import/export the wallet HD seed yet? And if so how...

No. That feature has not been implemented yet AFAIK.

[j753k]

Thanks for the update.

[achow101]

can this version .13.2 allow the import/export the wallet HD seed yet? And if so how...

No. That feature has not been implemented yet AFAIK.

You can export the Master Private Key using the dumpwallet RPC command. The Master Private Key will be in the exported text file. However there currently is no way to export just the Master Private Key to the console as can be done with dumpprivkey. Additionally the Master Private Key cannot be imported to a wallet.