{"id":3650,"date":"2026-11-10T07:06:27","date_gmt":"2026-11-10T07:06:27","guid":{"rendered":"https:\/\/smartcryptosecurity.com\/?p=3650"},"modified":"2026-11-10T07:06:27","modified_gmt":"2026-11-10T07:06:27","slug":"bitcoin-improvement-proposal-110-enters-mandatory-signaling-phase-amid-low-miner-support-and-high-stakes","status":"publish","type":"post","link":"https:\/\/smartcryptosecurity.com\/?p=3650","title":{"rendered":"Bitcoin Improvement Proposal 110 Enters Mandatory-Signaling Phase Amid Low Miner Support and High Stakes"},"content":{"rendered":"<p>Bitcoin Improvement Proposal 110 (BIP-110) has officially entered its mandatory-signaling phase at block 961,632, marking a high-stakes moment for the world&#8217;s leading cryptocurrency network. According to data from the BIP-110 monitor, participating miners signaled support in just 51 of the preceding 2,016 blocks, translating to a meager 2.53% signaling rate. This figure falls dramatically short of the 55% threshold required for an early activation of the protocol changes, setting the stage for a tense period of potential network division and ideological conflict over the future of Bitcoin\u2019s block space.<\/p>\n<p>The arrival of block 961,632 triggered automated changes among nodes configured to enforce the BIP-110 standard. These enforcing nodes immediately began rejecting any incoming blocks that failed to set version bit 4, a designated signaling mechanism for the proposal. Simultaneously, ordinary Bitcoin nodes operating under standard consensus rules continued to accept both signaling and non-signaling blocks, preventing an immediate, catastrophic network-wide split while allowing a minority BIP-110 branch to materialize. This minority branch quickly fell behind the dominant, majority-supported chain in terms of cumulative proof-of-work.<\/p>\n<p>Industry analysts note that the exceptionally low signaling rate makes a sustained, competitive rival chain highly unlikely without a substantial and sudden influx of miner participation. Without adequate mining hash rate securing its transactions, a distinct BIP-110 branch faces the grim prospect of advancing at a glacial pace or halting block production altogether, highlighting the immense coordination challenges faced by minority protocol upgrades on a decentralized proof-of-work network.<\/p>\n<p>This milestone serves as a rigorous real-world test of whether a dedicated faction of supporters can successfully advance a contentious consensus change without broad backing from the mining community. By pushing forward regardless, the move risks driving a permanent wedge between enforcing nodes and the dominant chain, escalating an ongoing, bitter dispute over how Bitcoin\u2019s limited block space should be utilized and who gets to decide the network&#8217;s operational boundaries.<\/p>\n<h2>BIP-110 Seeks Temporary Limits on Bitcoin Data<\/h2>\n<p>Authored by the pseudonymous developer Dathon Ohm, BIP-110 proposes a series of strict consensus-level restrictions designed to last for approximately one year following activation. The core objective of the proposal is to reshape how data is handled and stored on the blockchain by imposing severe limitations on various types of transaction outputs and script structures.<\/p>\n<p>Under the specific parameters outlined in the proposal, most new output scripts would be restricted to a maximum size of 34 bytes. Furthermore, OP_RETURN data-carrying outputs would be capped at 83 bytes, while certain data push operations and witness elements would face a strict limit of 256 bytes. The proposal also calls for temporary restrictions on several features introduced via the Taproot upgrade. Importantly, unspent transaction outputs (UTXOs) that were created prior to the activation of BIP-110 would be exempt from these newly minted rules.<\/p>\n<p>Proponents of the measure argue that these sweeping restrictions are necessary to discourage inscriptions, ordinals, and various other forms of non-monetary data that have increasingly populated the blockchain. According to supporters, these data-heavy transactions drive up storage, processing, and bandwidth costs for independent node operators, threatening the long-term decentralization of the network by making it increasingly expensive to run a full node.<\/p>\n<p>However, the proposal has encountered fierce opposition from prominent figures across the cryptocurrency ecosystem. High-profile critics, including Strategy executive chairman Michael Saylor and Blockstream CEO Adam Back, have publicly rebuffed the BIP-110 initiative. These industry leaders and developers have argued that implementing such a contentious change could deeply fracture the Bitcoin community, causing enforcing nodes to improperly reject valid transactions that are fully permitted under the network\u2019s existing, established consensus rules.<\/p>\n<p>The technical implementation of the proposal relies on version bit 4 for miner signaling. The deployment schedule laid out by its creators establishes blocks 961,632 through 963,647 as a mandatory-signaling window. During this specific window, nodes enforcing BIP-110 are programmed to strictly reject any blocks that do not carry the designated signal. Looking further down the timeline, the specification formally defines block 963,648 as the beginning of its locked-in state, with block 965,664 designated as the exact point when the strict transaction restrictions finally take effect across the enforcing network.<\/p>\n<p>Beyond the immediate scope of the proposal, proponents of BIP-110 have also discussed more drastic fallback mechanisms in the event of widespread miner resistance. On August 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work change originally authored by Luke Dashjr, the maintainer of Bitcoin Knots. Guida described the code at the time as a contingency measure designed for a scenario where miners overwhelmingly opposed BIP-110, though he emphasized that no specific activation date had been established for the alternative proof-of-work framework.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bitcoin Improvement Proposal 110 (BIP-110) has officially entered its mandatory-signaling phase at block 961,632, marking&#8230;<\/p>\n","protected":false},"author":3,"featured_media":3649,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58],"tags":[560,25,1253,83,2167,1944,2169,60,59,1254,571,2168,1075,2131,61,21],"class_list":["post-3650","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-network-security-nodes","tag-amid","tag-bitcoin","tag-enters","tag-high","tag-improvement","tag-mandatory","tag-miner","tag-network","tag-nodes","tag-phase","tag-proposal","tag-signaling","tag-stakes","tag-support","tag-uptime","tag-validation"],"_links":{"self":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3650","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3650"}],"version-history":[{"count":0,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3650\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/media\/3649"}],"wp:attachment":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3650"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3650"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3650"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}