aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgzhao408 <gzhao408@berkeley.edu>2020-10-08 14:03:24 -0700
committergzhao408 <gzhao408@berkeley.edu>2020-10-09 08:58:47 -0700
commit88197b0769770913941a3361bff3a1c67a86f7d2 (patch)
treeb6327dce31815174c5e92476cd1a6307fdf47e71
parentc201d73df3602dac75573a0ec3fe4c86bbc02585 (diff)
[doc] release notes for max fee checking
-rw-r--r--doc/release-notes.md14
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index d5cc5e90f8..24fcc23c01 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -102,8 +102,8 @@ will trigger BIP 125 (replace-by-fee) opt-in. (#11413)
option `-deprecatedrpc=banscore` is used. The `banscore` field will be fully
removed in the next major release. (#19469)
-- The `testmempoolaccept` RPC returns `vsize` and a `fee` object with the `base` fee
- if the transaction passes validation. (#19940)
+- The `testmempoolaccept` RPC returns `vsize` and a `fees` object with the `base` fee
+ if the transaction would pass validation. (#19940)
- The `getpeerinfo` RPC now returns a `connection_type` field. This indicates
the type of connection established with the peer. It will return one of six
@@ -347,6 +347,16 @@ RPC
- Fee estimation failed
- Transaction has too long of a mempool chain
+- The `sendrawtransaction` error code for exceeding `maxfeerate` has been changed from
+ `-26` to `-25`. The error string has been changed from "absurdly-high-fee" to
+ "Fee exceeds maximum configured by user (e.g. -maxtxfee, maxfeerate)." The
+ `testmempoolaccept` RPC returns `max-fee-exceeded` rather than `absurdly-high-fee`
+ as the `reject-reason`. (#19339)
+
+- To make wallet and rawtransaction RPCs more consistent, the error message for
+ exceeding maximum feerate has been changed to "Fee exceeds maximum configured by user
+ (e.g. -maxtxfee, maxfeerate)." (#19339)
+
Tests
-----