The Bitcoin (BTC) developer community is immersed in a new debate over possible modifications to Bitcoin Core, the fundamental software that implements the network's consensus rules and allows anyone, from their node, to independently validate transactions and blocks.  

Bitcoin Optech Newsletter #344 features the views of several Bitcoin contributors and developers. This time, Antoine Poinsot, Anthony Towns, and David Harding, whose opinions revolve around one central question: how should Bitcoin Core evolve to ensure both network security and ease of use for participants? 

Poinsot's proposals on the structure of the project

Poinsot, in a series of posts, argues that “Bitcoin Core should be a robust backbone for the Bitcoin network, balancing software protection with the implementation of new features to strengthen the ecosystem.”  

Antoine Poinsot proposes to split the Bitcoin Core software into three parts. Source: mitbtcexpo .

Poinsot proposes dividing Bitcoin Core into three independent projects: a node (in charge of validating the blockchain), a wallet (to manage funds) and a graphical user interface (GUI, which facilitates interaction with the software).  

This idea is supported by the multiprocessing subproject, a multi-year effort that separates the program's functions into distinct processes. For Poinsot, this restructuring would make each component easier to maintain and update, offering flexibility and agility to development. 

The hypothesis is that the wallet and GUI could be developed separately, as long as they continue to interact reliably with the master node. 

Towns' vision and his questions

Anthony Towns is sceptical about this split, saying that “components would still be tightly coupled” and changes in one area would likely require changes in others. Far from simplifying development, this could add layers of complexity, making maintenance more cumbersome. 

For him, the real gain would lie in moving functions that do not directly depend on the node to external libraries or tools , such as certain network indexes that allow users to easily connect to their own node without adding complexity to the main project.  

That, Towns says, would allow developers to focus on specific areas without altering the core of the software. In fact, he notes that some users are already adopting creative solutions: connecting their wallets to proprietary nodes via middleware that uses blockchain indexes, creating a kind of custom explorer. 

David Harding is concerned about everyday users

David Harding, on the other hand, is concerned that removing the focus on user experience will make it harder for those without extensive technical resources to validate transactions. He argues that the ability of each person to operate a full node is essential to maintaining the protocol's rules. 

He explains that “even a 30-minute change” in consensus parameters could“ upset fundamental properties of Bitcoin, such as the limit of 21 million coins issued.” 

For Harding, individual users are more committed to the core features of Bitcoin than organizations that offer services with nodes operated on behalf of third parties. Therefore, he concludes that if the integrity of the network is valued, making it easier to run a personal node and validate transactions should be given the same priority as fixing critical security bugs. 

David Harding believes that removing the focus on user experience will make transaction validation more difficult. Source: dtrt.org

Implications and impact on the Bitcoin ecosystem

These concerns affect various groups in the Bitcoin ecosystem. Node operators would be affected by the potential fragmentation of the software, as they would have to adapt to new tools to manage their portfolios.  

Miners, while not seeing direct changes to their block confirmation tasks, could be affected by any changes to validation policies or the way consensus updates are implemented.

End users, especially those using Bitcoin Core wallets or tools that rely on this client, may experience usability improvements or, on the contrary, experience difficulties if development focuses on purely technical aspects. 

Poinsot’s proposals, Towns’ doubts, and Harding’s warnings reflect the complexity of evolving software that underpins a global network . Every tweak to Bitcoin Core must consider not only its technical impact, but also its consequences for the community that uses it.