Release notes: update notes through to 11e1ac3ae0
This commit is contained in:
David A. Harding
parent
11e1ac3ae0
commit
6062f0e613
1 changed files with 87 additions and 3 deletions
|
|
@ -53,8 +53,14 @@ the Linux kernel, macOS 10.10+, and Windows 7 and newer (Windows XP is not suppo
|
|||
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.
|
||||
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. Additionally, Bitcoin Core does not yet change appearance when
|
||||
macOS "dark mode" is activated.
|
||||
|
||||
In addition to previously-supported CPU platforms, this release's
|
||||
pre-compiled distribution also provides binaries for the RISC-V
|
||||
platform.
|
||||
|
||||
Notable changes
|
||||
===============
|
||||
|
|
@ -69,9 +75,87 @@ nodes. The option will now by default be off for improved privacy and security
|
|||
as well as reduced upload usage. The option can explicitly be turned on for
|
||||
local-network debugging purposes.
|
||||
|
||||
Example item
|
||||
Documentation
|
||||
-------------
|
||||
|
||||
- A new short
|
||||
[document](https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md)
|
||||
about the JSON-RPC interface describes cases where the results of an
|
||||
RPC might contain inconsistencies between data sourced from different
|
||||
subsystems, such as wallet state and mempool state. A note is added
|
||||
to the [REST interface documentation](https://github.com/bitcoin/bitcoin/blob/master/doc/REST-interface.md)
|
||||
indicating that the same rules apply.
|
||||
|
||||
- A new [document](https://github.com/bitcoin/bitcoin/blob/master/doc/bitcoin-conf.md)
|
||||
about the `bitcoin.conf` file describes how to use it to configure
|
||||
Bitcoin Core.
|
||||
|
||||
- A new document introduces Bitcoin Core's BIP174
|
||||
[Partially-Signed Bitcoin Transactions (PSBT)](https://github.com/bitcoin/bitcoin/blob/master/doc/psbt.md)
|
||||
interface, which is used to allow multiple programs to collaboratively
|
||||
work to create, sign, and broadcast new transactions. This is useful
|
||||
for offline (cold storage) wallets, multisig wallets, coinjoin
|
||||
implementations, and many other cases where two or more programs need
|
||||
to interact to generate a complete transaction.
|
||||
|
||||
- The [output script descriptor](https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md)
|
||||
documentation has been updated with information about new features in
|
||||
this still-developing language for describing the output scripts that
|
||||
a wallet or other program wants to receive notifications for, such as
|
||||
which addresses it wants to know received payments. The language is
|
||||
currently used in the `scantxoutset` RPC and is expected to be adapted
|
||||
to other RPCs and to the underlying wallet structure.
|
||||
|
||||
Build system changes
|
||||
--------------------
|
||||
|
||||
- A new `--disable-bip70` option may be passed to `./configure` to
|
||||
prevent Bitcoin-Qt from being built with support for the BIP70 payment
|
||||
protocol or from linking libssl. As the payment protocol has exposed
|
||||
Bitcoin Core to libssl vulnerabilities in the past, builders who don't
|
||||
need BIP70 support are encouraged to use this option to reduce their
|
||||
exposure to future vulnerabilities.
|
||||
|
||||
Updated RPCs
|
||||
------------
|
||||
|
||||
- The `signrawtransaction` RPC is removed after being deprecated and
|
||||
hidden behind a special configuration option in version 0.17.0.
|
||||
|
||||
- The `getpeerinfo` RPC now returns an additional "minfeefilter" field
|
||||
set to the peer's BIP133 fee filter. You can use this to detect that
|
||||
you have peers that are willing to accept transactions below the
|
||||
default minimum relay fee.
|
||||
|
||||
- The mempool RPCs, such as `getrawmempool` with `verbose=true`, now
|
||||
return an additional "bip125-replaceable" value indicating whether the
|
||||
transaction (or its unconfirmed ancestors) opts-in to asking nodes and
|
||||
miners to replace it with a higher-feerate transaction spending any of
|
||||
the same inputs.
|
||||
|
||||
- The `settxfee` RPC previously silently ignored attempts to set the fee
|
||||
below the allowed minimums. It now prints a warning. The special
|
||||
value of "0" may still be used to request the minimum value.
|
||||
|
||||
- The `getaddressinfo` RPC now provides an `ischange` field indicating
|
||||
whether the wallet used the address in a change output.
|
||||
|
||||
Low-level changes
|
||||
=================
|
||||
|
||||
RPC
|
||||
---
|
||||
|
||||
- The `submitblock` RPC previously returned the reason a rejected block
|
||||
was invalid the first time it processed that block but returned a
|
||||
generic "duplicate" rejection message on subsequent occasions it
|
||||
processed the same block. It now always returns the fundamental
|
||||
reason for rejecting an invalid block and only returns "duplicate" for
|
||||
valid blocks it has already accepted.
|
||||
|
||||
- A new `submitheader` RPC allows submitting block headers independently
|
||||
from their block. This is likely only useful for testing.
|
||||
|
||||
Credits
|
||||
=======
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue