forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
…itcoin#19725, bitcoin#19770, bitcoin#19877, bitcoin#20043, partial bitcoin#18878 34c8047 Merge bitcoin#19877: [test] clarify rpc_net & p2p_disconnect_ban functional tests (Wladimir J. van der Laan) e424129 Merge bitcoin#19770: RPC: getpeerinfo: Deprecate "whitelisted" field (replaced by "permissions") (MarcoFalke) f96966b Merge bitcoin#20043: doc: Add 19501 release notes (fanquake) 6a164ea Merge bitcoin#19501: send* RPCs in the wallet returns the "fee reason" (MarcoFalke) b6c8d85 Merge bitcoin#19725: [RPC] Add connection type to getpeerinfo, improve logs (MarcoFalke) f86263b Merge bitcoin#18202: refactor: consolidate sendmany and sendtoaddress code (Samuel Dobson) fab41fd partial Merge bitcoin#18878: test: Add test for conflicted wallet tx notifications (Wladimir J. van der Laan) db5bd34 Merge bitcoin#19202: log: remove deprecated `db` log category (MarcoFalke) Pull request description: ## Issue being fixed or feature implemented Regular backports from bitcoin v21 ## What was done? - bitcoin#19202 - partial bitcoin#18878 - bitcoin#18202 - bitcoin#19725 - bitcoin#19501 - bitcoin#20043 - bitcoin#19770 - bitcoin#19877 ## How Has This Been Tested? Run unit/functional tests ## Breaking Changes - (RPC) The `getpeerinfo` RPC no longer returns the `addnode` field by default. This field will be fully removed in the next major release. It can be accessed with the configuration option `-deprecatedrpc=getpeerinfo_addnode`. However, it is recommended to instead use the `connection_type` field (it will return `manual` when addnode is true) - (Settings) The `sendtoaddress` and `sendmany` RPCs accept an optional `verbose=True` argument to also return the fee reason about the sent tx. - (Settings) The `-debug=db` logging category, which was deprecated in v0.18 and replaced by `-debug=walletdb` to distinguish it from `coindb`, has been removed. - (RPC) To make RPC `sendtoaddress` more consistent with `sendmany` the following error `sendtoaddress` codes were changed from `-4` to `-6`: - Insufficient funds - Fee estimation failed - Transaction has too long of a mempool chain ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone ACKs for top commit: PastaPastaPasta: utACK 34c8047 Tree-SHA512: 725a103e04c9c7d44a79da6f3f54e7745c7fb98ec906e7228ae16f7662d568e48c015c855902ff8485f2908f0f71815e769ca394cf6c3ca2e5fd920dd39cca74
- Loading branch information
Showing
24 changed files
with
303 additions
and
194 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,8 @@ | ||
Low-level RPC Changes | ||
--------------------- | ||
|
||
- To make RPC `sendtoaddress` more consistent with `sendmany` the following error | ||
`sendtoaddress` codes were changed from `-4` to `-6`: | ||
- Insufficient funds | ||
- Fee estimation failed | ||
- Transaction has too long of a mempool chain |
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,6 @@ | ||
Updated settings | ||
---------------- | ||
|
||
- The `-debug=db` logging category, which was deprecated in v0.18 and replaced by | ||
`-debug=walletdb` to distinguish it from `coindb`, has been removed. (#6033) | ||
|
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,10 @@ | ||
|
||
New settings | ||
------------ | ||
|
||
Wallet | ||
------ | ||
|
||
- The `sendtoaddress` and `sendmany` RPCs accept an optional `verbose=True` | ||
argument to also return the fee reason about the sent tx. (#6033) | ||
|
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,10 @@ | ||
|
||
Updated RPCs | ||
------------ | ||
|
||
- The `getpeerinfo` RPC no longer returns the `addnode` field by default. This | ||
field will be fully removed in the next major release. It can be accessed | ||
with the configuration option `-deprecatedrpc=getpeerinfo_addnode`. However, | ||
it is recommended to instead use the `connection_type` field (it will return | ||
`manual` when addnode is true). (#6033) | ||
|
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
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
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
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
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
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
Oops, something went wrong.