From: Matt Corallo <lf-lists@mattcorallo•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Thu, 12 Nov 2015 19:47:50 +0000 [thread overview]
Message-ID: <5644ECE6.9090304@mattcorallo.com> (raw)
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
next reply other threads:[~2015-11-12 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 19:47 Matt Corallo [this message]
2015-11-12 20:12 ` Luke Dashjr
2015-11-12 20:20 ` Chun Wang
2015-11-12 20:25 ` Luke Dashjr
2015-11-12 20:35 ` James Hilliard
2015-11-12 20:43 ` Jorge Timón
2015-11-12 21:10 ` Luke Dashjr
2015-11-12 21:21 ` Alex Morcos
2015-11-12 21:26 ` Luke Dashjr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5644ECE6.9090304@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox