Currently the checkpoints file is updated only when there is a new version of MBHD.
Thus as it gets older replays/ repairs get slower as we always do a replay from a checkpoint.
Checkpoints occur at difficulty changes, about every 2000 blocks / fortnight.
It would be possible for MBHD (and Classic) to update the checkpoints file themselves. If you have a look at BuildCheckpoints the code isn't terribly complicated.
This would mean that the performance of replays/ repairs for MBHD would not degrade over time when there were infrequent/ no MBHD releases (or Classic releases if the code were backported).
Currently the checkpoints file is updated only when there is a new version of MBHD. Thus as it gets older replays/ repairs get slower as we always do a replay from a checkpoint.
Checkpoints occur at difficulty changes, about every 2000 blocks / fortnight.
It would be possible for MBHD (and Classic) to update the checkpoints file themselves. If you have a look at BuildCheckpoints the code isn't terribly complicated.
This would mean that the performance of replays/ repairs for MBHD would not degrade over time when there were infrequent/ no MBHD releases (or Classic releases if the code were backported).