diff options
| author | Matt Corallo <git@bluematt.me> | 2017-08-25 11:27:03 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2017-11-02 15:18:56 -0400 |
| commit | bb83fe19026b4d86a6514e6f3ed5f4d71f1bc4bc (patch) | |
| tree | 6ee383a28fcaf9209373627f55ca5f071fb913a2 | |
| parent | 4c82cea99b514193672d8145c7777f3e715694ec (diff) | |
| download | bitcoin-bb83fe19026b4d86a6514e6f3ed5f4d71f1bc4bc.tar.xz | |
Add release notes describing blockmaxweight deprecation
Github-Pull: #11100
Rebased-From: 6f703e9bf11c5f2fcb0fca0e4243fce6b4b9d35a
| -rw-r--r-- | doc/release-notes.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 1bb02e3761..6e4bd03cd5 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -72,6 +72,22 @@ Notable changes value is passed, instead of returning a list of all wallet transactions since the genesis block. +Miner block size limiting deprecated +------------------------------------ + +Though blockmaxweight has been preferred for limiting the size of blocks returned by +getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished +to limit their block size directly. Using this option resulted in a few UI issues as +well as non-optimal fee selection and ever-so-slightly worse performance, and has thus +now been deprecated. Further, the blockmaxsize option is now used only to calculate an +implied blockmaxweight, instead of limiting block size directly. Any miners who wish +to limit their blocks by size, instead of by weight, will have to do so manually by +removing transactions from their block template directly. + +Low-level RPC changes +---------------------- +- The "currentblocksize" value in getmininginfo has been removed. + Credits ======= |