Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id CA9A9C0033 for ; Fri, 14 Oct 2022 15:10:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 664E26F9FA for ; Fri, 14 Oct 2022 15:10:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 664E26F9FA Authentication-Results: smtp3.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=FxSYV5X1 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 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_FAIL=0.001, SPF_HELO_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 rHPayIND2lRX for ; Fri, 14 Oct 2022 15:10:48 +0000 (UTC) X-Greylist: delayed 00:08:18 by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 15B1F60AE1 Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by smtp3.osuosl.org (Postfix) with ESMTPS id 15B1F60AE1 for ; Fri, 14 Oct 2022 15:10:47 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id D203758012B; Fri, 14 Oct 2022 11:02:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 14 Oct 2022 11:02:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1665759746; x=1665766946; bh=7RHANW8OPwqg77Na8KuRcR2usylm Vsw6Z0KRpr0hSJc=; b=FxSYV5X1Jl9J7POeH1DZg48iFzyMgSOWEMwtHHHsV8GA PRHVYfXe3PgYU4xKjhok4FbI3BQiryP0oZD57J4Mni7bsVzHbAExFeOkBFs58z7f AKkVyg8toLNaWZHSUf8f5ePaQFghoL2Z1d9tx5D+2K43j6N1qRezOibRe5E2YXhY skcdhBBBGITX5pMyX8pIDKlCjPjfETqLu5kgTm/ddxCnPNOWM/LQBoTUzEtJEMMV NHR1udgjUopvt7JHR2yyhtp6veEaTYkl+1XqajSm/AzOPzy4n02ndJR2vZUOMyzZ uc+977e1vHOs01PG2HRrLea47uaNp+KrljuCFXIKXA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeekvddgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfhfgggtuggjsehgtd erredttddvnecuhfhrohhmpefrvghtvghrucfvohguugcuoehpvghtvgesphgvthgvrhht ohguugdrohhrgheqnecuggftrfgrthhtvghrnheptddtgedtffetueekfffhffekkeeihf etuddvteejueejffegveeghfduteejhfevnecuffhomhgrihhnpehgihhthhhusgdrtgho mhdpphgvthgvrhhtohguugdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpehpvghtvgesphgvthgvrhhtohguugdrohhrgh X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Oct 2022 11:02:26 -0400 (EDT) Received: by localhost (Postfix, from userid 1000) id 4D7565F86C; Fri, 14 Oct 2022 11:02:25 -0400 (EDT) Date: Fri, 14 Oct 2022 11:02:25 -0400 From: Peter Todd To: alicexbt , Bitcoin Protocol Discussion Message-ID: References: <166567725305.12.6779598172515633768.68724733@dralias.com> <4f73l5UZxQAv3BB6YIveAjJlp-YdQa7esPYMsiO-OnNX-G8psxzWSX70WDoLuHCv_FUoIkjY-HNQEkyZKQj88tHwOOIksXKn7qdMBxkbpm0=@protonmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2aToqJcxvSypgB7P" Content-Disposition: inline In-Reply-To: <4f73l5UZxQAv3BB6YIveAjJlp-YdQa7esPYMsiO-OnNX-G8psxzWSX70WDoLuHCv_FUoIkjY-HNQEkyZKQj88tHwOOIksXKn7qdMBxkbpm0=@protonmail.com> Subject: Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate danger 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: Fri, 14 Oct 2022 15:10:49 -0000 --2aToqJcxvSypgB7P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 14, 2022 at 02:44:04AM +0000, alicexbt via bitcoin-dev wrote: > > Relay of fullrbf transactions works reasonable well > > already, unless you get unlucky with your selected peers. The only > > missing piece is a few percent of hashrate that will accept fullrbf > > replacement transactions.=20 >=20 > I don't believe relay of fullrbf transactions works well right now. The m= issing piece you mentioned is important and a real need for all full node u= sers to try fullrbf. Relay of full-rbf transactions works well right now precisely because a few implementations exist of preferential rbf peering. I'm personally running f= our nodes with it enabled, two using my own custom patches, and another two usi= ng ariad's patch: https://github.com/bitcoin/bitcoin/pull/25600 I haven't seen a lot of non-opt-in doublespends get mined. But I have seen a few now via my Alice OTS calendar. This can of course increase dramatically= as miners turn on full-rbf. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --2aToqJcxvSypgB7P Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmNJef4ACgkQLly11TVR LzeQYRAAnfy8LWaY8V2TA3nNlDYn1gDEaxCeqgawmpkIS+O3GQ4HdYPsBaYI6As+ buAKGM+KbW7Hhi4Ah6x1hUaXjHs1l1NGEHxKAE2vKcezPA8LQk5K5Lt1uuUYl/vP MgPdVQ3lZhUHhe2ywUDmGwLmjBV3n+kXZi4u9nvg4+mzEtZkAdyrAimH+AaO+og5 8iVkPWQ7iWze2+t5R1rKsCt/Nlb71kG/nj4hXYVFZdOIK/PCl9jR+zjDWh7Kcfzh z4DelwOYSFhc3+CUEDvxCfr+AgJPzrNfOQCAOIdso4X3DBHt+CRqPxHwdxvBXAYT SklZXEGJegNxRR7f0uuEzGpsI6T1Ic+bQCa3XLkD3WX+4UZtMR+VLZbVz+/5oRgE Ag6VOKBqiAtglxXd0CNihvhNgySbF6PcXlRhUSWaVNQU4gkcMHbtDJb1+Bp9Cuab OA29TnyjY4txk3dAMj3mKJEPL85ED8RAKB16MMWTd1X6Gel4M6s+WYlK3VPdaR5s qop9zBgtbmRJfR2YUiOaI7kVEv203WKm8t68Vxg5YhSsLH6BWBmpI6XqeVT8JNQU AMdoWDq6HzkLKlzkphM8gG11iWvEkU6F9v6FR/0wvFwcaP93XuHgQcFlPYRm5ISI YqnL4N/xRV1+2O71fk/iAI6PgT/c/qVjUzxlAUKlji0hZUIo3mQ= =v8m8 -----END PGP SIGNATURE----- --2aToqJcxvSypgB7P--