Bitcoin Developer Says It Is Too Late to Cancel BIP110 Despite Growing Debate
0
0

What to Know
- Luke Dashjr rejected calls to cancel BIP110, insisting the proposal will continue despite growing community debate over Bitcoin network policy.
- Supporters say BIP110 limits blockchain spam from Ordinals and Runes, reducing storage pressure while prioritizing financial transactions more effectively overall.
- Michael Saylor urged cautious protocol changes, stressing institutional capital and long-term stability remain Bitcoin’s strongest growth drivers ahead today.
Bitcoin developer Luke Dashjr has rejected calls to withdraw the controversial BIP110 proposal, signaling that work on the network upgrade will continue despite growing debate within the community. His comments came as discussions intensified over how Bitcoin should handle non-financial data stored on its blockchain and whether additional protocol changes remain necessary.
According to Dashjr, suggestions that the proposal should be abandoned do not reflect the current direction of development. He also dismissed claims that Strategy Executive Chairman Michael Saylor had opposed the proposal. Instead, Dashjr stated that Saylor had not commented on BIP110 and insisted there was no reason to cancel the planned upgrade.
BIP110 aims to introduce temporary consensus changes designed to limit blockchain spam linked to protocols such as Ordinals and Runes. Supporters argue that these applications fill Bitcoin blocks with non-financial data, increasing storage requirements and reducing network efficiency for standard transactions.
Dashjr, who maintains the Bitcoin Knots software, also suggested that BIP110 may not be the final step. He explained that another long-term soft fork could become necessary if Bitcoin Core developers fail to introduce their own solution within the coming year. However, he added that further changes might become unnecessary if Core addresses the issue in time.
Also Read: XRP Faces Critical Two-Week Close as EGRAG Flags Key Breakout Levels Ahead Today
Dashjr links BIP110 to broader Bitcoin network priorities
The proposal has become a focal point in Bitcoin’s ongoing debate over balancing innovation with preserving the network’s primary purpose. While some developers believe Ordinals and similar protocols represent legitimate blockchain usage, others argue they place unnecessary pressure on network resources. Dashjr belongs to the group advocating tighter controls on non-financial data. He maintains that Bitcoin should prioritize monetary transactions instead of expanding support for unrelated data storage.
Meanwhile, Saylor recently outlined his broader philosophy for Bitcoin’s future without directly addressing BIP110. He argued that Bitcoin should avoid frequent protocol changes and instead protect the qualities that have made the network resilient over time. Saylor stated that Bitcoin should not behave like a technology company racing to introduce new features. Instead, he said the network succeeds by remaining stable while maintaining a very high standard before accepting protocol changes.
He also emphasized that future Bitcoin growth will depend more on institutional capital than on technical modifications. According to Saylor, the halving continues to reduce supply, while capital inflows will increasingly determine Bitcoin’s long-term trajectory. At the same time, Saylor warned that excessive leverage could encourage the expansion of paper Bitcoin, creating additional risks for the broader market.
Conclusion
Dashjr’s refusal to reconsider BIP110 indicates that debate surrounding Bitcoin’s future development remains far from settled. Although opinions differ over the proposal, discussions continue to center on preserving network efficiency while maintaining Bitcoin’s long-standing design principles.
Also Read: Nigel Farage Accused of Failing to Disclose Crypto-Linked Support Before Election
The post Bitcoin Developer Says It Is Too Late to Cancel BIP110 Despite Growing Debate appeared first on 36Crypto.
0
0
Securely connect the portfolio you’re using to start.





