BIP-110 Stalls with Minimal Miner Backing, Highlighting Bitcoin's Governance
Recent data shared by Michael Saylor, founder of MicroStrategy, indicates tepid community response to BIP-110, a proposal aimed at optimizing Bitcoin's data handling. According to his analysis, only approximately 2.6% of miners have signaled support for the initiative.
What BIP-110 Proposed
Designed as a temporary soft fork, BIP-110 sought to introduce seven new consensus limits over a roughly one-year period. Key restrictions included capping new script public key lengths, limiting certain data push and witness item sizes, and disabling specific Taproot extension paths.
The proposal's goal was to significantly reduce the amount of arbitrary, non-payment data—such as inscriptions or runes—that could be embedded in transactions. Proponents argued this would lower the operational burden on full nodes, curb potential spam, and refocus Bitcoin on its core monetary utility.
Low Adoption Signals a Dim Future
The lackluster miner support casts serious doubt on the proposal's viability. Saylor noted that, per the proposal's mechanism, nodes supporting BIP-110 would begin rejecting blocks mined by non-signaling miners after block height 961,632.
Given the absence of broad consensus, the most likely outcomes are either a complete stall of the activation process or the creation of an irrelevant minority fork that would have no material impact on the main Bitcoin network.
Bitcoin Continues Unaffected
Regardless of BIP-110's fate, the clear takeaway is that the main Bitcoin network will continue operating smoothly as designed. Saylor's comment that "Bitcoin is working as designed" underscores the network's inherent resilience and its ability to filter out changes lacking widespread community support.
This episode highlights the decentralized nature of Bitcoin's governance. Any significant protocol change, especially one modifying consensus rules, requires broad acceptance from miners, nodes, developers, and the wider user base. The low support for BIP-110 may reflect community caution about restricting non-payment data or disagreements over the specific implementation approach.