Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id BAC4CC002D for ; Sun, 12 Jun 2022 19:17:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 95624417B4 for ; Sun, 12 Jun 2022 19:17:03 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F3BwKC3fKq64 for ; Sun, 12 Jun 2022 19:17:02 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mail-40138.protonmail.ch (mail-40138.protonmail.ch [185.70.40.138]) by smtp4.osuosl.org (Postfix) with ESMTPS id 41CF1417A3 for ; Sun, 12 Jun 2022 19:17:02 +0000 (UTC) Date: Sun, 12 Jun 2022 19:16:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1655061419; x=1655320619; bh=xDWjEqz/fWXscPZEK6sTXiWScpWAYPFey1BdahmuOTM=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=arFxbaDM8fZHeZcYYinGfUJwjlQTR2DpwC8+SKQMH6BIuAcNE4nPSi/W9rVunW+tl A/aifFM/PFuYCd5JbavSr48vNwhSv+HZEVlxYBOD9M30iUfw7wBhrpgKxWPZTaSyjR GNIVgDUZ+aHZYNFOh/oGULzL6kMpPpVRrPyx5haBSySzSo8idnMs0kO3kyQDAKeMO1 tDc3YSNeApJDrUo2XW1pZDOY1eLujv/dI4ESN9dPmukjdxPrv+RORBqKHywwN7A1wT 4Jr6kSkBXywUWMN/eEl2Mnos7saHrM3g3ztOe3wEnmrEGD7iVXEBuOvY4Zz+uPZ+bf EXn6mGn5ctSeg== To: Peter Todd From: alicexbt Reply-To: alicexbt Message-ID: In-Reply-To: References: Feedback-ID: 40602938:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sun, 12 Jun 2022 19:51:23 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Bitcoin covenants are inevitable 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, 12 Jun 2022 19:17:03 -0000 Hi Peter, > Only because the block reward goes away. If it was made to continue > indefinitely - most likely with an inflation hard fork - demand for block= space > would not be critical to Bitcoin's security. I am not completely against your proposal although 100% sure this will not = have "consensus" to be implemented. I think if bitcoin doesn't have enough = demand for block space, it should die. I will be sad if bitcoin doesn't exi= st but it should be a lesson for all the people opposing soft forks based o= n drama and politics instead of technical review. I don't see anything wrong with users paying 100x fees for opening and clos= ing LN channels. /dev/fd0 Sent with Proton Mail secure email. ------- Original Message ------- On Sunday, June 12th, 2022 at 9:06 AM, Peter Todd via bitcoin-dev wrote: > On Mon, Jun 06, 2022 at 09:02:18AM -0400, Erik Aronesty via bitcoin-dev w= rote: > > > Maintaining the security of the protocol is squarely the responsibility= of > > the Bitcoin software and the core developers > > > > Continued demand for block space is critical for Bitcoin's security. > > > Only because the block reward goes away. If it was made to continue > indefinitely - most likely with an inflation hard fork - demand for block= space > would not be critical to Bitcoin's security. > > -- > https://petertodd.org 'peter'[:-1]@petertodd.org > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev