📅 Original date posted:2023-02-15
🗒️ Summary of this message: Running a high availability channel on the Lightning Network requires maintaining outbound liquidity by opening new channels, rebalancing, or swapping in. Publicly visible data may not be representative of the network as a whole.
📝 Original message:
>
> But how do you decide to set it without a credit relationship? Do I
> measure my channel and set the
>
bit because the channel is "usually" (at what threshold?) saturating in the
> inbound direction? What
> happens if this changes for an hour and I get unlucky? Did I just screw
> myself?
>
As a node setting the flag, you'll have to make sure you open new channels,
rebalance or swap-in in time to maintain outbound liquidity. That's part of
the game of running an HA channel.
> > How can you be sure about this? This isn't publicly visible data.
>
> Sure it is! https://river.com/learn/files/river-lightning-report.pdf
Some operators publish data, but are the experiences of one of the most
well connected (custodial) nodes representative for the network as a whole
when evaluating payment success rates? In the end you can't know what's
happening on the lightning network.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230215/1fb6f297/attachment.html>;
Joost Jager [ARCHIVE] /
npub1as…wfqmx
2023-06-09 13:12:41
in reply to nevent1q…5w2x
Author Public Key
npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmxPublished at
2023-06-09 13:12:41Event JSON
{
"id": "4526f750b8437eecdd84f2150d0ed747c228b1aa34ed2ce10b55e3e1da457651",
"pubkey": "ec3fb08b335b94aace30d13181f2ad0280df9bc34f1a99832c4e2da8fb125eb3",
"created_at": 1686316361,
"kind": 1,
"tags": [
[
"e",
"93b1d238fcaae143ea8ae5d6f9ddc582df195f32146237959ceb0a833db784e0",
"",
"root"
],
[
"e",
"39ba5862f10d98513c873b517f6465578298d349bc70d109579cf05531440f5b",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "📅 Original date posted:2023-02-15\n🗒️ Summary of this message: Running a high availability channel on the Lightning Network requires maintaining outbound liquidity by opening new channels, rebalancing, or swapping in. Publicly visible data may not be representative of the network as a whole.\n📝 Original message:\n\u003e\n\u003e But how do you decide to set it without a credit relationship? Do I\n\u003e measure my channel and set the\n\u003e\nbit because the channel is \"usually\" (at what threshold?) saturating in the\n\u003e inbound direction? What\n\u003e happens if this changes for an hour and I get unlucky? Did I just screw\n\u003e myself?\n\u003e\n\nAs a node setting the flag, you'll have to make sure you open new channels,\nrebalance or swap-in in time to maintain outbound liquidity. That's part of\nthe game of running an HA channel.\n\n\n\u003e \u003e How can you be sure about this? This isn't publicly visible data.\n\u003e\n\u003e Sure it is! https://river.com/learn/files/river-lightning-report.pdf\n\n\nSome operators publish data, but are the experiences of one of the most\nwell connected (custodial) nodes representative for the network as a whole\nwhen evaluating payment success rates? In the end you can't know what's\nhappening on the lightning network.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230215/1fb6f297/attachment.html\u003e",
"sig": "6681f24fe437ef227c3c93eefb78739b4ace930afd50dbc9350667bb72bcb8bfcd4ffd5c4b3d6d4b88bed97d094128ac013e0b07a50accf7b859fd9ea89bef20"
}