diff --git a/doc/release-process.md b/doc/release-process.md
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -12,6 +12,7 @@
 2. Verify tests passed
     - any known issues or limitations should be documented in release notes
     - known bugs should have tickets
+    - Verify IBD without checkpoints and without assumevalid.
  
 3. Update the documents / code which needs to be updated every release
     - Fill in doc/release-notes.md (copy existing one to versioned doc/release-notes/*.md document 
@@ -19,43 +20,43 @@
     - Update [bips.md](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  with information from the getblockhash rpc.
+    - 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.
     - Regenerate manpages (run contrib/devtools/gen-manpages.sh).
+    - Update seeds as per [contrib/seeds/README.md](contrib/seeds/README.md)
 
-4. Increment version number in:
-    - doc/Doxyfile
-    - doc/release-notes.md
-    - configure.ac
-    - src/config/CMakeLists.txt
-    - src/test/net_tests.cpp
-    - src/clientversion.h
-    - contrib/gitian-descriptors/*.yml (before a new major release)
-
-5. Add git tag for release
-
+4. Add git tag for release
 
 ## Release
 
-6. Create Gitian Builds (see doc/gitian-building.md), notify PPA buildmaster to start creating Ubuntu PPAs
+5. Create Gitian Builds (see doc/gitian-building.md), notify PPA buildmaster to start creating Ubuntu PPAs
 
-7. Verify matching gitian builds, gather signatures
+6. Verify matching gitian builds, gather signatures
 
-8. Upload gitian build to [bitcoinabc.org](https://download.bitcoinabc.org/)
+7. Upload gitian build to [bitcoinabc.org](https://download.bitcoinabc.org/)
 
-9. Re-verify the uploads (make sure that downloading them, their checksums are ok)
-
-10. Create a [GitHub release](https://github.com/Bitcoin-ABC/bitcoin-abc/releases).
+8. 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.
 
+9. Create a [GitHub release](https://github.com/Bitcoin-ABC/bitcoin-abc/releases) 
 
 ## After Release
 
+10. Increment version number in:
+    - doc/Doxyfile
+    - doc/release-notes.md
+    - configure.ac
+    - src/config/CMakeLists.txt
+    - src/test/net_tests.cpp
+    - src/clientversion.h
+    - contrib/gitian-descriptors/*.yml (before a new major release)
+
 11. Update version number on www.bitcoinabc.org
 
 12. Publish signed checksums (various places, e.g. blog, reddit/r/BitcoinABC)