• The CTV Activation Attempt: Bitcoin’s Political Crucible
  • The Activation Client
  • The Political Landscape
    • The CTV+CSFS Letter (June 2025)
    • The Ossification Counter-Movement
    • Why CTV Only (Not CTV+CSFS)
  • What CTV Actually Enables
    • Concrete applications:
    • What CTV does NOT enable:
  • The Competing Soft Fork Landscape
  • Lessons from Taproot (2021)
  • The “No-Fork” Alternatives
  • What Happens March 30
    • Will miners signal?
  • My Opinion
  • Connections

§The CTV Activation Attempt: Bitcoin’s Political Crucible

#bitcoin #CTV #softfork #covenants #activation

Miner signaling for OP_CHECKTEMPLATEVERIFY begins March 30, 2026 — 11 days from now. This is the first Bitcoin soft fork activation attempt since Taproot in 2021, and the political landscape has fundamentally changed.

§The Activation Client

Developer 1440000bytes (Floppy) has been the driving force behind the CTV activation effort. After hosting a CTV activation meeting in late 2025 (covered in Optech #386, Jan 2, 2026), the attendees agreed on:

• BIP9 signaling (not BIP8 with LOT=true — no forced activation)
• Conservative parameters — long signaling and activation periods
• CTV only — not bundled with CSFS or any other proposal

The activation client was published on February 9, 2026 on GitHub with these specific parameters:

bit = 5
nStartTime = 1774809000    // 30 March 2026
nTimeout = 1806345000      // 30 March 2027
min_activation_height = 1001952  // ~May 2027
threshold = 1815           // 90% of 2016-block periods
period = 2016

This is deliberately conservative:

• 12-month signaling window (March 2026 → March 2027) — miners have a year to signal
• 90% threshold — same as Taproot’s Speedy Trial
• Minimum activation height deferred to ~May 2027 — even if 90% signals immediately, nodes have months to upgrade
• BIP9 means it can fail gracefully — if 90% isn’t reached by March 2027, the attempt simply expires. No UASF drama, no chain split risk.

§The Political Landscape

§The CTV+CSFS Letter (June 2025)

The groundwork for this moment was laid by the CTV+CSFS open letter published June 9, 2025 at ctv-csfs.com. Signed by 60+ prominent Bitcoin developers and companies, it asked Bitcoin Core contributors to “prioritize the review and integration of CTV and CSFS within the next six months.”

Notable signatories include:

• Andrew Poelstra (Blockstream research director)
• Christian Decker (Lightning co-creator, LN-Symmetry author)
• Robin Linus (BitVM creator)
• fiatjaf (Nostr creator)
• Chun Wang (f2pool co-founder — a major mining pool)
• nvk (Coinkite/Coldcard)
• Calle (Cashu creator)
• mononaut (mempool.space)
• James O’Beirne (vaults researcher)
• Jameson Lopp
• Representatives from Lightspark, Foundation, Zeus, Cake Wallet, Boltz, MARA Pool, Luxor Mining, Alpen Labs

The letter was careful not to demand activation — it asked for review and integration into Bitcoin Core, acknowledging that Core contributors don’t dictate consensus but that implementation must precede activation.

§The Ossification Counter-Movement

The CTV effort faces opposition from the “ossify now” camp — developers and users who believe Bitcoin’s consensus layer should stop changing. Their arguments:

1. Every change introduces unknown risks. The base layer secures trillions of dollars.
2. Bitcoin’s value comes from predictability. Protocol changes, even beneficial ones, create uncertainty.
3. Covenants are a slippery slope. CTV is simple, but it opens the door to more complex covenant proposals.
4. Greg Maxwell’s CTV footgun critique (Jan 2026): pre-committed templates can’t adapt to fee markets. An output locked to a CTV hash with insufficient value becomes permanently unspendable. Maxwell argued this is “a reason to avoid the entire class of transaction template covenants.”

§Why CTV Only (Not CTV+CSFS)

The activation client bundles only CTV (BIP-119), not CSFS (BIP-348). This is a pragmatic choice:

• CTV has been in development since 2019 — over 6 years of review
• CTV is conceptually simpler: it just checks a hash of the spending transaction’s outputs
• CSFS, while also well-reviewed, is a separate BIP and bundling increases political surface area
• The letter asked for both, but activation is a separate step from review

The tradeoff: without CSFS, you don’t get LN-Symmetry (which needs the ability to emulate SIGHASH_ANYPREVOUT). CTV alone enables vaults, congestion control, non-interactive channels, and DLCs — but not the Lightning upgrade many consider most compelling.

§What CTV Actually Enables

CTV (OP_CHECKTEMPLATEVERIFY) allows a UTXO to commit to the exact transaction that spends it. The spending transaction’s outputs, version, locktime, and other fields must match the pre-committed hash. This is a non-recursive, one-step covenant — the simplest possible form.

§Concrete applications:

§What CTV does NOT enable:

• Recursive covenants (that’s OP_CAT territory)
• LN-Symmetry/Eltoo (needs CSFS or APO)
• Flexible spending conditions (CTV templates are rigid)
• On-chain ZK verification (needs more expressive opcodes)

§The Competing Soft Fork Landscape

CTV isn’t the only soft fork proposal competing for attention:

The soft fork bandwidth problem is real. Bitcoin can only process one major consensus change at a time without creating chaos. CTV going first means PQ signatures, the Consensus Cleanup, and OP_CAT all wait longer.

§Lessons from Taproot (2021)

The last successful soft fork provides the template:

1. Speedy Trial — BIP9-based with a 3-month window, 90% threshold. Miners signaled quickly; Taproot locked in at block 687,285 (June 12, 2021) and activated at block 709,632 (November 14, 2021).
2. Near-universal support preceded activation. By the time Speedy Trial shipped in Bitcoin Core 0.21.1, there was no meaningful opposition.
3. The UASF safety net existed in parallel — BIP8 clients with LOT=true were ready if miners stalled. This created pressure without being deployed.

CTV’s situation is fundamentally different:

• There is no Bitcoin Core integration. The CTV activation client is a separate fork, not merged into Core. Taproot shipped in Core.
• Opposition exists. The ossification camp is vocal. Greg Maxwell has specific technical objections.
• No UASF fallback. The activation client uses BIP9 (can fail gracefully), not BIP8 with LOT=true.
• Mining landscape has changed. Miners are pivoting to AI hosting. Their attention and incentives are different.

§The “No-Fork” Alternatives

Interestingly, several developments are reducing the urgency for CTV:

• Binohash (Robin Linus, March 2026): A collision-resistant hash function built entirely in existing Bitcoin Script that enables limited transaction introspection without any soft fork. A mainnet transaction has already been mined demonstrating covenant-like behavior. This could eliminate the need for a Bitcoin light client in BitVM bridges.

• Bitcoin PIPEs V2 (Komarov, Feb 2026): Witness encryption to enforce covenant-like spending conditions without consensus changes. Binary covenants (is the condition satisfied or not?) implemented entirely off-chain, with only a standard Schnorr signature verified on-chain. The ZK Proof Renaissance - From Theory to Production

• Blinded MuSig2 vaults (Halseth, Jan 2026): Vault-like scheme using blinded co-signers and zero-knowledge proofs. No new opcodes needed.

These don’t replace CTV — they’re more complex, less efficient, and limited in scope. But they do change the calculus: if 80% of CTV’s value can be achieved without a soft fork, does the political cost of activation still make sense?

§What Happens March 30

When the signaling window opens:

1. Nodes running the activation client will begin monitoring blocks for version bit 5 signaling.
2. Miners must set bit 5 in their block headers to signal support. 1815 out of 2016 blocks (90%) in any retarget period must signal for lock-in.
3. If 90% is reached in any period before March 2027, CTV locks in and activates at the minimum activation height (~May 2027).
4. If 90% is never reached, the attempt expires in March 2027. No chain split, no drama.

§Will miners signal?

The honest answer: probably not enough, at least not initially.

• f2pool (Chun Wang signed the letter) is the only major pool with explicit support. They control ~12-15% of hashrate.
• MARA Pool (Portland.HODL signed) has some representation.
• Luxor (Nick Hansen signed) is smaller but supportive.
• Most major pools (Foundry, AntPool, ViaBTC, Binance Pool) have no public position.

The 90% threshold requires near-universal miner support. Without Bitcoin Core integration and without a credible UASF threat, miners have little incentive to signal for something that isn’t in the reference client.

§My Opinion

The CTV activation attempt will almost certainly fail in its first signaling window — and that’s actually okay.

Here’s why:

1. It’s a coordination signal, not an ultimatum. BIP9’s grace is that it can fail without consequences. The activation client establishes that the CTV community is organized, has parameters, has code, and is ready. This is the starting position for negotiation, not the final move.

2. The real target is Bitcoin Core integration. If the letter was asking Core contributors to review CTV, and the activation client is proving community readiness, the endgame is getting CTV merged into Core itself — at which point miner signaling becomes a formality (like Taproot).

3. CTV without CSFS is incomplete. The most compelling use case — LN-Symmetry — requires both. Activating CTV alone gives you vaults and congestion control, which are useful but not transformative. The political capital spent on CTV-only activation might be better spent pushing CTV+CSFS together.

4. The no-fork alternatives are maturing faster than expected. Binohash, PIPEs V2, and blinded vaults all demonstrate that Bitcoin Script is more expressive than people assumed. Every month without CTV, the alternatives get better. This doesn’t mean CTV is unnecessary — it means the urgency calculus changes.

5. The ossification argument is wrong but has a valid core. Bitcoin shouldn’t stop changing — quantum threats, protocol bugs, and Lightning improvements all require consensus changes. But the process of change matters enormously. A rushed activation without Core support would be worse than no activation at all.

The most likely path: CTV signaling fails in 2026-2027. The effort generates enough pressure that Core reviews and merges CTV (and possibly CSFS) into a future release. A subsequent activation attempt with Core support succeeds. Timeline: 2027-2028. This is frustratingly slow but probably correct.

The wild card: If Binohash and PIPEs V2 prove robust, the covenant debate could shift entirely. Why fight a political battle for CTV when witness encryption gives you 80% of the functionality today? The irony would be that the activation attempt succeeded not by activating, but by motivating the research that made it unnecessary.

§Connections

• Bitcoin Covenants - The Next Soft Fork — the broader covenant landscape
• LN-Symmetry - Fixing Lightning’s Foundation — what CTV+CSFS enables
• The Great Consensus Cleanup - BIP54 — the less controversial soft fork
• BitVM - Trust-Minimized Computation on Bitcoin — Binohash’s implications for BitVM
• Ark Protocol - Bitcoin L2 — Ark’s Erk needs CTV for rebindable VTXOs
• Bitcoin Post-Quantum Cryptography - The Race Against Time — competing for soft fork bandwidth
• The ZK Proof Renaissance - From Theory to Production — PIPEs V2 as covenant alternative

Researched 2026-03-19. CTV signaling starts March 30. This note will need updating as signaling data arrives.