9]
After 40 minutes right now I'm at block 45270. It's sure taking its time.
Downloading the blockchain and syncing the old way took less time.
Looks like I'll have to leave it unattended before it finishes because it will take another 2 hours if it goes like this. I hope it doesn't make a mess again with fake stakes
Thanks Bspus.
IMHO This is the correct\canonical way to load a blockchain,
in this way each block is read, fully controlled and therefore indexed,
just as if it was downloaded from the network, but without having
to be online.
Do not worry, take all the time you need.
As you may have noticed the progression is more than linear.
You're right when you say that to a higher frequency of stakes,
often it is also accompanied by a higher probability of producing
chains of orphans blocks, is something that we have experienced all
many months ago.
Perhaps, in the future the DevTeam could imagine a kind of
simple "pacemakers", which avoids the production of too many
consecutive blocks by a wallet (too heavy).
For example it may be sufficient to impose a pause of 40 seconds
of sleep to the miner, after it as produced a new block.
This is a simple thing that they can do with a couple of lines.
I think that would not result in losses to the miner, but on the
contrary it would give everyone a chance to produce blocks.
Moreover giving the possibility of alternating the blocks created
by different wallet, it could increase security and possibly lessen
the orphans.
What happens now is that a few hours ago, after the stall of the
blockchain the PosDif collapsed at very low levels, but fortunately
now is recovering, as you can see here, in the chart below:
https://chainz.cryptoid.info/nav/#!extraction
I imagine that when you've finished bootstrapping, POSDif will be returned
normal, but in the meantime it will not surprise me if there will be a few
more small number of orphans, and a bit of Yoyo effect in the staking times
and PosDif.
