mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-05-19 00:11:42 +02:00
Release notes: update notes through fb52d0684
This commit is contained in:
parent
fb52d0684e
commit
97fbe67940
@ -72,16 +72,37 @@ Mining
|
|||||||
- Calls to `getblocktemplate` will fail if the segwit rule is not specified.
|
- Calls to `getblocktemplate` will fail if the segwit rule is not specified.
|
||||||
Calling `getblocktemplate` without segwit specified is almost certainly
|
Calling `getblocktemplate` without segwit specified is almost certainly
|
||||||
a misconfiguration since doing so results in lower rewards for the miner.
|
a misconfiguration since doing so results in lower rewards for the miner.
|
||||||
|
Failed calls will produce an error message describing how to enable the
|
||||||
|
segwit rule.
|
||||||
|
|
||||||
Command line option changes
|
Configuration option changes
|
||||||
---------------------------
|
----------------------------
|
||||||
|
|
||||||
The `-enablebip61` command line option (introduced in Bitcoin Core 0.17.0) is
|
- A warning is printed if an unrecognized section name is used in the
|
||||||
used to toggle sending of BIP 61 reject messages. Reject messages have no use
|
configuration file. Recognized sections are `[test]`, `[main]`, and
|
||||||
case on the P2P network and are only logged for debugging by most network
|
`[regtest]`.
|
||||||
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
|
- The `enablebip61` option (introduced in Bitcoin Core 0.17.0) is
|
||||||
local-network debugging purposes.
|
used to toggle sending of BIP 61 reject messages. Reject messages have no use
|
||||||
|
case on the P2P network and are only logged for debugging by most network
|
||||||
|
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.
|
||||||
|
|
||||||
|
- The `rpcallowip` option can no longer be used to automatically listen
|
||||||
|
on all network interfaces. Instead, the `rpcbind` parameter must also
|
||||||
|
be used to specify the IP addresses to listen on. Listening for RPC
|
||||||
|
commands over a public network connection is insecure and should be
|
||||||
|
disabled, so a warning is now printed if a user selects such a
|
||||||
|
configuration. If you need to expose RPC in order to use a tool
|
||||||
|
like Docker, ensure you only bind RPC to your localhost, e.g. `docker
|
||||||
|
run [...] -p 127.0.0.1:8332:8332` (this is an extra `:8332` over the
|
||||||
|
normal Docker port specification).
|
||||||
|
|
||||||
|
- The `rpcpassword` option now causes a startup error if the password
|
||||||
|
set in the configuration file contains a hash character (#), as it's
|
||||||
|
ambiguous whether the hash character is meant for the password or as a
|
||||||
|
comment.
|
||||||
|
|
||||||
Documentation
|
Documentation
|
||||||
-------------
|
-------------
|
||||||
@ -168,7 +189,7 @@ Updated RPCs
|
|||||||
Note: some low-level RPC changes mainly useful for testing are described
|
Note: some low-level RPC changes mainly useful for testing are described
|
||||||
in the Low-level Changes section below.
|
in the Low-level Changes section below.
|
||||||
|
|
||||||
- The `getpeerinfo` RPC now returns an additional "minfeefilter" field
|
- The `getpeerinfo` RPC now returns an additional `minfeefilter` field
|
||||||
set to the peer's BIP133 fee filter. You can use this to detect that
|
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
|
you have peers that are willing to accept transactions below the
|
||||||
default minimum relay fee.
|
default minimum relay fee.
|
||||||
@ -192,6 +213,22 @@ in the Low-level Changes section below.
|
|||||||
|
|
||||||
- See the [Mining](#mining) section for changes to `getblocktemplate`.
|
- See the [Mining](#mining) section for changes to `getblocktemplate`.
|
||||||
|
|
||||||
|
Graphical User Interface (GUI)
|
||||||
|
------------------------------
|
||||||
|
|
||||||
|
- A new Window menu is added alongside the existing File, Settings, and
|
||||||
|
Help menus. Several items from the other menus that opened new
|
||||||
|
windows have been moved to this new Window menu.
|
||||||
|
|
||||||
|
- In the Send tab, the checkbox for "pay only the required fee"
|
||||||
|
has been removed. Instead, the user can simply decrease the value in
|
||||||
|
the Custom Feerate field all the way down to the node's configured
|
||||||
|
minimum relay fee.
|
||||||
|
|
||||||
|
- In the Overview tab, the watch-only balance will be the only
|
||||||
|
balance shown if the wallet was created using the `createwallet` RPC
|
||||||
|
and the `disable_private_keys` parameter was set to true.
|
||||||
|
|
||||||
Low-level changes
|
Low-level changes
|
||||||
=================
|
=================
|
||||||
|
|
||||||
@ -216,6 +253,16 @@ Configuration
|
|||||||
deterministic wallets. This release makes specifying `-usehd` an
|
deterministic wallets. This release makes specifying `-usehd` an
|
||||||
invalid configuration option.
|
invalid configuration option.
|
||||||
|
|
||||||
|
Changes for particular platforms
|
||||||
|
--------------------------------
|
||||||
|
|
||||||
|
- On macOS, Bitcoin Core now opts out of application CPU throttling
|
||||||
|
("app nap") during initial blockchain download, when catching up from
|
||||||
|
over 100 blocks behind the current chain tip, or when reindexing chain
|
||||||
|
data. This helps prevent these operations from taking an excessively
|
||||||
|
long time because the operating system is attempting to conserve
|
||||||
|
power.
|
||||||
|
|
||||||
Credits
|
Credits
|
||||||
=======
|
=======
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user