Date: Fri, 22 Dec 2023 01:56:09 +0000
To: Luke Dashjr <luke@dashjr.org>
From: alicexbt <alicexbt@protonmail.com>
Message-ID: <Tp6LkEd_YZUe-0sI-EXRmGTaq4Om2RSKIOUsXS0GIsYW5z_MFnicWPz2hB1KZYJ1mihv0KrJT8DmnuDr1RCcIpFM9jCOy82BvRJySkO7Im8=@protonmail.com>
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
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Swift Activation - CTV
Precedence: list

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 <luke@dashjr.org> 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