From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id BC3B2C0037 for ; Fri, 22 Dec 2023 01:56:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 9DADF83D9D for ; Fri, 22 Dec 2023 01:56:18 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 9DADF83D9D Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com header.a=rsa-sha256 header.s=protonmail3 header.b=s/JwRy/2 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvqn29cP8KEd for ; Fri, 22 Dec 2023 01:56:17 +0000 (UTC) Received: from mail-4027.protonmail.ch (mail-4027.protonmail.ch [185.70.40.27]) by smtp1.osuosl.org (Postfix) with ESMTPS id 2218983D9C for ; Fri, 22 Dec 2023 01:56:16 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2218983D9C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1703210173; x=1703469373; bh=tfHnOsyzTvs3DOyIHXxBN9x8TTimCo8+u8T55r79nEA=; 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:BIMI-Selector; b=s/JwRy/2pS7KryGS0FSX5fQsL/7ipuxan3lT7jRPOdnyG7f5HvrMkRbjRsJ36egHY H8KugcYsUOsl7NcYddUibJGRGkR4ZTi6JcWx5y8gxr+K3rSq2HjHnPzTYGbpZmhLK3 GztKwkKP/p9DKs6KJq+NdPE6Y5M2H7qRMaQpcf0hjSIrupryZnrztFvQUPZ2NYrb1t 8g1125gm6isRuMzFaV4k+DWjN28UyzCB5hx7c+AJHVjKL7Uf4K3l7lUSa5DmeigVlk 8bW71GIsuOwQZErsKt6OqbR64AaXB9mlumoAkyligfvlaKqA9s5YlI2/2c3Ym+dhFT We2W22Y7R4WxA== Date: Fri, 22 Dec 2023 01:56:09 +0000 To: Luke Dashjr From: alicexbt Message-ID: In-Reply-To: <2e113332-2cfd-73ec-0368-136728ceb31a@dashjr.org> References: <39ecOLU7GJPGc0zWZmGuaj-a4ANySfoRjwxoUoxP480kfRRc_fsPl9MvZDC-0vSfrO3jYraHVUyxWpcg7AFHRJkEJUERYdHZlzimOwql1j0=@protonmail.com> <2e113332-2cfd-73ec-0368-136728ceb31a@dashjr.org> 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: Fri, 22 Dec 2023 14:26:21 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Swift Activation - CTV 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, 22 Dec 2023 01:56:18 -0000 Hi Luke, This is not the first time I am writing this but you keep ignoring it and t= hreaten with URSF. Please build BIP 8 client with LOT=3DTRUE if you think i= ts the best way to activate and share it so that users can run it. I had created this branch specifically for it but needed help which I didn'= t get: https://github.com/xbtactivation/bitcoin/tree/bip8-ctv Discussing trade-offs involved in different activation methods and providin= g options to users is not an attack. /dev/fd0 floppy disk guy Sent with Proton Mail secure email. On Friday, December 22nd, 2023 at 1:05 AM, Luke Dashjr wr= ote: > This IS INDEED an attack on Bitcoin. It does not activate CTV - it would > (if users are fooled into using it) give MINERS the OPTION to activate > CTV. Nobody should run this, and if it gets any traction, it would > behoove the community to develop and run a "URSF" making blocks > signalling for it invalid. >=20 > Luke >=20 >=20 > On 12/19/23 20:44, alicexbt via bitcoin-dev wrote: >=20 > > Hello World, > >=20 > > Note: This is not an attack on bitcoin. This is an email with some text= and links. Users can decide what works best for themselves. There is also = scope for discussion about changing method or params. > >=20 > > I want to keep it short and no energy left. I have explored different o= ptions for activation and this feels the safest at this point in 2023. I ha= ve not done any magic or innovation but updated activation params. If you a= gree with them, please run this client else build your own. Anyone who call= s this attack and do not build alternative option is an attack in itself. > >=20 > > It activates CTV which is simple covenant proposal and achieves what we= expect it to. It is upgradeable. I like simple things, at least to start w= ith. > >=20 > > Activation parameters: > >=20 > > `consensus.vDeployments[Consensus::DEPLOYMENT_COVTOOLS].nStartTime =3D = 1704067200; consensus.vDeployments[Consensus::DEPLOYMENT_COVTOOLS].nTimeout= =3D 1727740800; consensus.vDeployments[Consensus::DEPLOYMENT_COVTOOLS].min= _activation_height =3D 874874;` > >=20 > > I need payment pools and it does it for me. Apart from that it enables = vaults, congestion control etc. We have more PoCs for CTV than we had for t= aproot and I understand it better. > >=20 > > If you agree with me, please build and run this client before 01 Jan 20= 24 else we can discuss ordinals for next 5 years and activate something in = 2028. > >=20 > > Cheers > >=20 > > /dev/fd0 > > floppy disk guy > >=20 > > Sent with Proton Mail secure email. > >=20 > > _______________________________________________ > > bitcoin-dev mailing list > > bitcoin-dev@lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev