aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLuke Dashjr <luke-jr+git@utopios.org>2016-02-09 21:28:57 +0000
committerLuke Dashjr <luke-jr+git@utopios.org>2016-02-09 21:28:57 +0000
commitd0dbb6daeeca5eced16240e2723c0ee6ce06e8f9 (patch)
tree0f2ac0538f75a17dea12ac9bc3b8270705038625 /doc
parent73a0375ebedb3cf8c51189292ce80faa04c61fa4 (diff)
downloadbitcoin-d0dbb6daeeca5eced16240e2723c0ee6ce06e8f9.tar.xz
release-notes: Remove suggestion to use 0.11
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md4
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 3b7c2b0f69..1a9790f146 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -182,9 +182,7 @@ blocks to reserve for priority transactions. The old default was 50k, so to
retain the same policy, you must set `-blockprioritysize=50000`.
Additionally, calculation of the priority for transactions received with
-unconfirmed inputs is no longer updated correctly when they are received with
-unconfirmed inputs, so miners must continue to use 0.11 if accurate priority
-accounting is important to them.
+unconfirmed inputs is no longer updated accurately based on those inputs.
This internal automatic prioritization handling is being considered for removal
entirely in Bitcoin Core 0.13, and it is at this time undecided whether the