Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 68994C002A for ; Tue, 9 May 2023 00:04:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 3CA2F61135 for ; Tue, 9 May 2023 00:04:34 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 3CA2F61135 Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=q32-com.20221208.gappssmtp.com header.i=@q32-com.20221208.gappssmtp.com header.a=rsa-sha256 header.s=20221208 header.b=rPR/6e3e X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjrfEM1p7EaJ for ; Tue, 9 May 2023 00:04:33 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 0852A61132 Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) by smtp3.osuosl.org (Postfix) with ESMTPS id 0852A61132 for ; Tue, 9 May 2023 00:04:32 +0000 (UTC) Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-ba21644874cso471624276.0 for ; Mon, 08 May 2023 17:04:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20221208.gappssmtp.com; s=20221208; t=1683590672; x=1686182672; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Y3u1lhNWEKc1HBJFwOMfRvPU5uXDVoWNCq3bTm9RTTI=; b=rPR/6e3ewrMOWDnS4N/hC25IzhPvdI5C3nPYKEuNlbpfEB5n7dX2GY1bJnoutf7E3i 3jnWrJKrmu8uzbHbwfTeoO0y2OyTzIezTD4QhHiPQbW/eNmtPetohyy5kA67t3QGIi6Z VvkZeyAUCls+mX+AI9r6Yqm+7BddbNJO4g7nrP08+LK+nQwSx7f90AnoglvcVtCGFUcE bDkngsHUa/2yjx8seiwqOp6HG/lFc5GEebacMUMP0DIlwCNHZohCXX7Y23Hmcjk5d9b4 3BUYWrJ2FD41pW/OfWCEGHkKAK/3USl2xtIFpZOwy7JbmB3Jq8wB8Xhit0hRYRX4nDuT FAYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683590672; x=1686182672; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y3u1lhNWEKc1HBJFwOMfRvPU5uXDVoWNCq3bTm9RTTI=; b=KFMCaHKUdgmbQ5snEarhnWmgxLOTuMThCRPrdmlgGfn9CfQmoQfvOqWD3xCCNEbo/y pdmo+s/5O/UokU0Ss+c6IQ+dF1an+Zd0OKlWoq26o5x1QVM8PIwKpoAuEZILK4V4bYg6 xQ3GW4GygCf0CawtnxdV8V1IfeKXqGx61yIz9/vblboVqEpJWOO+GL0QoEDjoBnOr2HB i4lh5WLPZwSLhfjyd6eiHDiHitzaNXHPQVa0RrINOUtb8Lewex7nQyKAHeyXiZQZISit HQUirJEprrqV37smu0CXTOOogsTvs+TND3NNR61BoXYXQQNH4kS4xMsY7gNgC6+TJFjy 7OAg== X-Gm-Message-State: AC+VfDytDqc0fs9bXs5q3F3rrDjqZot2KD+msU+rgf86S3zGcRcSPwek wakoDubzyM2ds5+wFN53njtRkH5B2KaI+Fj4kUEjFwfN2aOK X-Google-Smtp-Source: ACHHUZ7oYGt/WgG3KuLODDFvFmIN+dUalwe/0+9vulOr4klZB54ABvgMyXT3I6QuKnvqGcHuOSxsEk+lHtDMbkwZuZw= X-Received: by 2002:a25:264a:0:b0:b9e:84b0:a7b9 with SMTP id m71-20020a25264a000000b00b9e84b0a7b9mr12071944ybm.0.1683590671692; Mon, 08 May 2023 17:04:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Erik Aronesty Date: Mon, 8 May 2023 20:04:19 -0400 Message-ID: To: Peter Todd Content-Type: multipart/alternative; boundary="000000000000eef92405fb377f23" X-Mailman-Approved-At: Tue, 09 May 2023 01:59:03 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] tx max fee X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 May 2023 00:04:34 -0000 --000000000000eef92405fb377f23 Content-Type: text/plain; charset="UTF-8" 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 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 > --000000000000eef92405fb377f23 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
fair.=C2=A0 =C2=A0i suppose you could support cpfp in any= dust filtering.=C2=A0 =C2=A0im not a fan, but I think its the only legit w= ay 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 a= t 07:59:40PM -0400, Erik Aronesty via bitcoin-dev wrote:
> possible to change tx "max fee"=C2=A0 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 certa= in
> 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
--000000000000eef92405fb377f23--