Jorge Timón [ARCHIVE] on Nostr: 📅 Original date posted:2023-05-02 📝 Original message: I'm not familiar with ...

📅 Original date posted:2023-05-02
📝 Original message:
I'm not familiar with libbitcoinkernel, but sounds similar to what I wanted
libconsensus to do (different from what matt corallo wanted). What would be
the differences?

Regarding node policy, I also wanted to make it polymorphic and let the
user chose RBF or the default of the time.
I can't remember the arguments against it.

Why do you call the default signet "bitcoin-inquisition" ?

I'm sorry if some of my inquires are offtopic for this mailing list, but I
no longer follow the main bitcoin mailing list for reasons that are
definitely offtopic to this mailing list (and apparently offtopic for
twitter and youtube too).

I'm all in favor of public communication, but I don't want to be kicked out
from this list.
So I'm happy to follow up this discussion privately too if it gets too
offtopic.

I know this is not the appropriate forum to publicly defend myself from
public attacks against me. Is there any forum appropriate for that?
I'm afraid not, nostr perhaps.

Anyway, sorry for the offtopic.
Keep up the good work, everyone.


On Sun, Apr 30, 2023 at 3:57 AM niftynei <niftynei at gmail.com> wrote:

> Hi Michael,
>
> CLN as implemented is currently nicely decoupled from the block source; as
> a project we assume that the node runner will choose a block backend that
> fits their self-sovereignty goals.
>
> This provides us with a nice separation of concerns. The block source is
> responsible for ensuring that only consensus valid data is delivered to the
> node, which in turn allows us to focus on processing and reacting to that
> data, as necessary.
>
> Bitcoin core as a project implements a broad swath of functionality
> (wallet, consensus, peering, rpc server, coin selection, key management,
> etc); breaking out the validation and peering functions into more
> composable parts would def open up more opportunities for building block
> sources for a wide variety of projects, not just CLN.
>
> There’s probably a real opportunity to “comingle” the peering of LN gossip
> + block data networks, this has been suggested a few times but never
> seriously pursued from the LN side. Having the peering functions of
> bitcoin-core broken out into a more composable/reusable piece may be a good
> first step here, and as a project would largely be on the bitcoin core
> side. Maybe this work is already in progress? I havent been keeping up with
> developments there.
>
> Thanks for the email, it’s definitely a good question.
>
> Lisa
>
>
> On Mon, Apr 24, 2023 at 02:09 Michael Folkson via Lightning-dev <
> lightning-dev at lists.linuxfoundation.org> wrote:
>
>> Any thoughts on this from the Core Lightning contributors? The way I see
>> it with upcoming proposed changes to default policy (primarily though not
>> exclusively for Lightning) and a soft fork activation attempt of APO/APOAS
>> (primarily though not exclusively for Lightning) that a tighter coupling
>> between the full node and the Lightning node could eventually make sense.
>> In a world where transaction fees were much higher you'd think almost every
>> full node would also want to be a Lightning node and so the separation of
>> concerns would make less sense. Having two separate P2P networks and two
>> separate P2P protocols also wouldn't make much sense in this scenario. You
>> could obviously still opt out of Lightning P2P messages if you weren't
>> interested in Lightning.
>>
>> The alternative would be just to focus on Knots style consensus
>> compatible forks of Core with limited additional functionality. But I think
>> we've reached the point of no return on Core dominance and not having
>> widely used "distros". As the ecosystem scales systems and processes should
>> be constantly evolving and improving and to me if anything Core's seem to
>> be going backwards.
>>
>> Thanks
>> Michael
>>
>> --
>> Michael Folkson
>> Email: michaelfolkson at protonmail.com
>> Keybase: michaelfolkson
>> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
>>
>> ------- Original Message -------
>>
>> On Saturday, January 14th, 2023 at 20:26, Michael Folkson <
>> michaelfolkson at protonmail.com> wrote:
>>
>> I tweeted this [0] back in November 2022.
>>
>> "With the btcd bugs and the analysis paralysis on a RBF policy option in
>> Core increasingly thinking @BitcoinKnots and consensus compatible forks of
>> Core are the future. Gonna chalk that one up to another thing @LukeDashjr
>> was right about all along."
>>
>> A new bare bones Knots style Bitcoin implementation (in C++/C) integrated
>> with Core Lightning was a long term idea I had (and presumably many others
>> have had) but the dysfunction on the Bitcoin Core project this week (if
>> anything it has been getting worse over time, not better) has made me start
>> to take the idea more seriously. It is clear to me that the current way the
>> Bitcoin Core project is being managed is not how I would like an open
>> source project to be managed. Very little discussion is public anymore and
>> decisions seem to be increasingly made behind closed doors or in private
>> IRC channels (to the extent that decisions are made at all). Core Lightning
>> seems to have the opposite problem. It is managed effectively in the open
>> (admittedly with fewer contributors) but doesn't have the eyeballs or the
>> usage that Bitcoin Core does. Regardless, selfishly I at some point would
>> like a bare bones Bitcoin and Lightning implementation integrated in one
>> codebase. The Bitcoin Core codebase has collected a lot of cruft over time
>> and the ultra conservatism that is needed when treating (potential)
>> consensus code seems to permeate into parts of the codebase that no one is
>> using, definitely isn't consensus code and should probably just be removed.
>>
>> The libbitcoinkernel project was (is?) an attempt to extract the
>> consensus engine out of Core but it seems like it won't achieve that as
>> consensus is just too slippery a concept and Knots style consensus
>> compatible codebase forks of Bitcoin Core seem to still the model. To what
>> extent you can safely chop off this cruft and effectively maintain this
>> less crufty fork of Bitcoin Core also isn't clear to me yet.
>>
>> Then there is the question of whether it makes sense to mix C and C++
>> code that people have different views on. C++ is obviously a superset of C
>> but assuming this merging of Bitcoin Core and Core Lightning is/was the
>> optimal final destination it surely would have been better if Core
>> Lightning was written in the same language (i.e. with classes) as Bitcoin
>> Core.
>>
>> I'm just floating the idea to (hopefully) hear from people who are much
>> more familiar with the entirety of the Bitcoin Core and Core Lightning
>> codebases. It would be an ambitious long term project but it would be nice
>> to focus on some ambitious project(s) (even if just conceptually) for a
>> while given (thankfully) there seems to be a lull in soft fork activation
>> chaos.
>>
>> Thanks
>> Michael
>>
>> [0]:
>> https://twitter.com/michaelfolkson/status/1589220155006910464?s=20&t=GbPm7w5BqS7rS3kiVFTNcw
>>
>> --
>> Michael Folkson
>> Email: michaelfolkson at protonmail.com
>> Keybase: michaelfolkson
>> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
>>
>>
>> _______________________________________________
>> Lightning-dev mailing list
>> Lightning-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>>
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230502/66c578d7/attachment-0001.html>;