📅 Original date posted:2021-11-23
📝 Original message:
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
transitioning into future envisioned mass.
If teams rather outsource the running of boxes with channels on mainnet for
impl release and rc versions they would of course be able to, but close to
home for managing analysis of the team impl themselves is what I would
recommend.
Can also see that each box loglines are collected at one central point
whereby requests can be made for comparing interoperability per unix.ts
identified by box.
(thats alot of data You say --not really in Big Data terms, question is
where to set a proper cap in time for collections ? a week ? a month ?)
I think i might have a solution for the central point collector that could
be run by an outside of impl teams perimeter. (sponsored?)
/xraid
On Tue, Nov 23, 2021 at 11:35 AM ZmnSCPxj <ZmnSCPxj at protonmail.com> wrote:
> 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 C-Lightning (and runs CLBOSS as well).
> I do not know the actual implementations of what they connect to, but LND
> is very popular on the network and LNBIG is known to be an LND shop, and
> LNBIG is so pervasive that nearly every long-lived forwarding node has at
> least one channel with *some* LNBIG node.
> I consider this "good enough" in practice to catch interop bugs, but some
> interop bugs are deeper than just direct node-to-node communications.
> For example, we had bugs in our interop with LND `keysend` before, by my
> memory.
>
> Regards,
> ZmnSCPxj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211123/2a4afb38/attachment-0001.html>;
x raid [ARCHIVE] /
npub157…fpqkx
2023-06-09 15:04:27
in reply to nevent1q…s4l7
Author Public Key
npub15758wuggl6u8umupz8ellvdjad7mjcchkn2vcelrmmeg55f48euspfpqkxPublished at
2023-06-09 15:04:27Event JSON
{
"id": "be8d7b46e8948245302a5c0df24314edff86a49ef53cfa8e6559ef4ef8392fd1",
"pubkey": "a7a8777108feb87e6f8111f3ffb1b2eb7db96317b4d4cc67e3def28a51353e79",
"created_at": 1686315867,
"kind": 1,
"tags": [
[
"e",
"d55fb1e5571803458104e1618e1a1ffb3fd14d11e56c39cebadd489957473ffa",
"",
"root"
],
[
"e",
"b3c4e765af5efcce60014197e5d8a9f0f08e3388c756c1cc824daee9fe3b68a6",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 Original date posted:2021-11-23\n📝 Original message:\nwhat i can imagine is each team should provide boxes and channel liquidity\nas stake on mainnet for tests before announce a public realise as to feel\nthe pain first hand instead of having several K´s of plebs confused and at\nworst have funds in channelclosed etc. but mostly for helping in smooth\ntransitioning into future envisioned mass.\n\nIf teams rather outsource the running of boxes with channels on mainnet for\nimpl release and rc versions they would of course be able to, but close to\nhome for managing analysis of the team impl themselves is what I would\nrecommend.\n\nCan also see that each box loglines are collected at one central point\nwhereby requests can be made for comparing interoperability per unix.ts\nidentified by box.\n(thats alot of data You say --not really in Big Data terms, question is\nwhere to set a proper cap in time for collections ? a week ? a month ?)\nI think i might have a solution for the central point collector that could\nbe run by an outside of impl teams perimeter. (sponsored?)\n\n/xraid\n\n\n\nOn Tue, Nov 23, 2021 at 11:35 AM ZmnSCPxj \u003cZmnSCPxj at protonmail.com\u003e wrote:\n\n\u003e Good morning again x-raid,\n\u003e\n\u003e Are you proposing as well to provide the hardware and Internet connection\n\u003e for these boxes?\n\u003e\n\u003e I know of one person at least who runs a node that tracks the C-Lightning\n\u003e master (I think they do a nightly build?), and I run a node that I update\n\u003e every release of C-Lightning (and runs CLBOSS as well).\n\u003e I do not know the actual implementations of what they connect to, but LND\n\u003e is very popular on the network and LNBIG is known to be an LND shop, and\n\u003e LNBIG is so pervasive that nearly every long-lived forwarding node has at\n\u003e least one channel with *some* LNBIG node.\n\u003e I consider this \"good enough\" in practice to catch interop bugs, but some\n\u003e interop bugs are deeper than just direct node-to-node communications.\n\u003e For example, we had bugs in our interop with LND `keysend` before, by my\n\u003e memory.\n\u003e\n\u003e Regards,\n\u003e ZmnSCPxj\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211123/2a4afb38/attachment-0001.html\u003e",
"sig": "4f7589b96662cf6c1b5b25201e71d148ae1a7600af2cdf02453767295ccca9057266abfa27aefed81984ac6188bc022a9925a1e60e16c93684b03bf36acdb14d"
}