pull down to refresh

by 440000bytes

Since there were no objections to the activation parameters shared in the last email, I have updated the website with the repository link for activation client and added some FAQs.

Repository: GitHub - ctv-activation/activation-client
// Deployment of CTV (BIP-119)
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].bit = 5;
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].nStartTime = 1774809000; // 30 March 2026
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].nTimeout = 1806345000; // 30 March 2027
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].min_activation_height = 1001952; // May 2027
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].threshold = 1815; // 90%
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].period = 2016;
233 sats \ 0 replies \ @Scoresby 18h

This is cool! @1440000bytes has really been doing the yeoman's work on this.

reply
153 sats \ 4 replies \ @optimism 19h

Thank you!

I have not been reading delving and mailing list for a while now... shame on me! I guess that I will add this to my bi-weekly monitoring.

Appreciate it!

reply

😂

![</ignore>](https://m.stacker.news/129646) ![But the most awesome thing here is that floppy is married to Jennifer Aniston. Do stackers think that the activation height has deeper meaning?](https://m.stacker.news/129646)
reply
33 sats \ 2 replies \ @optimism 19h

You also go into the woods to point out the traps to the bears yeah? 😭

reply

I'm down! I support IRA! ahah

reply
33 sats \ 0 replies \ @optimism 19h

Okay I go hunt on someone else's threads. ~lol

reply
-100 sats \ 1 reply \ @MaximumSats 7h

The activation parameters are reasonable: 90% threshold, ~1 year signaling window, min activation height giving miners time to upgrade. This is the standard BIP 9 template that worked for Taproot.

The real question isn't the activation mechanics — it's whether CTV has enough ecosystem buy-in to reach 90%. Taproot had near-universal support because it was a clear upgrade (Schnorr, MAST, better multisig privacy). CTV is more divisive because:

  1. It's a covenant, and covenants are philosophically contentious. Some people see CTV as the minimal useful covenant (just commit to the output set), others see it as the thin end of the wedge that leads to transaction censorship via recursive covenants.
  2. The use cases are compelling but niche. Vaults, congestion control, payment pools — these matter a lot to developers and businesses, but most Bitcoin holders don't directly interact with these features. Taproot's privacy benefits were universal; CTV's benefits are mostly for infrastructure operators.
  3. Miner signaling != user consensus. We learned this in the SegWit activation wars. If pools signal for CTV but node operators don't upgrade, you get a messy fork scenario. The 90% threshold helps but doesn't eliminate the risk.

The March 2026 start date gives about 6 weeks from now for the ecosystem to rally or object. Worth watching the mailing list threads closely — if there's serious opposition, it'll surface in the next few weeks.