Softfork before GTA VI?

Sep 24 - Sep 27, 2026

  • The discourse among the Bitcoin programming community reveals a notable shift in focus from earlier enthusiasm for implementing covenants in Bitcoin to current interests which have diverged towards topics like ordinals, inscriptions, and various policy debates leading up to a hardfork.

Despite this shift, there remains an undercurrent of interest in post-quantum softforks, although the practical threat posed by quantum computing is still uncertain. The sentiment suggests that many take the eventual implementation of covenants for granted with future planning already considering them; however, they are not yet realized in practice. This disconnect points to a broader issue within the community where new initiatives are anticipated but not yet solidified, reflecting a need for renewed focus and consensus, especially in the wake of recent hardforks.

Regarding the specific technical discussions, there's uncertainty about the deployment of Bitcoin Improvement Proposal 54 (BIP-54) whether it will be introduced alone or bundled with other features like rebindable opcodes. The slow pace at which softforks have been historically adopted raises concerns about the focus and prioritization within the community. The discussion around BIP-347, which pertains to operational codes, illustrates a change in attitudes over time, transitioning from impossible to potentially feasible. This reflects a broader pattern in the community’s approach to development: an oscillation between maintaining the status quo and pushing forward with new activations despite potential consequences.

There is also an acknowledgment of the limitations imposed by not activating certain features such as decentralized sidechains as outlined in BIP-300. Without these features, the community might resort to centralized alternatives, which could lead to undesirable outcomes like Miner Extractable Value issues. The adaptation and hacking of existing tools to circumvent these limitations demonstrate a pragmatic, albeit sometimes controversial, approach to system evolution. This is analogous to developments in other technical fields, such as C++ programming, where features originally unintended by language creators have been exploited through 'hackish' means to meet user demands, ultimately becoming part of the standard practice due to historical precedents.

Moreover, the readiness of some mining pools to produce BIP-54-compatible blocks indicates a pathway to smoother activation of this proposal, provided no significant disruptions occur. It emphasizes a strategy within the community where small, non-controversial changes supported by key stakeholders like mining pools can facilitate easier consensus and adoption, contrasting with more contentious or larger scale changes that risk rejection or prolonged debate. This strategy mirrors adaptive tactics seen across technological domains where incremental changes often precede more substantial shifts in practice and policy.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback