aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLuke Dashjr <luke-jr+git@utopios.org>2016-02-09 08:13:38 +0000
committerLuke Dashjr <luke-jr+git@utopios.org>2016-02-09 08:13:38 +0000
commit73a0375ebedb3cf8c51189292ce80faa04c61fa4 (patch)
tree67570ba27214d4a50cdeeea7bbc8e9fa900c8c7c /doc
parent4b8d2bc625a15adb2402fe91f7acb9d233153ed9 (diff)
downloadbitcoin-73a0375ebedb3cf8c51189292ce80faa04c61fa4.tar.xz
release-notes: Mention possibility of priority removal in 0.13, uncertainty of priority calculation being changed back, and request community input
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 5db30c33af..3b7c2b0f69 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -186,6 +186,12 @@ 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.
+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
+inaccurate priority calculation will be fixed or left as-is in future releases.
+Community direction on this topic is particularly requested to help set project
+priorities.
+
Automatically use Tor hidden services
-------------------------------------