Sunny Sarah's Posts
Posted about 2 years ago
I thoroughly manage fees for all my channels (both manually and automatically). Nevertheless, if you feel like the fee from my side is unfairly high or you want to rebalance our channel and can't do it over my fee wall, feel free to drop me a note 🤝
Posted about 2 years ago
I'm back after a big hardware upgrade. Now fast as ⚡️ ! You can check new latency ( for example, " bos probe 03423790614f023e3c0cdaa654a3578e919947e4c3a14bf5044e7c787ebd11af1a " ). You will be surprised 😉
Disable TOR support ( don't affect any existing or new Channels! ), reduce latency
Posted about 2 years ago
From today I stop broadcasting external TOR address to the network and disable TOR support. All Nodes can still connect to me via clearnet IPv4 address, even if they use TOR themselves. I hope this step should improve stability of the Node and reduce latency. Ping to IPv4 address is fast enough from anywhere in the world. Please, feel free to inform me about any connectivity issues, I'll do my best to solve it!
Posted about 2 years ago
Finally! Now Sunny Sarah ☀️ Node has IPv4 clearnet-address! We are going to improve connectivity, reduce latency and increase quality of Node.
Posted about 2 years ago
I'm alive again! More refreshed, more ambitious and more powerful than ever before! I plan to systematically reopen all closed channels within the following few days and to be in touch via twitter/telegram (@SunnySarahNode). Let's keep working for bright and sunny future together! ☀️
Posted about 2 years ago
Node is still offline, but the issue is very serious and I'm doing everything in my power to resume service and be back online ASAP. I hope this will happen within next 24h, max 48h. I will reopen all closed channels (expired HTLCs and so on). I really appreciate each of you and hope to resume cooperation after the issue is resolved.
FYI: spontaneous force-closes of good channels
Posted over 2 years ago
Over the past few days network members have been observing spontaneous force-closes of good channels, that were not initiated by either side. As of now an issue supposedly related to this problem has been raised on github. Fees management might be the root couse for this behavior. It might affect nodes with automatic or manual but intensive fees changes.
Please keep this in mind and clarify whether a really good channel was indeed closed by the initiative of the other side.
Github issue : https://github.com/lightningnetwork/lnd/issues/6793
Please keep this in mind and clarify whether a really good channel was indeed closed by the initiative of the other side.
Github issue : https://github.com/lightningnetwork/lnd/issues/6793
August 02st planned maintenance 12:00-14:00 UTC
Posted over 2 years ago
There will be a planned maintenance on my node.
Sorry for the inconvenience and appreciate your patience.