From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
Matt Corallo <lf-lists@mattcorallo.com>
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Thu, 12 Nov 2015 20:12:28 +0000 [thread overview]
Message-ID: <201511122012.29966.luke@dashjr.org> (raw)
In-Reply-To: <5644ECE6.9090304@mattcorallo.com>
On Thursday, November 12, 2015 7:47:50 PM Matt Corallo via bitcoin-dev wrote:
> 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
This should be optional, at least for 0.12.
> * Default block priority size will be 0
We should not be influencing miner policy by changing defaults.
Luke
next prev parent reply other threads:[~2015-11-12 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 19:47 [bitcoin-dev] Upcoming Transaction Priority Changes Matt Corallo
2015-11-12 20:12 ` Luke Dashjr [this message]
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=201511122012.29966.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lf-lists@mattcorallo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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