Changeset View
Changeset View
Standalone View
Standalone View
doc/release-notes/release-notes-0.14.0.md
Show First 20 Lines • Show All 102 Lines • ▼ Show 20 Lines | |||||
------------------------------------ | ------------------------------------ | ||||
The ability to nest RPC commands has been added to the debug console. This | The ability to nest RPC commands has been added to the debug console. This | ||||
allows users to have the output of a command become the input to another | allows users to have the output of a command become the input to another | ||||
command without running the commands separately. | command without running the commands separately. | ||||
The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can | The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can | ||||
be nested (i.e. `getblock(getblockhash(1))`). Simple queries can be | be nested (i.e. `getblock(getblockhash(1))`). Simple queries can be | ||||
done with square brackets where object values are accessed with either an | done with square brackets where object values are accessed with either an | ||||
array index or a non-quoted string (i.e. `listunspent()[0][txid]`). Both | array index or a non-quoted string (i.e. `listunspent()[0][txid]`). Both | ||||
commas and spaces can be used to separate parameters in both the bracket syntax | commas and spaces can be used to separate parameters in both the bracket syntax | ||||
and normal RPC command syntax. | and normal RPC command syntax. | ||||
Network Activity Toggle | Network Activity Toggle | ||||
----------------------- | ----------------------- | ||||
A RPC command and GUI toggle have been added to enable or disable all p2p | A RPC command and GUI toggle have been added to enable or disable all p2p | ||||
network activity. The network status icon in the bottom right hand corner | network activity. The network status icon in the bottom right hand corner | ||||
is now the GUI toggle. Clicking the icon will either enable or disable all | is now the GUI toggle. Clicking the icon will either enable or disable all | ||||
p2p network activity. If network activity is disabled, the icon will | p2p network activity. If network activity is disabled, the icon will | ||||
be grayed out with an X on top of it. | be grayed out with an X on top of it. | ||||
Additionally the `setnetworkactive` RPC command has been added which does | Additionally the `setnetworkactive` RPC command has been added which does | ||||
the same thing as the GUI icon. The command takes one boolean parameter, | the same thing as the GUI icon. The command takes one boolean parameter, | ||||
`true` enables networking and `false` disables it. | `true` enables networking and `false` disables it. | ||||
Out-of-sync Modal Info Layer | Out-of-sync Modal Info Layer | ||||
---------------------------- | ---------------------------- | ||||
▲ Show 20 Lines • Show All 53 Lines • ▼ Show 20 Lines | |||||
to a `mempool.dat` file. This file preserves the mempool so that when the node | to a `mempool.dat` file. This file preserves the mempool so that when the node | ||||
restarts the mempool can be filled with transactions without waiting for new transactions | restarts the mempool can be filled with transactions without waiting for new transactions | ||||
to be created. This will also preserve any changes made to a transaction through | to be created. This will also preserve any changes made to a transaction through | ||||
commands such as `prioritisetransaction` so that those changes will not be lost. | commands such as `prioritisetransaction` so that those changes will not be lost. | ||||
Final Alert | Final Alert | ||||
----------- | ----------- | ||||
The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in Bitcoin Core 0.12.1 and removed in 0.13.0. | The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in Bitcoin Core 0.12.1 and removed in 0.13.0. | ||||
The Alert System was retired with a maximum sequence final alert which causes any nodes | The Alert System was retired with a maximum sequence final alert which causes any nodes | ||||
supporting the Alert System to display a static hard-coded "Alert Key Compromised" message which also | supporting the Alert System to display a static hard-coded "Alert Key Compromised" message which also | ||||
prevents any other alerts from overriding it. This final alert is hard-coded into this release | prevents any other alerts from overriding it. This final alert is hard-coded into this release | ||||
so that all old nodes receive the final alert. | so that all old nodes receive the final alert. | ||||
GUI Changes | GUI Changes | ||||
----------- | ----------- | ||||
- After resetting the options by clicking the `Reset Options` button | - After resetting the options by clicking the `Reset Options` button | ||||
in the options dialog or with the `-resetguioptions` startup option, | in the options dialog or with the `-resetguioptions` startup option, | ||||
the user will be prompted to choose the data directory again. This | the user will be prompted to choose the data directory again. This | ||||
is to ensure that custom data directories will be kept after the | is to ensure that custom data directories will be kept after the | ||||
option reset which clears the custom data directory set via the choose | option reset which clears the custom data directory set via the choose | ||||
datadir dialog. | datadir dialog. | ||||
- Multiple peers can now be selected in the list of peers in the debug | - Multiple peers can now be selected in the list of peers in the debug | ||||
window. This allows for users to ban or disconnect multiple peers | window. This allows for users to ban or disconnect multiple peers | ||||
simultaneously instead of banning them one at a time. | simultaneously instead of banning them one at a time. | ||||
- An indicator has been added to the bottom right hand corner of the main | - An indicator has been added to the bottom right hand corner of the main | ||||
window to indicate whether the wallet being used is a HD wallet. This | window to indicate whether the wallet being used is a HD wallet. This | ||||
icon will be grayed out with an X on top of it if the wallet is not a | icon will be grayed out with an X on top of it if the wallet is not a | ||||
HD wallet. | HD wallet. | ||||
Low-level RPC changes | Low-level RPC changes | ||||
---------------------- | ---------------------- | ||||
- `importprunedfunds` only accepts two required arguments. Some versions accept | - `importprunedfunds` only accepts two required arguments. Some versions accept | ||||
an optional third arg, which was always ignored. Make sure to never pass more | an optional third arg, which was always ignored. Make sure to never pass more | ||||
than two arguments. | than two arguments. | ||||
- The first boolean argument to `getaddednodeinfo` has been removed. This is | - The first boolean argument to `getaddednodeinfo` has been removed. This is | ||||
an incompatible change. | an incompatible change. | ||||
- RPC command `getmininginfo` loses the "testnet" field in favor of the more | - RPC command `getmininginfo` loses the "testnet" field in favor of the more | ||||
generic "chain" (which has been present for years). | generic "chain" (which has been present for years). | ||||
- A new RPC command `preciousblock` has been added which marks a block as | - A new RPC command `preciousblock` has been added which marks a block as | ||||
precious. A precious block will be treated as if it were received earlier | precious. A precious block will be treated as if it were received earlier | ||||
than a competing block. | than a competing block. | ||||
- A new RPC command `importmulti` has been added which receives an array of | - A new RPC command `importmulti` has been added which receives an array of | ||||
JSON objects representing the intention of importing a public key, a | JSON objects representing the intention of importing a public key, a | ||||
private key, an address and script/p2sh | private key, an address and script/p2sh | ||||
- Use of `getrawtransaction` for retrieving confirmed transactions with unspent | - Use of `getrawtransaction` for retrieving confirmed transactions with unspent | ||||
outputs has been deprecated. For now this will still work, but in the future | outputs has been deprecated. For now this will still work, but in the future | ||||
it may change to only be able to retrieve information about transactions in | it may change to only be able to retrieve information about transactions in | ||||
the mempool or if `txindex` is enabled. | the mempool or if `txindex` is enabled. | ||||
- A new RPC command `getmemoryinfo` has been added which will return information | - A new RPC command `getmemoryinfo` has been added which will return information | ||||
about the memory usage of Bitcoin Core. This was added in conjunction with | about the memory usage of Bitcoin Core. This was added in conjunction with | ||||
optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753) | optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753) | ||||
for more information. | for more information. | ||||
- A new RPC command `bumpfee` has been added which allows replacing an | - A new RPC command `bumpfee` has been added which allows replacing an | ||||
unconfirmed wallet transaction that signaled RBF (see the `-walletrbf` | unconfirmed wallet transaction that signaled RBF (see the `-walletrbf` | ||||
startup option above) with a new transaction that pays a higher fee, and | startup option above) with a new transaction that pays a higher fee, and | ||||
should be more likely to get confirmed quickly. | should be more likely to get confirmed quickly. | ||||
HTTP REST Changes | HTTP REST Changes | ||||
----------------- | ----------------- | ||||
- UTXO set query (`GET /rest/getutxos/<checkmempool>/<txid>-<n>/<txid>-<n> | - UTXO set query (`GET /rest/getutxos/<checkmempool>/<txid>-<n>/<txid>-<n> | ||||
/.../<txid>-<n>.<bin|hex|json>`) responses were changed to return status | /.../<txid>-<n>.<bin|hex|json>`) responses were changed to return status | ||||
code `HTTP_BAD_REQUEST` (400) instead of `HTTP_INTERNAL_SERVER_ERROR` (500) | code `HTTP_BAD_REQUEST` (400) instead of `HTTP_INTERNAL_SERVER_ERROR` (500) | ||||
when requests contain invalid parameters. | when requests contain invalid parameters. | ||||
Minimum Fee Rate Policies | Minimum Fee Rate Policies | ||||
------------------------- | ------------------------- | ||||
Since the changes in 0.12 to automatically limit the size of the mempool and improve the performance of block creation in mining code it has not been important for relay nodes or miners to set `-minrelaytxfee`. With this release the following concepts that were tied to this option have been separated out: | Since the changes in 0.12 to automatically limit the size of the mempool and improve the performance of block creation in mining code it has not been important for relay nodes or miners to set `-minrelaytxfee`. With this release the following concepts that were tied to this option have been separated out: | ||||
- incremental relay fee used for calculating BIP 125 replacement and mempool limiting. (1000 satoshis/kB) | - incremental relay fee used for calculating BIP 125 replacement and mempool limiting. (1000 satoshis/kB) | ||||
▲ Show 20 Lines • Show All 608 Lines • Show Last 20 Lines |