From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id E96C9C002D for ; Thu, 20 Oct 2022 23:21:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id C1F49410D2 for ; Thu, 20 Oct 2022 23:21:04 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org C1F49410D2 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=S4ysmfKg X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 ux0aaWUwOCf3 for ; Thu, 20 Oct 2022 23:21:04 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D55A2400A6 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by smtp2.osuosl.org (Postfix) with ESMTPS id D55A2400A6 for ; Thu, 20 Oct 2022 23:21:03 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id EB16A5C0096; Thu, 20 Oct 2022 19:21:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 20 Oct 2022 19:21:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1666308062; x=1666394462; bh=cXsfrqpTKMCfIc1YjUGFLtmVOGmO WZ/C0YF+0IxwEwo=; b=S4ysmfKglZv6SHRJTDYI5zvLLfIeZ5tdaw0jZUDn0hfs 0PGdZMDvvhKQdL9UyjICFEe4FSs77trpbE77cf8dSWgcxMF/y917QChMTGa6xupt hsqderpjvZqaltPm90b6SF+yHuQM+BU1lGsWULQYIXnTEBcK7MvG7pGPv5ssrAIK HVacSOZboSFY12EzgFZQtkAIP7fhHgbetpYQ2p4Ur1lHLmqZHsY8wjLsqozDGcdb ONncmPy/19ZfM5hgzvgdJkZ7INEMWO4Yu98V76XTBAR3jMismSEXC4GaaeVoO4y6 A2Ku8rmJp03BvcdnKwo2N9XHvxOoveIj1QAT+LmJhQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeljedgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrvghtvghr ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg hrnhepiedvvdelieekjeeukefgtdelfeegheehleffueehteeghfelveejfeelgeevffef necuffhomhgrihhnpehpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepuhhsvghrsehpvghtvghrthhouggurdho rhhg X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 20 Oct 2022 19:21:02 -0400 (EDT) Received: by localhost (Postfix, from userid 1000) id 10EA8204BA; Thu, 20 Oct 2022 19:21:01 -0400 (EDT) Date: Thu, 20 Oct 2022 19:21:01 -0400 From: Peter Todd To: Greg Sanders , Bitcoin Protocol Discussion Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7v7nFs9Tdl9IzEvF" Content-Disposition: inline In-Reply-To: Subject: Re: [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction 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: Thu, 20 Oct 2022 23:21:05 -0000 --7v7nFs9Tdl9IzEvF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 11, 2022 at 08:50:07AM -0400, Greg Sanders via bitcoin-dev wrot= e: > Hello fellow Bitcoiners, >=20 > After looking at some fairly exotic possible transaction types, I ran into > the current policy limit requiring transactions to be 85 non-witness > serialized bytes. This was introduced as a covert fix to policy fix > for CVE-2017-12842. Later the real motivation was revealed, but the > "reasonable" constant chosen was not. >=20 > I'd like to propose relaxing this to effectively the value BlueMatt > proposed in the Great Consensus Cleanup: 65 non-witness bytes. This would > allow a single input, single output transaction with 4 bytes of OP_RETURN > padding, rather than padding out 21 bytes to get to p2wpkh size. >=20 > The alternative would be to also allow anything below 64 non-witness byte= s, > but this seems fraught with footguns for a few bytes gain. What footguns exactly? Spending a single input to OP_RETURN with no payload= is a valid use to get rid of dust in the UTXO set. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --7v7nFs9Tdl9IzEvF Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEFcyURjhyM68BBPYTJIFAPaXwkfsFAmNR19gACgkQJIFAPaXw kfsjlQf+Oda2VM423DYAw2drUaaIrdb70WLE6OvP2PRH2lLSCHio5kcpjq7AQl1L h1JB+Zuya96JJaLAUcNvoafPtUcck2H1rgvMF1FW80V2zqPfBkVwqG8bMaKxRtRa o3XmpU0r9Nkd4lYbKVUOuBX/EtTQE0pLGAwpXZbMBkXyJtRi+Y5zuJduzVVADOrS ggQfmKxRaBEp+2pEVljuZ63Y/Vejvv/+tkkVf86j+JOuFYgMo+yyQYL4YPrnQ5j0 lAlqD+kXJkanE/K0JRAbZ18U5r5ZdzHSiwLfY/l3voxjwTC2ivqY450dOoBZT8C8 3vLBuvhRhSrpvaiRVVbvKt1nuKW5/Q== =HMFx -----END PGP SIGNATURE----- --7v7nFs9Tdl9IzEvF--