yes i do have a solution that is easily integrated to the different impl
for pumping up live loglines, what's needed there for this very purpose
would be a html ws UI with side by side windows representing a impl
instance version, also a query for download files of range unix.ts per
instance.
Good morning x raid,
> 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
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
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
> so You propose Acinq / Blockstream / Lightning Labs do not have funds to
run a box or 2 ?
Fwiw we already do that with our main node. It's even better than a demo
one because it has real economic activity, and has a lot of channels to a
variety of nodes implementations and versions.
Sometimes
Each dev does tests on a local machine before push to repo, repo
maintainers do tests and when satisfied do an acceptance test in the
proposed system to verify against all other implementations partaking
before public release. Has not anything to do with You relly, not Your
private machine but
so You propose Acinq / Blockstream / Lightning Labs do not have funds to
run a box or 2 ?
contributions can be made towards each impl by ppl while the project still
do need put liquidity on mainnet to be a viable test before a public
sanctioned release.
I find You choose misread what the text is
Good morning x-raid,
> what i can imagine is each team should provide boxes and channel liquidity as
> stake on mainnet for tests before announce a public realise as to feel the
> pain first hand instead of having several K´s of plebs confused and at worst
> have funds in channelclosed etc.
ZmnSCPxj via Lightning-dev
writes:
> Are you proposing as well to provide the hardware and Internet
> connection for these boxes?
Having implemented and operated the lightning integration testing
framework [1,2] in the past this is something near and dear to my
heart. However I have since become
what i can imagine is each team should provide boxes and channel liquidity
as stake on mainnet for tests before announce a public realise as to feel
the pain first hand instead of having several K´s of plebs confused and at
worst have funds in channelclosed etc. but mostly for helping in smooth
Good morning again x-raid,
Are you proposing as well to provide the hardware and Internet connection for
these boxes?
I know of one person at least who runs a node that tracks the C-Lightning
master (I think they do a nightly build?), and I run a node that I update every
release of
Good morning x-raid,
> I propose a dialog of the below joint effort ...
>
> thanks
> /xraid
>
> ***
> A decentralised integration lab where CL Eclair LDK LND (++ ?) runs each the
> latest release on "one box" rBOX and master.rc on "another box" rcBOX.
I believe Electrum also has its own bespoke
I propose a dialog of the below joint effort ...
thanks
/xraid
***
A decentralised integration lab where CL Eclair LDK LND (++ ?) runs each
the latest release on "one box" rBOX and master.rc on "another box" rcBOX.
The rBOX of each impl has a channels to the other impl rBOXés
same setup goes
13 matches
Mail list logo
