public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Bitcoin development mailing list
	<bitcoin-dev@lists.linuxfoundation.org>,
	 Bitcoin Core development mailing list
	<bitcoin-core-dev@lists.linuxfoundation.org>
Cc: Matt Corallo <matt@bluematt.me>
Subject: [bitcoin-dev] Bitcoin Core 0.17.1 released
Date: Tue, 25 Dec 2018 10:27:42 +0100	[thread overview]
Message-ID: <20181225092742.albj7cf3suxw4hyj@aurora.visucore.com> (raw)

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

Bitcoin Core version 0.17.1 is now available from:

  <https://bitcoincore.org/bin/bitcoin-core-0.17.1/>

or through BitTorrent:

    magnet:?xt=urn:btih:c56c87ccfaa8e6fbccc90d549121e61efd97cb6f&dn=bitcoin-core-0.17.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fexplodie.org%3A6969    

This is a new minor version release, with 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).

If your node has a txindex, the txindex db will be migrated the first time you run 0.17.0 or newer, which may take up to a few hours. Your node will not be functional until this migration completes.

The first time you run version 0.15.0 or newer, 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.

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.10+, and Windows 7 and newer (Windows XP is not supported).

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

- From 0.17.0 onwards macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn't
support versions of macOS older than 10.10.

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

`listtransactions` label support
- --------------------------------

The `listtransactions` RPC `account` parameter which was deprecated in 0.17.0
and renamed to `dummy` has been un-deprecated and renamed again to `label`.

When bitcoin is configured with the `-deprecatedrpc=accounts` setting, specifying
a label/account/dummy argument will return both outgoing and incoming
transactions. Without the `-deprecatedrpc=accounts` setting, it will only return
incoming transactions (because it used to be possible to create transactions
spending from specific accounts, but this is no longer possible with labels).

When `-deprecatedrpc=accounts` is set, it's possible to pass the empty string ""
to list transactions that don't have any label. Without
`-deprecatedrpc=accounts`, passing the empty string is an error because returning
only non-labeled transactions is not generally useful behavior and can cause
confusion.

0.17.1 change log
=================

### P2P protocol and network code
- - #14685 `9406502` Fix a deserialization overflow edge case (kazcw)
- - #14728 `b901578` Fix uninitialized read when stringifying an addrLocal (kazcw)

### Wallet
- - #14441 `5150acc` Restore ability to list incoming transactions by label (jnewbery)
- - #13546 `91fa15a` Fix use of uninitialized value `bnb_used` in CWallet::CreateTransaction(…) (practicalswift)
- - #14310 `bb90695` Ensure wallet is unlocked before signing (gustavonalle)
- - #14690 `5782fdc` Throw error if CPubKey is invalid during PSBT keypath serialization (instagibbs)
- - #14852 `2528443` backport: [tests] Add `wallet_balance.py` (MarcoFalke)
- - #14196 `3362a95` psbt: always drop the unnecessary utxo and convert non-witness utxo to witness when necessary (achow101)
- - #14588 `70ee1f8` Refactor PSBT signing logic to enforce invariant and fix signing bug (gwillen)
- - #14424 `89a9a9d` Stop requiring imported pubkey to sign non-PKH schemes (sipa, MeshCollider)

### RPC and other APIs
- - #14417 `fb9ad04` Fix listreceivedbyaddress not taking address as a string (etscrivner)
- - #14596 `de5e48a` Bugfix: RPC: Add `address_type` named param for createmultisig (luke-jr)
- - #14618 `9666dba` Make HTTP RPC debug logging more informative (practicalswift)
- - #14197 `7bee414` [psbt] Convert non-witness UTXOs to witness if witness sig created (achow101)
- - #14377 `a3fe125` Check that a separator is found for psbt inputs, outputs, and global map (achow101)
- - #14356 `7a590d8` Fix converttopsbt permitsigdata arg, add basic test (instagibbs)
- - #14453 `75b5d8c` Fix wallet unload during walletpassphrase timeout (promag)

### GUI
- - #14403 `0242b5a` Revert "Force TLS1.0+ for SSL connections" (real-or-random)
- - #14593 `df5131b` Explicitly disable "Dark Mode" appearance on macOS (fanquake)

### Build system
- - #14647 `7edebed` Remove illegal spacing in darwin.mk (ch4ot1c)
- - #14698 `ec71f06` Add bitcoin-tx.exe into Windows installer (ken2812221)

### Tests and QA
- - #13965 `29899ec` Fix extended functional tests fail (ken2812221)
- - #14011 `9461f98` Disable wallet and address book Qt tests on macOS minimal platform (ryanofsky)
- - #14180 `86fadee` Run all tests even if wallet is not compiled (MarcoFalke)
- - #14122 `8bc1bad` Test `rpc_help.py` failed: Check whether ZMQ is enabled or not (Kvaciral)
- - #14101 `96dc936` Use named args in validation acceptance tests (MarcoFalke)
- - #14020 `24d796a` Add tests for RPC help (promag)
- - #14052 `7ff32a6` Add some actual witness in `rpc_rawtransaction` (MarcoFalke)
- - #14215 `b72fbab` Use correct python index slices in example test (sdaftuar)
- - #14024 `06544fa` Add `TestNode::assert_debug_log` (MarcoFalke)
- - #14658 `60f7a97` Add test to ensure node can generate all rpc help texts at runtime (MarcoFalke)
- - #14632 `96f15e8` Fix a comment (fridokus)
- - #14700 `f9db08e` Avoid race in `p2p_invalid_block` by waiting for the block request (MarcoFalke)
- - #14845 `67225e2` Add `wallet_balance.py` (jnewbery)

### Documentation
- - #14161 `5f51fd6` doc/descriptors.md tweaks (ryanofsky)
- - #14276 `85aacc4` Add autogen.sh in ARM Cross-compilation (walterwhite81)

Credits
=======

Thanks to everyone who directly contributed to this release:

- - Andrew Chow
- - Chun Kuan Lee
- - David A. Harding
- - Eric Scrivner
- - fanquake
- - fridokus
- - Glenn Willen
- - Gregory Sanders
- - gustavonalle
- - John Newbery
- - Jon Layton
- - Jonas Schnelli
- - João Barbosa
- - Kaz Wesley
- - Kvaciral
- - Luke Dashjr
- - MarcoFalke
- - MeshCollider
- - Pieter Wuille
- - practicalswift
- - Russell Yanofsky
- - Sjors Provoost
- - Suhas Daftuar
- - Tim Ruffing
- - Walter
- - Wladimir J. van der Laan

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

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAlwh9x0ACgkQHkrtYphs
0l1yqQf/WzqxJkIrzyO9ZRaLKjaaxVz8E7jqHsyA+4mdObsSPjneGfKh7OEC2Fhx
VV7EF+A5kNFQgwnPwXlW3AaiuDhcGHEG4T0AB0JGaggLD6KrjpzuWHYx5k0COwdG
5sYRH4tZxbtWoF1+IQ1R8Ceac20VBqBUBJJfAAntg4VrGaBjDqFJzf+0GmQM0gyW
tq12nMIwevHWXsmtrQWhAbCeLI8pyhGLOtLqCgrrD5hqe72iV7t6Njs5E+kRkEM1
Um6a3nc7LTUMXufTwBf6Sie6azubybvI2/G2HvYEn7DKpLAXiihyO8iiheAi6g4U
JtAgFUiyIvmeLh8etboF3pLy/Q8F5A==
=LFNX
-----END PGP SIGNATURE-----



                 reply	other threads:[~2018-12-25  9:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181225092742.albj7cf3suxw4hyj@aurora.visucore.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-core-dev@lists.linuxfoundation.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=matt@bluematt.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox