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 F0E36C002D for ; Tue, 11 Oct 2022 16:25:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id D2E7E409FF for ; Tue, 11 Oct 2022 16:25:26 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D2E7E409FF Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=wuille.net header.i=@wuille.net header.a=rsa-sha256 header.s=protonmail3 header.b=lChOuq51 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.598 X-Spam-Level: X-Spam-Status: No, score=0.598 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 uXWedVj0UCfr for ; Tue, 11 Oct 2022 16:25:25 +0000 (UTC) X-Greylist: delayed 00:06:48 by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org CF448402E7 Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch [185.70.41.103]) by smtp2.osuosl.org (Postfix) with ESMTPS id CF448402E7 for ; Tue, 11 Oct 2022 16:25:23 +0000 (UTC) Date: Tue, 11 Oct 2022 16:18:10 +0000 Authentication-Results: mail-41103.protonmail.ch; dkim=pass (2048-bit key) header.d=wuille.net header.i=@wuille.net header.b="lChOuq51" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wuille.net; s=protonmail3; t=1665505102; x=1665764302; bh=w+5E4+W89vtUT45/taZ2hONHHqbYIIIR6tu6fo0bIjA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=lChOuq51TyaKTSN2y5/tph/Uty6Tv1z6eYeBGIIO6lgwdHPPPN/c1JDiHegJRO1q9 aQJGNJY4NlwsQF5iY0fOv4DEWSJnRqcJwSYkq1Rd9twmFYSK7OmwQuur59EZhqOVhD eDuTK5xkbGpXIf0e4isqPO0hcdjw1mWEJiUBX1P/kX0uKlxOlpLJkg0q5V5/iNgjyq l6SK8TFqDCjTBVkp/HRJ9RcGZooNxkAtBfFMsW1ez0wIPYRpFdxyvttH8XSWPFwd8y ofA5Ip3PO3tRmTk1zQjoyOJH0ZbSWD5m9tIQDJ6azYtjCM4jnDyCg8KUGUl3Qy4Q1v VSzWF8HXVbvSw== To: Dario Sneidermanis , Bitcoin Protocol Discussion From: Pieter Wuille Message-ID: In-Reply-To: References: <1ee5a4e7ecffa0f638bbd45b195ecca6@dtrt.org> Feedback-ID: 19463299:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 11 Oct 2022 19:46:56 +0000 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: Tue, 11 Oct 2022 16:25:27 -0000 On Friday, October 7th, 2022 at 5:37 PM, Dario Sneidermanis via bitcoin-dev= wrote: > Hello David, >=20 > Thanks for the fast answer! It seems I missed the link to the PR, sorry f= or the > confusion. I'm referring to the opt-in flag for full-RBF from #25353 > (https://github.com/bitcoin/bitcoin/pull/25353). Hello Dario, It is not clear to me why you believe the merging of this particular pull r= equest poses an immediate risk to you. As explained by others, it's only a configuration option that is default of= f, and the possibility of running rull-RBF policy nodes on the network have= been trivial for anyone who wanted to for a long time on the network. I don't want to sound dismissive of your concerns, but at this point I'm no= t convinced you're actually aware of what this PR does and doesn't do. Cheers, --=20 Pieter