GordianLN/gordian.md

Lots happened in the meantime, and lots I didn't update in here: cool new features of my script, issues here and there, force closes (oh those damn, pesky, stinky force closes, I almost decided to quit), and I'll probably go on not updating this, but feel free to holler at me on Telegram for anything!

GordianWatch service has been launched! For now free and for my channel peers only, will notify you as soon as you are seen offline by my node, ask me for details.

Gordian is now hybrid!

Gordian was chosen by clboss as a channel peer for SethForPrivacy, overall a cool experience to realize that an algo examined my node over a period of time and finally decided to throw liquidity at it.

ZeroFeeRouting is another cool operator to look for! There was an issue with a script they were using that caused a force close of our channel, even without a pending HTLC, due to me being offline for about 12hrs straight due to a power issue. I planned to re-open to them no matter what, but this makes me all the happier to do so!

Gordian surpassed the 30 channels mark, and the 2.1M capacity streak was broken by an incoming 3M channel from South Korea (very cool operator, thank you!) I decided to enable max_htlc for all my channels, and increase CLTV delta to reduce risk of force closures (I'll take the slightly lower chance of being selected for routes, safety above all), plus I reduced the updatechanpolicy frequency from every 3hrs to every 6.

Second friday report in the green, costs are at 96% of total income after a net month of activity, I am still looking into extending my reach into the network to be selected in more paths.

It's like LN was a malicious lover, welcoming me by giving a lot of sudden affection (in the form of profitability in a record timeframe), only to throw me down with disdain (as I'm hardly routing anything now, while activity was way more in the past week, even at higher fees than now). My script works without sentiment, as it only knows how to scan for flow, and won't take it personally; please have patience, Gordian's peers. On a side note, there's that one peer whose node really likes to disable our channel, let's hope we find a way to solve that.

Gordian is profitable! The accounting shows 10sats of net profit over the life of the node, which has been quite a short life, as first channel dates back to 21st march, all fees were frozen at 2500ppm for the first 6 days until I got to 11 peers and started the fee autotuning script, 12 days offline starting 4th april because of filesystem failure, this means the node became profitable in less than 20 days, is it a record or what?

I need to mark the date: I just received an unsolicited inbound channel, of the just right capacity, 2.1M, by GirthMaul, this is my very first spontaneus inbound channel and I am really happy!

G-Spot, albeit arguably expensive, is ran by a very dependable operator.

First month after launch, minus 12 days of downtime, minus first 6 days of very high default fees while waiting to get critical edge mass, it has now been 12 days of "proper routing", and I am at 156% costs vs earned fees, break even here I come!

I lost a very good peer today! Goes to show that even if you are an excellent system operator, rm -rf is a great leveler waiting for you just around the corner; I wish them to get back up ASAP.

Gordian is back up and running! just one casualty for a force close after a few days of being offline; luckily the postgresql dump I had was fine, ended up using the main instance dump even if the replica looked "newer" (also enabled synchronous replication this time): lightningnetwork/lnd#6395

Blockchain is fully synced, ETA for LN node reboot is 15th or 16th.

Blockchain sync at 70% roughly, system has been hardened even more than before, with solid zswap setting, new leaner power SSD's (Kingston A400's, slower for desktop usage, perfect for node operations), more stable (I hope) and definitely better looking SATA adapters, and new USB3 hub incoming.

Gordian is offline. Some mean errors with Raid1 setup, not exactly troubleshooted yet (most probably a silly power delivery issue to the disks, that started a chain reaction of R/W errors which didn't stop even after fixing power lines), led to system instability and freezes. New USB3 powered HUB and new USB-SATA adapters are incoming, and tests will be done right after; worst case scenario, I'll also need to swap out SSD's, but this will be clear after new components start arriving. I beg my pardon to all my current peers, please do not close channels to me, as my postgresql database is working and tested, last time I had to cold reboot the system I made sure I could connect correctly to the network, I stopped accepting forwards with BOS, and then shut down LND gracefully. I also have the postgres replica sitting in another ext4 disk that's not been touched by the failures, and I have tested and verified working a procedure to dump the postegresl and import it in another LND instance successfully on playground signet.

Reached 12 edges to 11 peers, enough to be palatable as a routing node, so my scripts have been unleashed and fee tuner + rebalancer are now running

Opened my very first reciprocal channels with a peer, too bad it couldn't be a dualfunded channel, as being without inbound I couldn't receive the initiating keysend