From: Luke Dashjr <luke@dashjr•org>
To: Alex Morcos <morcos@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Thu, 12 Nov 2015 21:26:38 +0000 [thread overview]
Message-ID: <201511122126.39532.luke@dashjr.org> (raw)
In-Reply-To: <CAPWm=eXNFimrG1A7bxJ3i=w_iWm57r93bjfiGZwq9y8KbZ8+Qg@mail.gmail.com>
On Thursday, November 12, 2015 9:21:57 PM Alex Morcos wrote:
> To be clear Luke, its not THAT complicated to maintain the mining policy,
> but preserving the ability of people to place priority based transactions
> in a limited mempool world is quite complicated. See recently closed
> #6992.
> I think the biggest issue with #6357 is being sure the logic doesn't break
> in future changes. There are a lot of things that need to be updated in
> the right order when blocks are connected or disconnected.
That's what unit tests are for. :)
> And whats the point of having even that added extra complication if its not
> easy to place free transactions and starting priority is a decent
> approximation for mining anyway (txs can just be rebroadcast in the worst
> case).
I'm not sure what you're getting at here, but rebroadcasting won't work if
they're still in the memory pools (unless we open the door to DoS from
reprocessing the same tx over and over).
Luke
prev parent reply other threads:[~2015-11-12 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 19:47 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
2015-11-12 21:21 ` Alex Morcos
2015-11-12 21:26 ` Luke Dashjr [this message]
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=201511122126.39532.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=morcos@gmail$(echo .)com \
/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