From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail•com>
To: "niftynei" <niftynei@gmail•com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>,
"Michael Folkson" <michaelfolkson@protonmail•com>
Cc: Lightning Dev <lightning-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] A new Bitcoin implementation integrated with Core Lightning
Date: Sun, 30 Apr 2023 17:22:01 +0200 [thread overview]
Message-ID: <CSA6YMDAU8FF.1FEV1VYNWWH3K@vincent-arch> (raw)
In-Reply-To: <CAM1a7P0qEkydNQQt38UUvyX3SorfgPNyfO79j72roG0_zo22+w@mail.gmail.com>
Hi Michael and Lisa,
> 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.
Let me just mention that [1] I have been working on a plugin
that allows experimentation with different types of Bitcoin Core
node alternatives (including core too), and it also supports BIP 157
with nakamoto [2].
In the upcoming months, I plan to allocate some time to work
directly on Nakamoto.
> 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.
A missing piece at the moment is a unified approach to fee calculation.
This logic is critical for Lightning nodes, so if we don't have a uniform
way of estimating fees, it could lead to several issues.
P.S: The fee estimation problem may have already been solved by Neutrino,
but I'm not aware of it.
[1] https://github.com/coffee-tools/folgore
[2] https://github.com/cloudhead/nakamoto
Cheers!
Vincent.
next prev parent reply other threads:[~2023-04-30 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 20:26 [bitcoin-dev] " Michael Folkson
2023-01-14 20:34 ` [bitcoin-dev] [Lightning-dev] " Fabian
2023-01-14 20:45 ` Michael Folkson
2023-01-15 13:04 ` [bitcoin-dev] " alicexbt
[not found] ` <KdDQGItU-BH7EotUQ9DoiUZRPM9TRnflf4P664Ue2ynCyj6ts1zFIoHxf4q-EsaM8b_GVrvXZZA9TtPX6BVY6CfSvXcme12lxLe_1RoAwZw=@protonmail.com>
2023-01-16 15:45 ` [bitcoin-dev] [Lightning-dev] " Michael Folkson
2023-04-18 17:06 ` [bitcoin-dev] " Michael Folkson
2023-04-19 9:05 ` Kostas Karasavvas
2023-04-19 10:54 ` Michael Folkson
2023-04-24 16:06 ` [bitcoin-dev] [Lightning-dev] " niftynei
2023-04-30 15:22 ` Vincenzo Palazzo [this message]
2023-05-06 5:58 ` Matt Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CSA6YMDAU8FF.1FEV1VYNWWH3K@vincent-arch \
--to=vincenzopalazzodev@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lightning-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@protonmail$(echo .)com \
--cc=niftynei@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox