Bitcoin Faces Potential Split With BIP110 Proposal
Bitcoin users are watching closely as the BIP110 proposal approaches its enforcement deadline, sparking debate over the network's future.

BTCcoinbeat.news
BTC/USD live chart
LIVEA debate is brewing over BIP110, a proposed update to the Bitcoin protocol designed to limit the size of OP_RETURN data on the blockchain. The proposal, backed by the Bitcoin Knots implementation, aims to reduce data usage. However, the plan lacks broad support, and the most widely used software, Bitcoin Core, has not adopted it. With only a small percentage of mining power signaling support, the community is looking at three potential outcomes when the enforcement starts around August 8.
In the most likely scenario, the lack of miner support leaves the network mostly unchanged. Miners who do not support BIP110 will continue building the main chain as usual. For those running BIP110 enforcing nodes, this would effectively stall their software, as they would reject standard blocks. These users would then face a tough choice, either revert to standard software or attempt a hard fork to create their own version of the currency.
Another scenario involves miners signaling support for the upgrade to keep the network unified. Even if all miners signal, this does not guarantee the new rules will be enforced by the rest of the network. If the economic majority of nodes does not validate these changes, we could still see a chain split, with different nodes accepting different blocks.
Finally, a sizable minority of miners could create a separate chain. This would lead to a split where two versions of the Bitcoin blockchain exist simultaneously. While blocks would confirm more slowly, it would technically allow BIP110 nodes to remain functional. Traders and users should keep an eye on mining signals as we approach block 961,632, as the market response to these technical shifts remains uncertain.
Prices update live from CoinMarketCap. Market data, not financial advice.
Market sentiment
Be the first to react
▍Comments (0)
No comments yet. Start the conversation!



