We just transitioned into epoch 227 and the d parameter is now set to 0.5. This means that this is the very first epoch where the community pools produce the same amount of blocks as the governed BFT nodes. It really feels great to see the network going forward and forward every single epoch.
I did also already calculate the schedule for this epoch:
Checking leadership log for Epoch 227 [ d Param: 0.5 ] 2020-11-02 23:24:15 ==> Stolen by BFT for 88764, Cumulative stolen blocks due to d param: 1 2020-11-03 00:15:55 ==> Stolen by BFT for 91864, Cumulative stolen blocks due to d param: 2 2020-11-04 00:44:33 ==> Stolen by BFT for 179982, Cumulative stolen blocks due to d param: 3 2020-11-04 08:34:58 ==> Leader for 208207, Cumulative epoch blocks: 1 2020-11-04 20:46:39 ==> Stolen by BFT for 252108, Cumulative stolen blocks due to d param: 4 2020-11-05 14:37:25 ==> Stolen by BFT for 316354, Cumulative stolen blocks due to d param: 5 2020-11-06 10:42:21 ==> Stolen by BFT for 388650, Cumulative stolen blocks due to d param: 6
Note: The times shown refer to the central european summer time (CET, UTC+1).
As you can see there is an unlucky epoch lying ahead. We expect to produce one block this epoch and 6! blocks will be stolen by the BFT nodes. Thats very unfortunate as with the d parameter at 0.5 only about half of the blocks of a whole epoch should get stolen by BFT. In our case 6 out of 7 blocks are stolen this relates to 85% stolen blocks instead of 50%. There is still a little chance that one of the BFT nodes misses a block and if that happens, be sure that the pool is ready to take over this work 😉
If you’re interested in whats going in the cardano space, make sure to check out the October Cardano monthly update. Great news and information in there and definetely worth listening/watching.
Lets hope for a better epoch 228! Thanks for stopping by. Talk to you soon 🙂