New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.12] Update release-notes.md #7309
Conversation
maflcko
commented
Jan 7, 2016
- Transaction memory pool limiting
- Priority transactions
- Wallet transaction fees
Pending 995b9f3 to get merged. Also, I am not a native speaker, so feedback on syntax or content is appreciated. |
Transaction memory pool limiting Priority transactions Wallet transaction fees
fa19b2f
to
fabba1c
Compare
utACK (ut=english looks good but i'm not a lector)
Should we mention the tiny API change in 0.12 when using settxfee and the GUI? Still missing:
|
|
||
Sometimes, it is not possible to give good estimates, or an estimate | ||
at all. Therefore, a fallback value can be set with `-fallbackfee=<f>` | ||
(default: `FIXME`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fc7dc75
to
fa4ba40
Compare
Bitcoin Core 0.12 will have a strict maximum size on the mempool. The | ||
default value is 300 MB and can be configured with the `-maxmempool` | ||
parameter. Whenever a transaction would cause the mempool to exceed | ||
it's maximum size, the transaction with the lowest feerate will be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its
57542c3
to
fa0a391
Compare
@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) |