During this epoch, our node experienced its first simultaneous block creation. We created the block but never got credit for it. In Shelley Explorer, I found that another stake pool created the exact block that we created, 13802.
We noticed that our node’s log file contains more “stuck_notifier” warnings. This increased frequency of warnings prompted our team to consult with other node operators in the Cardano Stake Pool & Best Practice Telegram channel.
We received more ADA stake delegates. More delegates subscribed to our pool’s email newsletter. More delegates visited our DApp360 Pool Community Telegram channel. Our node was constantly up without going down. We even got a Twitter mentioned as you
Epoch 11 started flawlessly without the DApp360’s node getting stuck or going off on a forked chain. To my disbelief, the node kept running without our assistance. We started epoch 11 ranked #3 in Daedalus Reward Wallet with a 100% performance.
However, we kept working, reading Jormungandr guide, and researching Telegram channels on ways we could improve our node configuration for resiliency and maximum uptime. At this point, I am getting about 3 hours of sleep each night.
Though we had more stakes and our node created its most blocks ever, I was a little demoralized. This demoralization resulted directly from the faulty (stuck nodes and forked chains) ITN causing our node to miss blocks.
Epoch 4 was not just transformational, but it exponentially boosted the DApp360 team morale. We were still getting sleepless nights but this time we had stakes and we were creating blocks. So who cares about sleep?