x raid [ARCHIVE] on Nostr: 📅 Original date posted:2021-11-24 📝 Original message: We are talkin ...
📅 Original date posted:2021-11-24
📝 Original message:
We are talkin interoperability among impl not individual node operators
version management of chosen impl.
where Pierre of Acinq says
"So we eat our own dog food and will experience force closes before our
users do.."
hahaha made my day ...
a node operator do tests live in its continuous integration efforts would
be expected and should be able do so with a by impl assured latest stable
release version.
what is suggested for dialog is the different impl maintainers before sign
off a stable release do a extra test live on mainnet with liquidity in
channels towards the other impl versions and by doing so can catch
unforseen glitches that tests of impl in isolation can not catch.
what also suggested was a collection point where one could fetch loglines
from the instances partaking in the interoperability assurance test.
ex. impl (a) try open channel to impl (b) and fails --can then ask central
logline point for the loglines of ( a < -- > b ) at unix.ts(start) - range
- unix.ts(end).
this then would help assert a new release of a impl is interoperable and
can be recommende for install as considered be latest stable release
version.
LN a Network System Class "Finacial" need in preparation for onboarding 1B
by 2026 start to grow up *now*.
thanks
/xraid
On Wed, Nov 24, 2021 at 12:14 AM ZmnSCPxj <ZmnSCPxj at protonmail.com> wrote:
> Good morning x-raid,
>
> > so You propose Acinq / Blockstream / Lightning Labs do not have funds to
> run a box or 2 ?
>
> Not at all, I am proposing that these people, who have already done the
> effort to release working Lightning Network Node implementations free of
> charge to you, are not obligated to *also* devote more hardware and
> resources.
>
> Let me tell a little story...
>
> Some years ago, during the SegWit wars, there was a sentiment "when are
> **they** going to implement Lightning??"
> Both anti-SegWit and pro-SegWit asked this:
>
> * anti-SegWit: Yeah, you need bigblocks, Lightning is vaporware, when are
> **they** going to implement Lightning?
> * pro-SegWit: Lightning is so totes kool, this is why we SegWit, when are
> **they** going to implement Lightning?
>
> After some time participating in the SegWit wars, I realized that I was,
> in fact, a programmer (LOL).
> So why should **I** be asking when **they** are going to implement
> Lightning?
> As a programmer, **I** could implement Lightning myself!
> I should be asking myself why **I** was not implementing it.
>
> Thus I started contributing to the Lightning implementation written in a
> language I could understand, C-Lightning.
>
>
> My question to you is: obviously you are a node operator as otherwise the
> issue you raise would not be relevant to you, but what can *you* do to
> advance your goal?
>
> (In any case: C-Lightning and Eclair devs have already mentioned they
> already run mainnet nodes tracking our respective master branches (i.e. we
> already eat our own dog food, because duh --- for many of us, the reason we
> are developing this is because for *other* reasons, we *have to* run
> Lightning nodes), is there any particular implementation you are concerned
> about?
> Maybe ask them directly?)
>
>
> Regards,
> ZmnSCPxj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211124/0f74cf48/attachment.html>;
📝 Original message:
We are talkin interoperability among impl not individual node operators
version management of chosen impl.
where Pierre of Acinq says
"So we eat our own dog food and will experience force closes before our
users do.."
hahaha made my day ...
a node operator do tests live in its continuous integration efforts would
be expected and should be able do so with a by impl assured latest stable
release version.
what is suggested for dialog is the different impl maintainers before sign
off a stable release do a extra test live on mainnet with liquidity in
channels towards the other impl versions and by doing so can catch
unforseen glitches that tests of impl in isolation can not catch.
what also suggested was a collection point where one could fetch loglines
from the instances partaking in the interoperability assurance test.
ex. impl (a) try open channel to impl (b) and fails --can then ask central
logline point for the loglines of ( a < -- > b ) at unix.ts(start) - range
- unix.ts(end).
this then would help assert a new release of a impl is interoperable and
can be recommende for install as considered be latest stable release
version.
LN a Network System Class "Finacial" need in preparation for onboarding 1B
by 2026 start to grow up *now*.
thanks
/xraid
On Wed, Nov 24, 2021 at 12:14 AM ZmnSCPxj <ZmnSCPxj at protonmail.com> wrote:
> Good morning x-raid,
>
> > so You propose Acinq / Blockstream / Lightning Labs do not have funds to
> run a box or 2 ?
>
> Not at all, I am proposing that these people, who have already done the
> effort to release working Lightning Network Node implementations free of
> charge to you, are not obligated to *also* devote more hardware and
> resources.
>
> Let me tell a little story...
>
> Some years ago, during the SegWit wars, there was a sentiment "when are
> **they** going to implement Lightning??"
> Both anti-SegWit and pro-SegWit asked this:
>
> * anti-SegWit: Yeah, you need bigblocks, Lightning is vaporware, when are
> **they** going to implement Lightning?
> * pro-SegWit: Lightning is so totes kool, this is why we SegWit, when are
> **they** going to implement Lightning?
>
> After some time participating in the SegWit wars, I realized that I was,
> in fact, a programmer (LOL).
> So why should **I** be asking when **they** are going to implement
> Lightning?
> As a programmer, **I** could implement Lightning myself!
> I should be asking myself why **I** was not implementing it.
>
> Thus I started contributing to the Lightning implementation written in a
> language I could understand, C-Lightning.
>
>
> My question to you is: obviously you are a node operator as otherwise the
> issue you raise would not be relevant to you, but what can *you* do to
> advance your goal?
>
> (In any case: C-Lightning and Eclair devs have already mentioned they
> already run mainnet nodes tracking our respective master branches (i.e. we
> already eat our own dog food, because duh --- for many of us, the reason we
> are developing this is because for *other* reasons, we *have to* run
> Lightning nodes), is there any particular implementation you are concerned
> about?
> Maybe ask them directly?)
>
>
> Regards,
> ZmnSCPxj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211124/0f74cf48/attachment.html>;