Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 053FDC002A for ; Sun, 7 May 2023 23:59:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id CD12460B65 for ; Sun, 7 May 2023 23:59:53 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org CD12460B65 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=Tmx4HlF3 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 9OfZBj4WCTv8 for ; Sun, 7 May 2023 23:59:53 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 125FF60AE8 Received: from mail-yw1-x112a.google.com (mail-yw1-x112a.google.com [IPv6:2607:f8b0:4864:20::112a]) by smtp3.osuosl.org (Postfix) with ESMTPS id 125FF60AE8 for ; Sun, 7 May 2023 23:59:53 +0000 (UTC) Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-556f2c24a28so4140947b3.1 for ; Sun, 07 May 2023 16:59:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20221208.gappssmtp.com; s=20221208; t=1683503992; x=1686095992; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=8nH6BY4RMvfaexkn1Lg4L0cCHHqk5fzv38/67ifZc8w=; b=Tmx4HlF39Ys2R86+rJb/VXENABKaTsitinn/z4y48k8jDB3xH/pimCnXBgS/yT0qdU 75v6wxS8ecJ8IZT1GpPBkuy2v5UEN4dA/pISJeFahT2n4362BAfpU/vtIE3YWHFNQEUO oUwDHBBVduP2p3iT/VizUzDzqz8CEhb7Pt122xBvxCcvkcmr+TpSN9uoUDMCt5XcjGoZ 5obldTSDXrGy61YtQxVS0k30dyK2gQgVXt7kbhnBw6gefCpWhUaiYzjUap1IiB5ZX5Nm JKYHpeiMS9ltRGqlJI2LIQVkI3wK0zy98L4jjriby1PmXa5e/t+Pk/4ypQPgJr2vRFxg NrbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683503992; x=1686095992; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8nH6BY4RMvfaexkn1Lg4L0cCHHqk5fzv38/67ifZc8w=; b=lOzNv2fe9sLF2dXhZ9SqWTkr1SvPqViKHata4ZI1pcvTUUd85cEoNEh74ZJsTx7SlD kuyK8UlIK9fkFylcZMwGa7WswjKeU2GhRfXTPsBGFk6pQYRMdIfQWaQXvcmILeI3zPsE 52ZXkdlT1bmaQHQC16e76DmW2cV5Gfz/l930+e6oJtqhUK2EpDjOwdHKWSv6bK57g55G VvENqhHrjdxLzZE8ONq0xwcIWzRYvDbRRZo1Pru3WLDk36hcte5RE4E2VdOc9H6U83eJ oLlqXFgBPvWvX1ETcKFv4k5R+XTukqpvjDoYduBnZnezCox8BDhS82BzXp3AngJ2ZXjE 7afQ== X-Gm-Message-State: AC+VfDzMi7ujCEnpz7rQGO54+XBw2nmFEDrH77vQCQx4v6mDB+sDPmp6 xVBMg5AiGw1vARDo/FHN5HsrLVkrvAIftArvRvMMwQsVp5cW X-Google-Smtp-Source: ACHHUZ6EH1g2EW8RDjUBDGCH8VW7ZH1ifvs0dlcHxLAspa+FwFj/16ryyTL+yoexHf9GuddSKt35yiSw+OhHoExkjto= X-Received: by 2002:a81:2507:0:b0:55a:586f:3b4f with SMTP id l7-20020a812507000000b0055a586f3b4fmr9017535ywl.4.1683503991664; Sun, 07 May 2023 16:59:51 -0700 (PDT) MIME-Version: 1.0 From: Erik Aronesty Date: Sun, 7 May 2023 19:59:40 -0400 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000066b59a05fb235127" X-Mailman-Approved-At: Mon, 08 May 2023 11:54:58 +0000 Subject: [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: Sun, 07 May 2023 23:59:54 -0000 --00000000000066b59a05fb235127 Content-Type: text/plain; charset="UTF-8" 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 --00000000000066b59a05fb235127 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 w= arned about

its not a fi= x for everything, but it seems could help a bit with certain attacks=C2=A0<= /div>

--00000000000066b59a05fb235127--