Planning for the future
Since our pool performed optimally for the last four epochs (10, 11, 12, and 13), our team decided to focus on observing and documenting the behavior of both the Incentivized Testnet (ITN) and the DApp360 node. We figured that observational learning would help our team plan an optimal operational strategy for the DApp360 node. We want our node to be resilient. Also, we needed to craft several plans, including disaster recovery, marketing, as well as reaching “Saturation Point.” Since the node was running fine, it was time to prepare for the future.
During this epoch (14), we also considered our communication strategy for our stake pool’s delegates. We want to provide our delegates with useful and transparent information that would enable them to make a better decision about our pool. At the same time, we want to avoid inundating them with unimportant information. So we started crafting a communication strategy for our stake pool’s delegates.
While doing all this, our team frequently monitored our node progress. We noticed that we had missed a block. But we figured that it was not a big deal since the node was not stuck. This epoch ended without any significant event.