More checkpoint tribal knowledge

doc/release-process.md

@@ -68,6 +68,12 @@ Install deps on Linux:
    - PROTIP: Man page creation must be done after updating the version number and recompiling and before Debian package creation
  - Update checkpoints in src/chainparams.cpp via util/checkpoints.pl
    - hushd must be running to run this script, since it uses hush-cli to get the data
+   - Run `./util/checkpoints.pl &> checkpoints.txt` to generate the latets checkpoint data
+     - By default it will generate checkpoints for every 1000 blocks, the "stride"
+     - You can get a different "stride" by passing it in as the first arg to the script
+     - To get checkpoint data for every 5000 blocks: `./util/checkpoints.pl 5000 &> checkpoints.txt`
+     - Currently checkpoints from before block 340k are given for every 5k blocks to keep the data smaller
+   - Look for line which says "HUSH mainnet checkpoint data" near line 560 in chainparams.cpp , that is where checkpoint data begins.
    - checkpoints.pl will just generate the data you need, it must be manually copied into the correct place
    - Checkpoints are a list of block heights and block hashes that tell a full node the correct block history of the blockchain
    - Checkpoints make block verification a bit faster, because nodes can say "is this block a descendant of a checkpoint block?" instead of doing full consensus checks, which take more time

src/chainparams.cpp

@@ -559,7 +559,7 @@ void *chainparams_commandline() {
         pCurrentParams->consensus.vUpgrades[Consensus::UPGRADE_OVERWINTER].nActivationHeight = ASSETCHAINS_OVERWINTER;
 		// Generated at 1575831755 via hush3 util/checkpoints.pl by Duke Leto
         if (strcmp(SMART_CHAIN_SYMBOL,"HUSH3") == 0) {
-                // Generated at 1596199654 via hush3 util/checkpoints.pl by Duke Leto
+                // HUSH mainnet checkpoint data
                 checkpointData = //(Checkpoints::CCheckpointData)
                 {
                         boost::assign::map_list_of