forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
235 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,235 @@ | ||
| 23.0 Release Notes | ||
| ================== | ||
|
|
||
| Groestlcoin Core version 23.0 is now available from: | ||
|
|
||
| <https://www.groestlcoin.org/groestlcoin-core-wallet/> | ||
|
|
||
| This release includes new features, various bug fixes and performance | ||
| improvements, as well as updated translations. | ||
|
|
||
| Please report bugs using the issue tracker at GitHub: | ||
|
|
||
| <https://github.com/groestlcoin/groestlcoin/issues> | ||
|
|
||
| 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 in some cases), then run the | ||
| installer (on Windows) or just copy over `/Applications/Groestlcoin-Qt` (on Mac) | ||
| or `groestlcoind`/`groestlcoin-qt` (on Linux). | ||
|
|
||
| Upgrading directly from a version of Groestlcoin Core that has reached its EOL is | ||
| possible, but it might take some time if the data directory needs to be migrated. Old | ||
| wallet versions of Groestlcoin Core are generally supported. | ||
|
|
||
| Compatibility | ||
| ============== | ||
|
|
||
| Groestlcoin Core is supported and extensively tested on operating systems | ||
| using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Groestlcoin | ||
| Core should also work on most other Unix-like systems but is not as | ||
| frequently tested on them. It is not recommended to use Groestlcoin Core on | ||
| unsupported systems. | ||
|
|
||
| Notable changes | ||
| =============== | ||
|
|
||
| P2P and network changes | ||
| ----------------------- | ||
|
|
||
| - A groestlcoind node will no longer rumour addresses to inbound peers by default. | ||
| They will become eligible for address gossip after sending an ADDR, ADDRV2, | ||
| or GETADDR message. | ||
|
|
||
| - Before this release, Groestlcoin Core had a strong preference to try to connect only to peers that listen on port 1331. As a result of that, Groestlcoin nodes listening on non-standard ports would likely not get any Groestlcoin Core peers connecting to them. This preference has been removed. | ||
|
|
||
| - Full support has been added for the CJDNS network. See the new option `-cjdnsreachable` and [doc/cjdns.md](https://github.com/groestlcoin/groestlcoin/blob/23.0.0/doc/cjdns.md) | ||
|
|
||
| Fee estimation changes | ||
| ---------------------- | ||
|
|
||
| - Fee estimation now takes the feerate of replacement (RBF) transactions into | ||
| account. | ||
|
|
||
| Rescan startup parameter removed | ||
| -------------------------------- | ||
|
|
||
| The `-rescan` startup parameter has been removed. Wallets which require | ||
| rescanning due to corruption will still be rescanned on startup. | ||
| Otherwise, please use the `rescanblockchain` RPC to trigger a rescan. | ||
|
|
||
| Tracepoints and Userspace, Statically Defined Tracing support | ||
| ------------------------------------------------------------- | ||
|
|
||
| Groestlcoin Core release binaries for Linux now include experimental tracepoints which | ||
| act as an interface for process-internal events. These can be used for review, | ||
| debugging, monitoring, and more. The tracepoint API is semi-stable. While the API | ||
| is tested, process internals might change between releases requiring changes to the | ||
| tracepoints. Information about the existing tracepoints can be found under | ||
| [doc/tracing.md](https://github.com/groestlcoin/groestlcoin/blob/23.0.0/doc/tracing.md) and | ||
| usage examples are provided in [contrib/tracing/](https://github.com/groestlcoin/groestlcoin/blob/23.0.0/contrib/tracing). | ||
|
|
||
| Updated RPCs | ||
| ------------ | ||
|
|
||
| - The `validateaddress` RPC now returns an `error_locations` array for invalid | ||
| addresses, with the indices of invalid character locations in the address (if | ||
| known). For example, this will attempt to locate up to two Bech32 errors, and | ||
| return their locations if successful. Success and correctness are only guaranteed | ||
| if fewer than two substitution errors have been made. | ||
| The error message returned in the `error` field now also returns more specific | ||
| errors when decoding fails. | ||
|
|
||
| - The `-deprecatedrpc=addresses` configuration option has been removed. RPCs | ||
| `gettxout`, `getrawtransaction`, `decoderawtransaction`, `decodescript`, | ||
| `gettransaction verbose=true` and REST endpoints `/rest/tx`, `/rest/getutxos`, | ||
| `/rest/block` no longer return the `addresses` and `reqSigs` fields, which | ||
| were previously deprecated in 22.0. | ||
| - The `getblock` RPC command now supports verbosity level 3 containing transaction inputs' | ||
| `prevout` information. The existing `/rest/block/` REST endpoint is modified to contain | ||
| this information too. Every `vin` field will contain an additional `prevout` subfield | ||
| describing the spent output. `prevout` contains the following keys: | ||
| - `generated` - true if the spent coins was a coinbase. | ||
| - `height` | ||
| - `value` | ||
| - `scriptPubKey` | ||
|
|
||
| - The top-level fee fields `fee`, `modifiedfee`, `ancestorfees` and `descendantfees` | ||
| returned by RPCs `getmempoolentry`,`getrawmempool(verbose=true)`, | ||
| `getmempoolancestors(verbose=true)` and `getmempooldescendants(verbose=true)` | ||
| are deprecated and will be removed in the next major version (use | ||
| `-deprecated=fees` if needed in this version). The same fee fields can be accessed | ||
| through the `fees` object in the result. WARNING: deprecated | ||
| fields `ancestorfees` and `descendantfees` are denominated in gros, whereas all | ||
| fields in the `fees` object are denominated in GRS. | ||
|
|
||
| - Both `createmultisig` and `addmultisigaddress` now include a `warnings` | ||
| field, which will show a warning if a non-legacy address type is requested | ||
| when using uncompressed public keys. | ||
|
|
||
| Changes to wallet related RPCs can be found in the Wallet section below. | ||
|
|
||
| New RPCs | ||
| -------- | ||
|
|
||
| - Information on soft fork status has been moved from `getblockchaininfo` | ||
| to the new `getdeploymentinfo` RPC which allows querying soft fork status at any | ||
| block, rather than just at the chain tip. Inclusion of soft fork | ||
| status in `getblockchaininfo` can currently be restored using the | ||
| configuration `-deprecatedrpc=softforks`, but this will be removed in | ||
| a future release. Note that in either case, the `status` field | ||
| now reflects the status of the current block rather than the next | ||
| block. | ||
|
|
||
| Files | ||
| ----- | ||
|
|
||
| * On startup, the list of banned hosts and networks (via `setban` RPC) in | ||
| `banlist.dat` is ignored and only `banlist.json` is considered. Groestlcoin Core | ||
| version 22.0 is the only version that can read `banlist.dat` and also write | ||
| it to `banlist.json`. If `banlist.json` already exists, version 22.0 will not | ||
| try to translate the `banlist.dat` into json. After an upgrade, `listbanned` | ||
| can be used to double check the parsed entries. | ||
|
|
||
| Updated settings | ||
| ---------------- | ||
|
|
||
| - In previous releases, the meaning of the command line option | ||
| `-persistmempool` (without a value provided) incorrectly disabled mempool | ||
| persistence. `-persistmempool` is now treated like other boolean options to | ||
| mean `-persistmempool=1`. Passing `-persistmempool=0`, `-persistmempool=1` | ||
| and `-nopersistmempool` is unaffected. | ||
|
|
||
| - `-maxuploadtarget` now allows human readable byte units [k|K|m|M|g|G|t|T]. | ||
| E.g. `-maxuploadtarget=500g`. No whitespace, +- or fractions allowed. | ||
| Default is `M` if no suffix provided. | ||
|
|
||
| - If `-proxy=` is given together with `-noonion` then the provided proxy will | ||
| not be set as a proxy for reaching the Tor network. So it will not be | ||
| possible to open manual connections to the Tor network for example with the | ||
| `addnode` RPC. To mimic the old behavior use `-proxy=` together with | ||
| `-onlynet=` listing all relevant networks except `onion`. | ||
|
|
||
| Tools and Utilities | ||
| ------------------- | ||
|
|
||
| - Update `-getinfo` to return data in a user-friendly format that also reduces vertical space. | ||
|
|
||
| - CLI `-addrinfo` now returns a single field for the number of `onion` addresses | ||
| known to the node instead of separate `torv2` and `torv3` fields, as support | ||
| for Tor V2 addresses was removed from Groestlcoin Core in 22.0. | ||
|
|
||
| Wallet | ||
| ------ | ||
|
|
||
| - Descriptor wallets are now the default wallet type. Newly created wallets | ||
| will use descriptors unless `descriptors=false` is set during `createwallet`, or | ||
| the `Descriptor wallet` checkbox is unchecked in the GUI. | ||
|
|
||
| Note that wallet RPC commands like `importmulti` and `dumpprivkey` cannot be | ||
| used with descriptor wallets, so if your client code relies on these commands | ||
| without specifying `descriptors=false` during wallet creation, you will need | ||
| to update your code. | ||
|
|
||
| - Newly created descriptor wallets will contain an automatically generated `tr()` | ||
| descriptor which allows for creating single key Taproot receiving addresses. | ||
|
|
||
| - `upgradewallet` will now automatically flush the keypool if upgrading | ||
| from a non-HD wallet to an HD wallet, to immediately start using the | ||
| newly-generated HD keys. | ||
|
|
||
| - a new RPC `newkeypool` has been added, which will flush (entirely | ||
| clear and refill) the keypool. | ||
|
|
||
| - `listunspent` now includes `ancestorcount`, `ancestorsize`, and | ||
| `ancestorfees` for each transaction output that is still in the mempool. | ||
|
|
||
| - `lockunspent` now optionally takes a third parameter, `persistent`, which | ||
| causes the lock to be written persistently to the wallet database. This | ||
| allows UTXOs to remain locked even after node restarts or crashes. | ||
|
|
||
| - `receivedby` RPCs now include coinbase transactions. Previously, the | ||
| following wallet RPCs excluded coinbase transactions: `getreceivedbyaddress`, | ||
| `getreceivedbylabel`, `listreceivedbyaddress`, `listreceivedbylabel`. This | ||
| release changes this behaviour and returns results accounting for received | ||
| coins from coinbase outputs. The previous behaviour can be restored using the | ||
| configuration `-deprecatedrpc=exclude_coinbase`, but may be removed in a | ||
| future release. | ||
|
|
||
| - A new option in the same `receivedby` RPCs, `include_immature_coinbase` | ||
| (default=`false`), determines whether to account for immature coinbase | ||
| transactions. Immature coinbase transactions are coinbase transactions that | ||
| have 121 or fewer confirmations, and are not spendable. | ||
|
|
||
| GUI changes | ||
| ----------- | ||
|
|
||
| - UTXOs which are locked via the GUI are now stored persistently in the | ||
| wallet database, so are not lost on node shutdown or crash. | ||
|
|
||
| - The Bech32 checkbox has been replaced with a dropdown for all address types, including the new Bech32m (BIP-350) standard for Taproot enabled wallets. | ||
|
|
||
| Low-level changes | ||
| ================= | ||
|
|
||
| RPC | ||
| --- | ||
|
|
||
| - `getblockchaininfo` now returns a new `time` field, that provides the chain tip time. | ||
|
|
||
| Tests | ||
| ----- | ||
|
|
||
| - For the `regtest` network the activation heights of several softforks were | ||
| set to block height 1. They can be changed by the runtime setting | ||
| `-testactivationheight=name@height`. | ||
|
|
||
| Credits | ||
| ======= | ||
|
|
||
| Thanks to everyone who directly contributed to this release. | ||
|
|
||
| As well as to everyone that helped with translations on | ||
| [Transifex](https://www.transifex.com/bitcoin/bitcoin/). |