diff options
| author | John Newbery <john@johnnewbery.com> | 2019-10-08 16:24:30 -0400 |
|---|---|---|
| committer | John Newbery <john@johnnewbery.com> | 2019-10-10 13:31:57 -0400 |
| commit | 9075d13153ce06cd59a45644831ecc43126e1e82 (patch) | |
| tree | 49dda7e40956d8aa488476041ea7b68ea20e8e55 | |
| parent | 04a2f326ec0f06fb4fce1c4f93500752f05dede8 (diff) | |
[docs] Add release notes for removal of REJECT reasons
| -rw-r--r-- | doc/release-notes-15437.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/release-notes-15437.md b/doc/release-notes-15437.md index 031e90ccd2..6614207757 100644 --- a/doc/release-notes-15437.md +++ b/doc/release-notes-15437.md @@ -32,3 +32,22 @@ Please use the recommended alternatives if you rely on this deprecated feature: could wait until the transaction has confirmed (taking into account the fee target they set (compare the RPC `estimatesmartfee`)) or listen for the transaction announcement by other network peers to check for propagation. + +The removal of BIP61 REJECT message support also has the following minor RPC +and logging implications: + +* `testmempoolaccept` and `sendrawtransaction` no longer return the P2P REJECT + code when a transaction is not accepted to the mempool. They still return the + verbal reject reason. + +* Log messages that previously reported the REJECT code when a transaction was + not accepted to the mempool now no longer report the REJECT code. The reason + for rejection is still reported. + +Updated RPCs +------------ + +- `testmempoolaccept` and `sendrawtransaction` no longer return the P2P REJECT + code when a transaction is not accepted to the mempool. See the Section + _Removal of reject network messages from Bitcoin Core (BIP61)_ for details on + the removal of BIP61 REJECT message support. |