Bitcoin Forum

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

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.

Here are the hashes for the binaries:


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

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?

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.

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

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.

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.

It actually reindexes not rescans.

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


Icon

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

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.

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

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

No. That feature has not been implemented yet AFAIK.

Thanks for the update.

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.

Hi, forgive me for asking, but i dont understand even after reading on various sites, what the purpose of this Bitcoin Core - Wallet is?
I have a Bitcoin address with a site called Luno  (not Luna).
It is a long number starting with .....

SO now how and what is the use of this Bitcoin Core application, it is just another means of how to get a wallet?

I dont know what they mean when they say YOUR WALLET ADDRESS on those command line utilities.
I mostly get authentication errors, such a pain to work with.
I have tried -u username and -p password and the bloody thing always throws an authentication issue.
I dont understand how those utils actually work.
Cgminer is one of the worst it clears the screen and shows you information but it doesnt tell you whether it has started or nor or rather connected successfully.

Sorry its an all-sorts post.

Its a wallet and a full node. Thus running it you dont rely on anyone else, the client confirms all information on its own.


... with? 1, 3 would be common prefixes for addresses, 5, L and K for private keys.


You currently use a service, not a wallet. You have no control over your private keys. If the company offering the service is gone tomorrow, so are your coins. Its no different than a bank, well a bank probably has more laws to follow than a bitcoin service. This is not only true for bitcoin core, which requires you to download the entire blockchain, but also for other wallets like e.g. electrum and multibit hd.


"Command line utilities"? Not sure what your question is, can you rephrase?

Hi shorena , thakns for replying and i will get back to you soon.
I was typing and then everything i wrote disappeared, cant believe it, i have to re-type again.

hanks 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].

No it doesn't. I see it showing 0.13.2. It has been showing that for several weeks now.

So i think i understand you better.
Do you mean that i can have the Bitcoin Core wallet installed on my desktop and then that provides me with a coin address?
So i do not have to use the Luno.com bitcoiin id ?
Not sure i know how to set it up...
I have allowed the program to stay open for a few hours and i can see now the synchronization is complete...it doesnt say 5 years behind anymore so i take it that is a good thing.

I have tried so many utils now and some are being up by my antivirus as a Artemis! trojan/virus ...not sure.
I have downloaded them from sites that look kosher and or also from github so i take it this is a false positive.
As for using them and actually making them work , what a bloody head ache.
I can not get any of them to work, the only one wihch does seem to work is Minderd.exe and Cudaminer.exe which are running through a gui i downloaded called Easy miner. I am also using a pool called litecoinpool. It has something like stratum+tcp://litecoilpool.org:3333  as the host name to mine against.
It seems to like my log in also.

Now as for the other tools like SGMiner and CGMiner God knows whats going on , all sorts of errors or warnings about SETX or SET and environment variables and then it doesnt even connecgt or it looks like it does and then it sits there doing something or nothing?  and then i dont know why the heck the screen clears and also why it doesnt tell u anything is wrong.... only when i press control-c then it shows me the error like could not connect.

I need some guidance here please, i am going nuts i cant handle this i dont know what i am doing wrong and maybe i am following the wrong sites or tutorials.
Either the guide is outdated and my version is different and then i also noticed with Slushpool they say that only certain utilities work with them and then again when you use the guis like nicehashminer they seems to work BUT how the hell does it know how u are? because u could be mining for nothing.

I really dont understand this , its driving me mad, i really just want to give as much detail as i can to whoever is going to help me and get me on my feet with this.
I also want to report enhancements or experience to the developers of these tools because im sure they can make them more robust .

Thanks for reading


Windows 7 Ult x64 on an MSI-A88X-G43, AMD X4 860K, GTX 650, 16GB Ram

As many as you want, yes.


Depends on your OS, but its usually as simple as installing a programm.


It takes some time to download and verify all transactions ever done. Currently thats ~100 GB.


Not sure what you are talking about, but I wouldnt just dismiss the warnings by your anti virus software. Otherwise there is no point in having it.


Dont bother mining with that hardware, this is done with ASICs (special mining hardware) now. You would just raise your electricity bill and likely never see any coins. Its also not the topic to talk about this. There is an entire section about mining with profit (or not). -> https://bitcointalk.org/index.php?board=81.0

Great work.

Only the consensus of miners is left.


From wan.

where can i get my wallet ? i just started and im barely confused on how things are getting well around here. thanks in advance :D have a nice day !

Thanks  :)

It'd be nice if this updates make Bitcoin faster, I know there's a lot of variables, specially fees... but maybe if the block was larger than 1Mb it'd be faster.

Confirmation speed if one of the biggest issues with Bitcoin

curious about this, but are miners at least running this version, or they are still stuck with old version since they seems to hate segwit and don't want to activate it

not to mention that many of them use spv client

v0.14.0 RC1 on the rail : https://github.com/bitcoin/bitcoin/releases/tag/v0.14.0rc1

Great work!Thanks

v0.14.0 RC2 on the rail : https://github.com/bitcoin/bitcoin/releases/tag/v0.14.0rc2

I really enjoyed this interview and encourage people to listen to it. In it, he discusses one of the biggest problems with Bitcoin user friendliness, which is private key security. While many people want Bitcoin to be used in the mainstream, the reality is that there is a tremendous amount of user education required for understanding just the aspect of private key security.

v0.14.0 RC3 on the rail : https://github.com/bitcoin/bitcoin/releases/tag/v0.14.0rc3
 :)

 :) good , the mempool.dat is activated !  And no crash at shutdown in disablewallet mode. ;)

what are the relevant update in this release? is it onyl for bug fixed or they added new features?

Bitcoin Core always build the futur ... so, every release is a step and introduce somes very interesting things to force the rules over the Network of Bitcoin.

Bitcoin Core is my go to wallet, and in my opinion the best due to constant updates!

And it's the base of Bitcoin Network after all.

Hi

I installed Bitcoin Core for Ubuntu through the ubuntu software center. When I see the ABOUT tab it says:

Bitcoin Core version v0.13.2.0-g0d71914(32-bit)

Trying to find some reference to this specific version but can't. Can someone help and let me know if it's a valid version and where I could find some reference to it, before I start the verification process?

Thanks very much in advance

Bitcoin Core initial synchronization will take time and download a lot of data. You should make sure that you have enough bandwidth and storage for the full block chain size (over 100GB). If you have a good Internet connection, you can help strengthen the network by keeping your PC running with Bitcoin Core and port 8333 open.

114 Go.

0.14.0 released. Update your nodes!

---

Thread: https://bitcointalk.org/index.php?topic=1817896.0
Github: https://github.com/bitcoin/bitcoin/blob/0.14/doc/release-notes.md
Binaries: https://bitcoin.org/bin/bitcoin-core-0.14.0/