The future of the Bitcoin Core GUI

The discussion revolves around the support for existing Bitcoin Core wallet users, emphasizing the historical importance of the wallet and GUI components to Bitcoin's success. However, with the evolution of Bitcoin and the emergence of superior alternatives, the focus has shifted towards maintaining the node, which is deemed critical given the vast amount of people and value depending on it. The idea is to mark the wallet and GUI as deprecated to manage user expectations, acknowledging that there are no current replacements for managing a Bitcoin Core wallet. This suggests a gradual phase-out rather than an immediate removal, recognizing the challenges in transitioning without suitable alternatives.

An alternative plan is proposed to address concerns regarding users potentially being stuck on version 34, unable to receive security updates for their full nodes or wallets. The plan includes abandoning the update to QML, releasing the existing GUI as a separate process communicating through IPC, and splitting off the GUI into its own project with a separate release schedule. Despite the recognition of this requiring significant effort, it's viewed as preferable to discontinuing the GUI entirely when no alternative exists. This approach also opens the door to competition among alternative GUIs, assuming there's interest in development.

Addressing software quality and the decision-making process in a leaderless structure, the proposal suggests setting clear quality thresholds for released software and communicating openly about any shortcomings. This could include warnings on download pages if software does not meet certain standards, balancing the need to inform users with the reality of development challenges. Concerns are raised about the slow development pace and unresolved issues within the GUI, indicating potential risks but not to the extent of deeming the software irresponsible to ship. The indirect costs and risks associated with maintaining the GUI, such as code churn and potential impacts on the broader Bitcoin user base, are highlighted as significant considerations. These include updates made for GUI purposes that may hinder node development or require compromises that affect other aspects of the project.

In summary, while there is acknowledgment of the need to eventually move away from supporting the Bitcoin Core wallet and GUI due to evolving priorities and better alternatives, there is also recognition of the importance of ensuring a smooth transition for users. The proposed path forward involves strategic deprecation, clear communication about software quality, and reorganization of development efforts to minimize impact on the main project goals. This strategy aims to balance the needs of the current user base with the long-term vision for Bitcoin Core’s development.