Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id E1D90C002A for ; Tue, 9 May 2023 00:05:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 9475440B9A for ; Tue, 9 May 2023 00:05:53 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 9475440B9A Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=YUkgXltQ X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.603 X-Spam-Level: X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8XXsMr8tCwm for ; Tue, 9 May 2023 00:05:51 +0000 (UTC) X-Greylist: delayed 00:09:48 by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 6AD504017B Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by smtp2.osuosl.org (Postfix) with ESMTPS id 6AD504017B for ; Tue, 9 May 2023 00:05:51 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id BA78F32009BE; Mon, 8 May 2023 19:58:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 08 May 2023 19:58:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1683590281; x=1683676681; bh=OaOHpYrfSXhit XwKAmOToJauWrPmjORJRimySU5EQrQ=; b=YUkgXltQQOl+EigKB6pe+AtguudXy GPjJFLgbuhodvo0BrsSO5NVqsZIJI/e61o7OjQLiWnGmmRyWtsPjyiyt8JLKruno uBvRYjBB2UdRyd99a6LXZzDlYCMZEMTuxRKYtW+9DE8d4R7IAlKG5+NOlZn6MeHA 5LMy4iivvmIb8X3fVD7FSCuvIVOLUMXsGzI10BIotJKeaW4F5IHKEtSZoaQqUY5J BV9ndVakt4+Tj+OOr+F95yCtJXfibSMUl/SxXGD+ttOpkKcAttaq3HqEODqoxocG ocgauD45FVY3pRKrwQ2VkMU2ecI4Q/8NtaGGh7IHPERFF2Na98vMMkZyQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefledgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrvghtvghr ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg hrnhepiedvvdelieekjeeukefgtdelfeegheehleffueehteeghfelveejfeelgeevffef necuffhomhgrihhnpehpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivg epudenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvsehpvghtvghrthhouggurdho rhhg X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 May 2023 19:58:01 -0400 (EDT) Received: by localhost (Postfix, from userid 1000) id 1A05F5F844; Mon, 8 May 2023 23:57:59 +0000 (UTC) Date: Mon, 8 May 2023 23:57:59 +0000 From: Peter Todd To: Erik Aronesty , Bitcoin Protocol Discussion Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="mZNDvK2R+XoyITLu" Content-Disposition: inline In-Reply-To: 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:05:54 -0000 --mZNDvK2R+XoyITLu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 07, 2023 at 07:59:40PM -0400, Erik Aronesty via bitcoin-dev wro= te: > possible to change tx "max fee" to output amounts? >=20 > seems like the only use case that would support such a tx is spam/dos type > stuff that satoshi warned about >=20 > 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. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --mZNDvK2R+XoyITLu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmRZjIUACgkQLly11TVR LzeKcg//dZ+lcbnG68aZbDRtQRGni1HIvCde53dbYRaLQyhKwCbvoV+DnITJhPEi ngdIOZuJyvxhOXYcLr4ZZK0/HIpuTAlA457ulvo1gTSjkbxyQ+51+GktWsfOjFdC 4lwHJj3fG3JOchTBrQrn7Uavm4mHBEv2T0PTifAgjCI96K7PtcbpuRqa4Tj5eK2Z FSbJgkgA3cKnr+Qx2b+ynzEaflFlUQU2ihDUG2LH2zlvX5NCqaOPl6/LVzmpY1YX q3TXSMrI5jTOMu7yKcOLviyVfCFgFc62g8nqFRcZM5NYGFmnOEmZqi08kXYTnjab FG5bxLjGurJ4Y9IQTdSJEfAk1QQJpH+wGkK457I1gCEjqcPQle2+Of+vFnaaZGks E7geerby9yBi7K8N9Gop+N2s8HgepgUnGfBzOiDu2dkbGXkpam0c3w4sdOB4q4bo Og3Z/4KPIwmXDlFUE2HxEd9oNsJdDwSnTGBtuyAcMVsbqpSDFIYuuN6tE3EZKfCO IA1nj0DKn8whsjbpknqmOffjiaW7+nxCXHkS3geOxNKo01656fqs3yB5dyFCtziw EO2Nqi4V+kOAS5nZO04U2f5bnOhcEFajG8d88YAyKnlI+TbYDAWCyn7s/3MfChWr SDMA6Y9/ds6BIR3pIRQarF6V79yubbiZbIDrAZaM5e2xUIVtJtM= =bFAY -----END PGP SIGNATURE----- --mZNDvK2R+XoyITLu--