Author: Jorge Timón 2023-05-02 13:34:58
Published on: 2023-05-02T13:34:58+00:00
The email correspondence includes several topics related to Bitcoin and Lightning nodes. The first email asks about the differences between libbitcoinkernel and libconsensus, as the former seems to be what the sender wanted the latter to do. The sender also mentions wanting to make node policy polymorphic and allowing users to choose RBF or the default of the time. They apologize if their inquiries are off-topic but express their desire for public communication without being kicked out of the mailing list.The second email discusses the separation of concerns between the block source and the node runner in CLN (C-lightning network). The sender suggests that breaking out validation and peering functions into more composable parts could open up opportunities for building block sources for a variety of projects. They propose combining the peering of LN gossip and block data networks, although it has not been seriously pursued from the LN side yet. The sender wonders if such work is already in progress.The third email is a tweet by Michael Folkson from November 2022, discussing btcd bugs and analysis paralysis on an RBF policy option in Core. Folkson suggests that consensus-compatible forks of Core, such as Bitcoin Knots, may be the future. He also mentions wanting a bare bones Bitcoin and Lightning implementation integrated into one codebase and believes that the current way the Bitcoin Core project is being managed is not how he would like an open-source project to be managed. In contrast, Core Lightning seems to be managed effectively in the open, but it doesn't have the usage that Bitcoin Core does. Overall, the emails touch upon different aspects of Bitcoin and Lightning nodes, including their functionalities, policies, and management. They suggest potential areas for improvement and innovation within the Bitcoin ecosystem.
Updated on: 2023-06-03T11:33:28.878314+00:00