public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: "Jorge Timón" <jtimon@jtimon.cc>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Thu, 12 Nov 2015 21:10:45 +0000	[thread overview]
Message-ID: <201511122110.47665.luke@dashjr.org> (raw)
In-Reply-To: <CABm2gDqnmR5eAEZj_CRJ6Q5gi8LM_chb3tBCt2=L9ojr+Ziadw@mail.gmail.com>

On Thursday, November 12, 2015 8:43:17 PM Jorge Timón wrote:
> On Thu, Nov 12, 2015 at 9:12 PM, Luke Dashjr via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > On Thursday, November 12, 2015 7:47:50 PM Matt Corallo via bitcoin-dev
> > wrote:
> >>  * Mining code will use starting priority for ease of implementation
> > 
> > This should be optional, at least for 0.12.
> 
> The ease of implementation is not gained if it's maintained optionally.

It has come to my attention maintaining the current priority algorithm is not 
even expensive, so I think I'm inclined to NACK using starting priority 
altogether. Since I am the mining maintainer for Core, I believe it's 
reasonable for me to decide on maintenance tradeoffs...

Therefore, my goal in this matter will be to review #6357 in depth to be 
merged, and follow up with #6898 based on the current default policies.

> >>  * Default block priority size will be 0
> > 
> > We should not be influencing miner policy by changing defaults.
> 
> I agree changing policy defaults is meaningless, but in this case it
> is supposed to signal deprecation of the policy option.

This is a bad idea anyway, since priority is the best metric we have right now 
for ensuring legitimate transactions get mined despite spam attacks.

Luke


  reply	other threads:[~2015-11-12 21:10 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
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 [this message]
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=201511122110.47665.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jtimon@jtimon.cc \
    /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