Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id D377FC0033 for ; Sun, 20 Feb 2022 14:24:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id C24836003C for ; Sun, 20 Feb 2022 14:24:33 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.601 X-Spam-Level: X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com 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 VAkmKoF7pOxJ for ; Sun, 20 Feb 2022 14:24:32 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch [185.70.40.141]) by smtp3.osuosl.org (Postfix) with ESMTPS id D16256059D for ; Sun, 20 Feb 2022 14:24:31 +0000 (UTC) Date: Sun, 20 Feb 2022 14:24:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1645367068; bh=Y7AwbMvVUHvFXTf+J4vTAqC0/wdBeWiXPrOThgAv0xo=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=Q6nn5TGwTRlDh32ehWgbbB/31YKrnA2crkmUNLR+xSaXemk65weCZ/KQLk2lsGuZh 6gwbEpn31E/pxQ4cvvzBJ7DXLdFLLeF8Qgy5m62p7e2D4clocvMwVnVwODvyILP8N5 cGLqUAOcojLuhHg3XaTMvqEVl3cQGUgaHr0UwUOHW5WI+o8N/XzTEJi3ySn8bxC00T oopHWYY8XLspHK6idEEHFkhevJNydpPsn5iHz3VLbwjEZqDtbyknCnt9+PK6oZ5+It N+Dme2TA2uacxBMr/JwR1IjJB9t8Ia5+R/xx9XnB5oh/kUhFrCwMiOvo3WSLm3BcJd hFp2l9w27DROw== To: "damian@willtech.com.au" From: ZmnSCPxj Reply-To: ZmnSCPxj Message-ID: In-Reply-To: <590cf52920040c9cf7517b219624bbb5@willtech.com.au> References: <590cf52920040c9cf7517b219624bbb5@willtech.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Bitcoin Protocol Discussion , lightning-dev , Jeremy Subject: Re: [bitcoin-dev] [Lightning-dev] [Pre-BIP] Fee Accounts 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, 20 Feb 2022 14:24:33 -0000 Good morning DA, > Agreed, you cannot rely on a replacement transaction would somehow > invalidate a previous version of it, it has been spoken into the gossip > and exists there in mempools somewhere if it does, there is no guarantee > that anyone has ever heard of the replacement transaction as there is no > consensus about either the previous version of the transaction or its > replacement until one of them is mined and the block accepted. -DA. As I understand from the followup from Peter, the point is not "this should= never happen", rather the point is "this should not happen *more often*." Regards, ZmnSCPxj