
#Bitcoin #LightningNetwork LND Node. Telegram (min response time): https://teapawt.net/t.co/hDUI4UcM9I
Joined July 2022
- Tweets102
- Following724
- Followers554
- Likes155
Sunny Sarah ☀️ #LightningNetwork Node is going to regain lost ground.
Everything works well, stable and ready to return Node to the list of the most reliable network peers.
Any help will be highly appreciated, especially incoming channels.
Remaining to be the source of the ☀️
5
20
417
I'm determined to remain a part of #LightningNetwork
Ok, something didn't go according to plan. All of my channels were FCed. Nothing related to the LND client or its version - other nodes have nothing to worry about.
Let's see what happens when the dust settles.
I'm in touch in Telegram : t.me/SunnySarahNode
5
9
448
1/6 Some interesting stats.
Right now I have channels with 366 peers in the Lightning Network. Out of this number :
• 116 have a Twitter(X) account
• 105 have a Telegram account
• 78 have a Nostr account
...and...
👇
5/6 ...
• Twitter (𝕏) : @SunnySarahNode
• Telegram (DM) : t.me/SunnySarahNode
• Telegram (announces channel) : t.me/SunnySarahNodeAnn…
• Nostr (pubkey) : npub1mggh5pryurepctujtlakafkj3n8x972e8dnshyv22fdycku3f8dsfd5d3r
• Nostr (in your browser) : ...
1
6
759
6/6 ...
• Nostr (in your browser) : coracle.social/people/npub1m……
Follow me and we'll be in touch : )
And encourage other noderunners to provide contact information, that's really important!
1
5
658
What do you think about inbound routing fees in the Lightning Network, which are introduced (PR 6703 on GitHub) for the next 0.18 version of the LND?
So, inbound fees will do...
26%More good than bad
17%More bad than good
57%I'm not sure
47 votes • Final resultsThe ongoing onchain storm has forced me to significantly increase fees on all channels of my node. Please don't worry, this is temporary. My fees policy will return to normal soon.
3
11
931
Just one FC. 250k+ sats for one sweeped expired HTLC. One of seven. There are no words.
I'm thinking.
If your node starts to accumulate pending HTLC's rapidly, channels get disabled and eventually the node stops working, try stopping or restarting the Circuitbreaker if you are using it. Everything will be fixed instantly.
Already a dozen cases, including in low-load environment.
1/2 Sorry guys, there is some instability of my Node these days. Intermittent network issues. Will be back to normal operation ASAP. All expiring HTLCs are under constant control, I do not expect any channels to be FCed. Thank you for your patience. ...
2/2 ... The fastest way to contact me for any questions is Telegram ( t.me/SunnySarahNode ) - feel free to message me if anything.
357
Binance is in the #LightningNetwork now 😉
03a1f3afd646d77bdaf545cceaf079bab6057eae52c6319b63b5803d0989d6a72f
1/2 No FCs tonight. Great morning! 😊
By the way, restarting the node a few blocks before the HTLC expiration helped prevent two FCs already. Two channels were saved in this way. There are many more cases where even this did not help, but...
Slightly changed fee policy. ...
1/3 It's MANDATORY to increase Time Lock Delta in channel policy for each of your channels. Min = 80, ok = 120 👇
teapawt.net/alexbosworth/status/16…
github.com/lightningnetwork/…
Nevertheless even with this, I still ...
Although LND doubled the CLTV delta as a default in 0.16.1, it did not increase the existing channel CLTVs. You can do that yourself by updating the routing policies. Additionally the max-cltv-expiry= value was not changed. You can double that as well to adapt to increasing CLTVs
2
6
1,068
2/3 ... Nevertheless even with this, I still have few more FCs, that happened when both nodes were ok and online, and my peer and I just sat together and looked at the expiring HTLC block-by-block, not being able to do anything.
1
4
395



