@AntoineP wrote three interesting blog posts on Bitcoin Core:
- Antoine Poinsot - Bitcoin Core project direction
- “I think we are in this situation where everybody is working on their own thing and there is no broad agreement about what the scope of the project should even be. As a consequence, year after year we keep piling up more code, more features, more RPCs, etc… with at best a constant amount of competent reviewers’ time. This is not tenable, as a focus which gets further dispersed will inevitably lead to reduced overall software quality.”
- Antoine Poinsot - Stating the obvious
- “When you consider that Bitcoin Core’s userbase is indirectly all Bitcoin users, how to prioritise development becomes quite clear. Bitcoin Core should be a robust backbone for the Bitcoin network, balancing between securing the Bitcoin Core software and implementing new features to strengthen and improve the Bitcoin network.”
- Antoine Poinsot - Bitcoin Core scope, concretely
- “The multiprocess project presents an opportunity in this regard. Separate
bitcoin-node,bitcoin-walletandbitcoin-guibinaries communicating through well-defined interfaces open the door to splitting the current project into 3. The contributors at github.com/bitcoin/bitcoin would focus on the Bitcoin Core node and release abitcoin-nodeprogram, exposing JSONRPC and IPC interfaces. The contributors at github.com/bitcoin-core/wallet would work on thebitcoin-walletprocess. The Bitcoin Core wallet releases would contain both the wallet and node processes, presumably with a wrapper to make it transparent to users. This project would release the equivalent of today’sbitcoind. Finally, the contributors at github.com/bitcoin-core/gui would develop and release thebitcoin-guiprogram, which would ship with the node and wallet.”
- “The multiprocess project presents an opportunity in this regard. Separate