diff options
| author | MacroFake <falke.marco@gmail.com> | 2022-05-17 08:24:18 +0200 |
|---|---|---|
| committer | MacroFake <falke.marco@gmail.com> | 2022-05-17 08:25:25 +0200 |
| commit | 8270740befa3d182d436f5ec4c5b4f26ca763ed8 (patch) | |
| tree | ffc8a118d409de2233bc0f4cb2dc4392fc9a7940 /doc | |
| parent | 91a42d63efaff9a7eb955802b6d9f2c768d65db0 (diff) | |
| parent | a01b92ad8672dcf4369ee9cf36a6b0157d73786c (diff) | |
| download | bitcoin-8270740befa3d182d436f5ec4c5b4f26ca763ed8.tar.xz | |
Merge bitcoin/bitcoin#25114: rpc: remove deprecated "softforks" field from getblockchaininfo
a01b92ad8672dcf4369ee9cf36a6b0157d73786c doc: add release notes about removal of the `deprecatedrpc=softforks` flag (Sebastian Falbesoner)
8c5533c7a953e79b423b465905dbfaa45ad60a49 rpc: remove deprecated "softforks" field from getblockchaininfo (Sebastian Falbesoner)
Pull request description:
Information on soft fork status has been moved from the `getblockchaininfo` RPC to the `getdeploymentinfo` RPC in #23508. The "softfork" result in `getblockchaininfo` was still available for 23.0 with the `-deprecatedrpc=softforks` configuration option, but this can be fully removed now for the next release (24.0).
ACKs for top commit:
shaavan:
ACK a01b92ad8672dcf4369ee9cf36a6b0157d73786c
ajtowns:
ACK a01b92ad8672dcf4369ee9cf36a6b0157d73786c
Tree-SHA512: 692d9d02fdf0b3c18376644a85b24b57efebf612738084c01ef47d47e41861e773688613a808e81f10ab6eec340de00eef96987a1e34d612aaf7f0a0b134d89e
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-notes.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 8462714898..f9e712ed8d 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -50,6 +50,10 @@ P2P and network changes Updated RPCs ------------ +- The `-deprecatedrpc=softforks` configuration option has been removed. The + RPC `getblockchaininfo` no longer returns the `softforks` field, which was + previously deprecated in 23.0. (#23508) Information on soft fork status is + now only available via the `getdeploymentinfo` RPC. Changes to wallet related RPCs can be found in the Wallet section below. |