[0.12] Update release-notes.md #7309

MarcoFalke commented at 2:35 PM on January 7, 2016: member

Transaction memory pool limiting
Priority transactions
Wallet transaction fees

MarcoFalke commented at 2:38 PM on January 7, 2016: member

Pending 995b9f385b935e4e9b9fa46e82f642204cc85cba to get merged. Also, I am not a native speaker, so feedback on syntax or content is appreciated.

Update release-notes.md

Transaction memory pool limiting

Priority transactions

Wallet transaction fees

fabba1c1a4

MarcoFalke force-pushed on Jan 7, 2016

jonasschnelli commented at 8:01 PM on January 7, 2016: contributor

utACK (ut=english looks good but i'm not a lector)

Wallet transaction fees

Should we mention the tiny API change in 0.12 when using settxfee and the GUI?

Still missing:

ban functions (setban / banlist / ban persistence)
wallet can be used with pruning
...

in doc/release-notes.md:None in 0b4ce49fac outdated

 263 | +required to get into the `m`th block from now. This is configurable
 264 | +with `-txconfirmtarget=<m>` (default: `2`).
 265 | +
 266 | +Sometimes, it is not possible to give good estimates, or an estimate
 267 | +at all. Therefore, a fallback value can be set with `-fallbackfee=<f>`
 268 | +(default: `FIXME`).

MarcoFalke commented at 8:21 PM on January 7, 2016:

This would require e420a1b (#7296)

in doc/release-notes.md:None in 0b4ce49fac outdated

 266 | +Sometimes, it is not possible to give good estimates, or an estimate
 267 | +at all. Therefore, a fallback value can be set with `-fallbackfee=<f>`
 268 | +(default: `FIXME`).
 269 | +
 270 | +At all times, Bitcoin Core will cap fees at `-maxtxfee=<x>` (default:
 271 | +0.10) BTC.

MarcoFalke commented at 8:25 PM on January 7, 2016:

Related to #7084

in doc/release-notes.md:None in 0b4ce49fac outdated

 270 | +At all times, Bitcoin Core will cap fees at `-maxtxfee=<x>` (default:
 271 | +0.10) BTC.
 272 | +Furthermore, Bitcoin Core will never create transactions smaller than
 273 | +the current minimum relay fee.
 274 | +Finally, a user can set the minimum fee rate for all transactions with
 275 | +`-mintxfee=<i>`, which defaults to 1000 satoshis per kB.

MarcoFalke commented at 8:26 PM on January 7, 2016:

This would require 995b9f3 (part of #7296 and imo a mandatory backport for 0.12)

in doc/release-notes.md:None in db0064d81e outdated

 219 | +--------------------------------
 220 | +
 221 | +Previous versions of Bitcoin Core had their mempool limited by checking
 222 | +a transaction's fees against the node's minimum relay fee. There was no
 223 | +upper bound on the size of the mempool and attackers could send massive
 224 | +amounts of transactions paying just slighly more than the default minimum

fanquake commented at 7:56 AM on January 8, 2016:

s/massive amounts of/a large number of

in doc/release-notes.md:None in db0064d81e outdated

 236 | +
 237 | +Priority transactions
 238 | +---------------------
 239 | +
 240 | +Transactions that do not pay the minimum relay fee, are called "free
 241 | +transactions" or priority transactions. Previous versions of Bitcoin

fanquake commented at 7:57 AM on January 8, 2016:

Should priority transactions be in quotes as well?

MarcoFalke commented at 9:56 AM on January 8, 2016:

I think this is the "official" term.

in doc/release-notes.md:None in db0064d81e outdated

 243 | +setting of `-limitfreerelay=<r>` (default: `r=15` kB per minute) and
 244 | +`-blockprioritysize=<s>` (default: `50000` bytes of a block's
 245 | +priority space).
 246 | +
 247 | +Priority code is planned to get moved out of from Bitcoin Core 0.13
 248 | +and the default block priority size was set to `0` in Bitcoin Core

fanquake commented at 7:58 AM on January 8, 2016:

s/was/has been

MarcoFalke commented at 9:56 AM on January 8, 2016:

Thx!

in doc/release-notes.md:None in db0064d81e outdated

 249 | +0.12.
 250 | +
 251 | +Wallet transaction fees
 252 | +-----------------------
 253 | +
 254 | +Various impromements were made how the wallet calculates transaction

fanquake commented at 8:03 AM on January 8, 2016:

s/impromements were/improvements have been made to

jonasschnelli added the label Docs and Output on Jan 8, 2016

Expand section "Wallet transaction fees" & fix format and typos fa4ba40d8c

MarcoFalke force-pushed on Jan 8, 2016

Add Replace-by-fee to release-notes fa0a391b35

in doc/release-notes.md:None in a4807b0cfb outdated

 238 | +relay fee.
 239 | +
 240 | +Bitcoin Core 0.12 will have a strict maximum size on the mempool. The
 241 | +default value is 300 MB and can be configured with the `-maxmempool`
 242 | +parameter. Whenever a transaction would cause the mempool to exceed
 243 | +it's maximum size, the transaction with the lowest feerate will be

dgenr8 commented at 4:09 PM on January 10, 2016:

its

MarcoFalke force-pushed on Jan 13, 2016

laanwj added this to the milestone 0.12.0 on Jan 13, 2016

Add fallbackfee default value fab88af4d5

laanwj merged this on Jan 13, 2016

laanwj closed this on Jan 13, 2016

laanwj referenced this in commit 2c5c2154c9 on Jan 13, 2016

MarcoFalke deleted the branch on Jan 13, 2016

MarcoFalke commented at 11:48 AM on January 13, 2016: member

Still missing:

ban functions (setban / banlist / ban persistence)

wallet can be used with pruning

... @jonasschnelli I think you are the best person to write one or two sentences about the ban functions. (I haven't looked into that at all)

DrahtBot locked this on Sep 8, 2021