The Wait Continues
In epoch 1, DApp360 node waited to create a block but it did not happen. epoch 2 arrived without much fanfare for the DApp360 stake pool team. Our stake pool had the same 200K ADA pledge because we did not receive any stake delegation in epoch 1. So our expectation for creating a block was low, and the waiting game continued. In epoch 2, the Incentivized Testnet (ITN) constantly continued producing “stuck_notifier “ warnings. These warnings meant that the ITN instability was frequently getting our node stuck. Consequently, the node could not sync blocks with the ITN.
We did everything in our power to keep the buggy 8.2 node up. Restarting and bootstrapping the node became a half-an-hour routine even though the whole process took no more than 5 to 10 minutes. I got about 4 hours of sleep in epoch 2. Again, DApp360 node did not create a block in epoch 2.
We had a tiny email list (3 emails of which 2 were mine) of stake pool subscribers who had signed up via the DApp360 Stake Pool subscriber page. Hoping to get some stake delegations, I emailed our subscribers. This email was DApp360 pool first email ever sent. With the email sent, the waiting game continued.