Each time there’s a new Epoch in order to determine my leader slots? If so, is a way to just append the newer ledger information instead of re-running it to get the entire thing every time which can take a while and use a lot of memory?
yes you need to rerun it. For the leaderlog caluclation you need a delegation snapshot from the previous epoch and the random values, which are generated during the first 2/3 of the current epoch.
It’s super easy when using docker containers. I run this at the beginning of each epoch, so I can be sure that the generated ledger state is actually that what is used by the current epoch.
But I am still sad because I am still not sure if the pool is even working. With 25% chance and around 500k ada in the pool we did not get any blocks …
But it looks like everything is running on gLiveView so I do not understand
Being scheduled to mint blocks does not depend on your system to be operational.
As you said, with a 500K pledge you have about a 25 or 30% chance of being scheduled for a block, but that percentage resets every epoch. So similar to rolling a four sided dice 12 times, you may, unfortunately, never get scheduled any of those times. Just keep checking and working to get more delegates to increase your % chance.
Hi all, I was trying to check leaderlogs this morning (NZ time, about 1 hr ago), but I keep getting the “you’re a bit early” error for epoch 259. When I tried testing back on epoch 258 I get an API error. I’m following the coincashew guide. The script was updated when I can the updater.