Emerging Grassroots Support for Bitcoin Improvement Proposals
Grassroots support is steadily building for two significant Bitcoin Improvement Proposals (BIPs) as the Bitcoin community gears up for its next soft fork. These proposals, identified as BIPs 119 and 348, represent critical advancements in Bitcoin’s functionality. BIPs serve as the official method for discussing potential changes to the Bitcoin protocol. When a BIP garners substantial support, it can be integrated into Bitcoin through a soft fork or a standard update to Bitcoin Core. Often, these proposals are referred to by their nicknames, and multiple BIPs can be included in a single soft fork. Specifically, BIP 119 introduces OP_CHECKTEMPLATEVERIFY (CTV), while BIP 348 presents OP_CHECKSIGFROMSTACK (CSFS).
This article originally appeared in Blockspace Media, the leading publication dedicated to Bitcoin technology, markets, mining, and ordinals. To receive Blockspace articles directly in your inbox, click here.
The Dynamics of Bitcoin’s Technical Community
Bitcoin’s technical community usually engages in thorough debates surrounding these BIPs. The Taproot Wizards, a development firm recognized for its contributions to Bitcoin NFTs, recently shared a detailed graphic that clarifies the complex and often circular nature of these discussions. In essence, the soft fork process requires a rough estimate of support from various stakeholders in the Bitcoin ecosystem, including developers, custodians, investors, and miners. Miners, in particular, act as a reliable proxy for this support, as they can signal their endorsement for changes in their mined blocks. Typically, Bitcoin Core seeks a consensus of 95% of blocks over a specified period to signal support for a proposed update before it is officially locked in for activation.
However, defining what constitutes “widespread support” remains a challenge, as Bitcoin consensus is a continually evolving phenomenon. Miners provide a tangible means of signaling change due to their countable presence on the Bitcoin network, making it difficult to assess broader consensus given Bitcoin’s decentralized nature.
Recent Developments in BIP Support
In recent weeks, a noticeable shift has emerged, with numerous developers publicly expressing their support for both BIPs. This trend is a strong indication that the Bitcoin community, particularly on social media platforms like Twitter, is coalescing around these proposed changes.
What’s in a Proposal?
Both CTV and CSFS open new avenues for writing Bitcoin scripts, which are the foundational programming language utilized for creating and processing transactions. CTV, proposed by former Bitcoin core contributor Jeremy Rubin, has been under consideration for over five years, while CSFS was formally introduced in November 2024 by Rubin and developer Brandon Black. The activation of these two BIPs would introduce “covenants” to Bitcoin, which are mechanisms that impose restrictions on how a wallet can spend its bitcoin in future transactions. This functionality is anticipated to greatly enhance self-custody, fee management, and existing technologies like Lightning, Ark, and contract-based applications.
Moreover, developers regard these proposals as “narrowly defined,” suggesting a low risk of unexpected exploitation should they be activated. The Bitcoin developer community is known for its cautious approach to any changes in the protocol. For instance, despite BIP 119 remaining unchanged for almost five years, there was a period when CTV was deemed too radical for activation.
A Shift in Perspective
It’s worth noting that Rubin’s earlier campaign for CTV faced considerable resistance, particularly from influential Bitcoin figures like Adam Back and Jimmy Song. The criticisms eventually led to significant pushback within the community, prompting Rubin to step back from active involvement in Bitcoin development.
So, what has led to this change in sentiment? Recent advocacy for the OP_CAT opcode (BIP 347) has seemingly broadened the Overton Window of acceptable Bitcoin proposals, allowing CTV and CSFS to be viewed as more “conservative” alternatives. Interestingly, many supporters of OP_CAT also back BIPs 119 and 348, reflecting a general openness to various proposals within the community.
Looking Ahead
As we move forward, we can expect to see increased dialogue surrounding these proposals. Developers are slated to convene at several technical conferences, including OPNEXT in April, BTC++ in July, and TABConf in October. As consensus begins to take shape within the developer community, the next phase will involve miners, investors, and the broader community in the actual activation of the soft fork.
Despite the anticipation, there remains no formalized process for executing a soft fork on Bitcoin. This uncertainty leaves several questions unanswered: Will the soft fork solely include CTV and CSFS, or will OP_CAT also be part of the discussion? How will the activation of the soft fork be carried out? And will Bitcoin miners take notice and participate in the signaling process? One thing is clear: as these discussions unfold, familiarity with the array of acronyms will become increasingly important.
