From: Erik Aronesty <erik@q32•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] tx max fee
Date: Mon, 8 May 2023 20:04:19 -0400 [thread overview]
Message-ID: <CAJowKg+vkzhVWRP8FbtJiPBZ_yC0ZrfGA2+GpPTS8jQ3mOq+Bg@mail.gmail.com> (raw)
In-Reply-To: <ZFmMh6A7wtjgd1Xj@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
fair. i suppose you could support cpfp in any dust filtering. im not a
fan, but I think its the only legit way to defend the chain from non money
use cases
On Mon, May 8, 2023, 7:58 PM Peter Todd <pete@petertodd•org> wrote:
> On Sun, May 07, 2023 at 07:59:40PM -0400, Erik Aronesty via bitcoin-dev
> wrote:
> > possible to change tx "max fee" to output amounts?
> >
> > seems like the only use case that would support such a tx is spam/dos
> type
> > stuff that satoshi warned about
> >
> > its not a fix for everything, but it seems could help a bit with certain
> > attacks
>
> With CPFP it often makes sense for a transaction to have a fee larger than
> the
> output amounts.
>
> This proposal would also screw over applications like my OpenTimestamps
> service.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
[-- Attachment #2: Type: text/html, Size: 1345 bytes --]
next prev parent reply other threads:[~2023-05-09 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 23:59 Erik Aronesty
2023-05-08 23:57 ` Peter Todd
2023-05-09 0:04 ` Erik Aronesty [this message]
2023-05-10 16:19 vjudeu
2023-05-10 17:42 ` Erik Aronesty
2023-05-11 11:02 ` vjudeu
2023-05-11 12:32 ` Kalle Rosenbaum
2023-05-11 15:20 ` Andrew Baine
2023-05-12 0:06 ` Tom Harding
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=CAJowKg+vkzhVWRP8FbtJiPBZ_yC0ZrfGA2+GpPTS8jQ3mOq+Bg@mail.gmail.com \
--to=erik@q32$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--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