Since the commit 18f0689695 (currently on duke branch) a node will sync faster for blocks that are lower than a checkpoint, so if we want dragonx nodes to get this speedup, we will want at least one checkpoint for dragonx
Since the commit 18f06896953d96390d925060d6756a50ab3cd94b (currently on duke branch) a node will sync faster for blocks that are lower than a checkpoint, so if we want dragonx nodes to get this speedup, we will want at least one checkpoint for dragonx
As of b8ae39ccc7 in the duke branch there is now a place in the code to put DRAGONX checkpoints generated by checkpoints.pl
As of b8ae39ccc7c0fda99cd22c68626ba0f327525a62 in the duke branch there is now a place in the code to put DRAGONX checkpoints generated by checkpoints.pl
Probably a good idea to have some DRAGONX checkpoints
This wasn't done in the 3.9.3 release, maybe for the next release.
Since the commit
18f0689695(currently on duke branch) a node will sync faster for blocks that are lower than a checkpoint, so if we want dragonx nodes to get this speedup, we will want at least one checkpoint for dragonxAs of
b8ae39ccc7in the duke branch there is now a place in the code to put DRAGONX checkpoints generated by checkpoints.plAs of
97c7e814cfon duke branch, we now have checkpoints for DRAGONX