diff --git a/contrib/devtools/chainparams/README.md b/contrib/devtools/chainparams/README.md
new file mode 100644
index 0000000000..eba13f6560
--- /dev/null
+++ b/contrib/devtools/chainparams/README.md
@@ -0,0 +1,32 @@
+# Chainparams Constants
+
+Utilities to generate chainparams constants that are compiled into the client
+(see [src/chainparamsconstants.h](/src/chainparamsconstants.h).
+
+The chainparams constants are fetched from bitcoind, dumped to intermediate
+files, and then compiled into [src/chainparamsconstants.h](/src/chainparamsconstants.h).
+If you're running bitcoind locally, the following instructions will work
+out-of-the-box:
+
+## Mainnet
+```
+bitcoind
+make_chainparams > chainparams_main.txt
+```
+
+## Testnet
+```
+bitcoind --testnet
+make_chainparams --testnet -a 127.0.0.1:18332 > chainparams_test.txt
+```
+
+## Build C++ Header File
+```
+generate_chainparams_constants.py . > ../../../src/chainparamsconstants.h
+```
+
+## Testing
+
+Updating these constants should be reviewed carefully, with a
+reindex-chainstate, checkpoints=0, and assumevalid=0 to catch any defect that
+causes rejection of blocks in the past history.
diff --git a/doc/release-process.md b/doc/release-process.md
index 1a3231957b..48e2a6306f 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -1,72 +1,66 @@
 Bitcoin ABC Release Process
 ===========================
 
 
 ## Before Release
 
 1. Check configuration
     - Check features planned for the release are implemented and documented
       (or more informally, that the Release Manager agrees it is feature complete)
     - Check that finished tasks / tickets are marked as resolved
 
 2. Verify tests passed
     - Any known issues or limitations should be documented in release notes
     - Known bugs should have tickets
     - Run `arc lint --everything` and check there is no linter error
     - Ensure that bitcoind and bitcoin-qt run with no issue on all supported platforms.
       Manually test bitcoin-qt by sending some transactions and navigating through the menus.
  
 3. Update the documents / code which needs to be updated every release
     - Check that doc/release-notes.md is complete, and fill in any missing items.
     - Update [bips.md](/doc/bips.md) to account for changes since the last release.
     - (major releases) Update [`BLOCK_CHAIN_SIZE`](/src/qt/intro.cpp) to the current size plus
       some overhead.
-    - Update `src/chainparams.cpp` defaultAssumeValid and nMinimumChainWork with information from
-      the getblockhash rpc.
-        - The selected value must not be orphaned so it may be useful to set the value two blocks back 
-          from the tip.
-        - Testnet should be set some tens of thousands back from the tip due to reorgs there.
-        - This update should be reviewed with a reindex-chainstate with assumevalid=0 to catch any defect
-          that causes rejection of blocks in the past history.
+    - Update `src/chainparamsconstants.h` per [contrib/devtools/chainparams/README.md](contrib/devtools/chainparams/README.md)
     - Regenerate manpages (run `contrib/devtools/gen-manpages.sh`, or for out-of-tree builds run
       `BUILDDIR=$PWD/build contrib/devtools/gen-manpages.sh`).
     - Update seeds as per [contrib/seeds/README.md](/contrib/seeds/README.md).
 
 4. Add git tag for release
 
 5. Increment version number for the next release in:
     - doc/release-notes.md (and copy existing one to versioned doc/release-notes/*.md)
     - configure.ac
     - CMakeLists.txt
     - contrib/gitian-descriptors/*.yml (before a new major release)
     - contrib/seeds/makeseeds.py (only after a new major release)
 
 ## Release
 
 6. Create Gitian Builds (see [gitian-building.md](/doc/gitian-building.md))
 
 7. Verify matching Gitian Builds, gather signatures
 
 8. Verify IBD bith with and without `-checkpoints=0 -assumevalid=0`
 
 9. Upload Gitian Builds to [bitcoinabc.org](https://download.bitcoinabc.org/)
 
 10. Create a [GitHub release](https://github.com/Bitcoin-ABC/bitcoin-abc/releases).
     The Github release name should be the same as the tag (without the prepended 'v'), and
     the contents of the release notes should be copied from release-notes.md.
 
 11. Notify maintainers of Ubuntu PPA, AUR, and Docker images to build their packages.
     They should be given 1-day advance notice if possible.
 
 ## After Release
 
 12. Update version number on www.bitcoinabc.org
 
 13. Publish signed checksums (various places, e.g. blog, reddit/r/BitcoinABC)
 
 14. Announce Release:
     - [Reddit](https://www.reddit.com/r/BitcoinABC/)
     - Twitter @Bitcoin_ABC
     - Public slack channels friendly to Bitcoin ABC announcements 
       (eg. #abc-announce on BTCforks,  #hardfork on BTCchat)