From: Gregory Maxwell <gmaxwell@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Changing the fee on already sent transactions
Date: Tue, 12 Mar 2013 06:06:49 -0700 [thread overview]
Message-ID: <CAAS2fgRg6PXCdZdjD4dVnqAp-m4pLgkRgTULJm2S-50Rcm2HMQ@mail.gmail.com> (raw)
In-Reply-To: <20130312094700.GA8130@savin>
On Tue, Mar 12, 2013 at 2:47 AM, Peter Todd <pete@petertodd•org> wrote:
> Followed by the actual replacement logic. We could change this logic to
> instead evaluate if the candidate replacement does not remove or
> decrease the value of any existing outputs. Adding outputs is ok.
> Changing the set of inputs is also ok, provided that there are no
> conflicts with other spent transactions. DoS attacks would be prevented
> by only forwarding/accepting into the mempool replacements that increase
> the fees paid by at least MIN_RELAY_TX_FEE * size - essentially the same
> decision to allow the broadcast of the transaction in the first place.
I _strongly_ prefer this method of addressing this concern. I think
you've hit the required requirements: pay at least all the same
inputs, increase fee by at least the min_relay_tx_fee*size.
The discussion we had on IRC where some were proposing fast expiration
would practically lower the security of Bitcoin.
While there is complexity and testing required here, getting full
branch coverage of this code would be fairly straight forward. Doing
this correctly will be easier than child-pays-for-parent and although
it does not replace child-pays-for-parent (the two techniques are
complimentary in my view) it would reduce the urgency of getting
child-pays-for-parent included.
next prev parent reply other threads:[~2013-03-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:47 Peter Todd
2013-03-12 13:06 ` Gregory Maxwell [this message]
2013-03-12 13:10 ` Luke-Jr
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=CAAS2fgRg6PXCdZdjD4dVnqAp-m4pLgkRgTULJm2S-50Rcm2HMQ@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)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