From: Chun Wang <1240902@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Fri, 13 Nov 2015 04:20:45 +0800 [thread overview]
Message-ID: <CAFzgq-xZA7VApQJv-b9n12H+GmL7u4Qv_481UsHWNqXGn6NubA@mail.gmail.com> (raw)
In-Reply-To: <201511122012.29966.luke@dashjr.org>
I doubt changing the default value is useful as casual mining had long
dead, and pools all have their own customized policies. But I think
change the priority size to 0 is the right way to do. The sort by
priority part in the block is always the best place for spam nowadays.
I would think about to merge the priority, feerate, and probably
sigoprate into one number, probably 576 priorities trade for 1 satoshi
per kb?
On Fri, Nov 13, 2015 at 4:12 AM, 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:
>> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-11-12 20:20 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 [this message]
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=CAFzgq-xZA7VApQJv-b9n12H+GmL7u4Qv_481UsHWNqXGn6NubA@mail.gmail.com \
--to=1240902@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/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