summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Corallo <lf-lists@mattcorallo.com>2015-11-12 19:47:50 +0000
committerbitcoindev <bitcoindev@gnusha.org>2015-11-12 19:47:54 +0000
commit05619184288d0e85e20fba60256cb18deb858c92 (patch)
tree035785a1b99b8d70a56b24a8ab8db2b4e44dd92f
parentdb1d430fd9111c184e3120abc5b496ee934ecb0e (diff)
downloadpi-bitcoindev-05619184288d0e85e20fba60256cb18deb858c92.tar.gz
pi-bitcoindev-05619184288d0e85e20fba60256cb18deb858c92.zip
[bitcoin-dev] Upcoming Transaction Priority Changes
-rw-r--r--23/1d41d0f325f557a18a2af9c45cb0cb020e0cfc69
1 files changed, 69 insertions, 0 deletions
diff --git a/23/1d41d0f325f557a18a2af9c45cb0cb020e0cfc b/23/1d41d0f325f557a18a2af9c45cb0cb020e0cfc
new file mode 100644
index 000000000..f00313a0e
--- /dev/null
+++ b/23/1d41d0f325f557a18a2af9c45cb0cb020e0cfc
@@ -0,0 +1,69 @@
+Return-Path: <lf-lists@mattcorallo.com>
+Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
+ [172.17.192.35])
+ by mail.linuxfoundation.org (Postfix) with ESMTPS id 1A9EA405
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Thu, 12 Nov 2015 19:47:54 +0000 (UTC)
+X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
+Received: from mail.bluematt.me (mail.bluematt.me [192.241.179.72])
+ by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BE94D233
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Thu, 12 Nov 2015 19:47:53 +0000 (UTC)
+Received: from [172.17.0.1] (gw.vpn.bluematt.me [162.243.132.6])
+ by mail.bluematt.me (Postfix) with ESMTPSA id 3504159E7F
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Thu, 12 Nov 2015 19:47:52 +0000 (UTC)
+To: bitcoin-dev@lists.linuxfoundation.org
+From: Matt Corallo <lf-lists@mattcorallo.com>
+X-Enigmail-Draft-Status: N1110
+Message-ID: <5644ECE6.9090304@mattcorallo.com>
+Date: Thu, 12 Nov 2015 19:47:50 +0000
+User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
+ Thunderbird/38.3.0
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
+ version=3.3.1
+X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
+ smtp1.linux-foundation.org
+Subject: [bitcoin-dev] Upcoming Transaction Priority Changes
+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
+X-Mailman-Version: 2.1.12
+Precedence: list
+List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
+List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
+List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
+List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
+List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
+List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
+X-List-Received-Date: Thu, 12 Nov 2015 19:47:54 -0000
+
+On the IRC meeting today there was a long discussion on how to handle
+the old "transaction priority" stuff in 0.12. Over time the "transaction
+priority" stuff has added a huge amount of code and taken a bunch of
+otherwise-useful developer effort. There is still some debate about its
+usefulness going forward, but there was general agreement that it will
+either be removed entirely or replaced with something a bit less costly
+to maintain some time around 0.13.
+
+With the mempool limiting stuff already in git master, high-priority
+relay is disabled when mempools are full. In addition, there was
+agreement to take the following steps for 0.12:
+
+ * Mining code will use starting priority for ease of implementation
+ * Default block priority size will be 0
+ * Wallet will no longer create 0-fee transactions when mempool limiting
+is in effect.
+
+What this means for you is, essentially, be more careful when relying on
+priority to mine your transactions. If mempools are full, your
+transactions will be increasingly less likely to be relayed and more
+miners may start disabling high-priority block space. Make sure you
+analyze previous blocks to determine if high-priority mining is still
+enabled and ensure your transactions will be relayed.
+
+Matt
+