From 3a55c8851c746f57847218f47f179a5a4d10ab61 Mon Sep 17 00:00:00 2001 From: Adrian Gallagher Date: Mon, 14 Dec 2020 16:55:41 -0800 Subject: [PATCH] Litecoin: Branding --- doc/release-process.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/release-process.md b/doc/release-process.md index bc5c6d271f..7f06282e9b 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -290,7 +290,6 @@ Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spur - Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the litecoin.org server. -``` - Update litecoin.org version - Update other repositories and websites for new version @@ -351,13 +350,13 @@ Both variables are used as a guideline for how much space the user needs on thei Note that all values should be taken from a **fully synced** node and have an overhead of 5-10% added on top of its base value. To calculate `m_assumed_blockchain_size`: -- For `mainnet` -> Take the size of the data directory, excluding `/regtest` and `/testnet3` directories. -- For `testnet` -> Take the size of the `/testnet3` directory. +- For `mainnet` -> Take the size of the data directory, excluding `/regtest` and `/testnet4` directories. +- For `testnet` -> Take the size of the `/testnet4` directory. To calculate `m_assumed_chain_state_size`: - For `mainnet` -> Take the size of the `/chainstate` directory. -- For `testnet` -> Take the size of the `/testnet3/chainstate` directory. +- For `testnet` -> Take the size of the `/testnet4/chainstate` directory. Notes: - When taking the size for `m_assumed_blockchain_size`, there's no need to exclude the `/chainstate` directory since it's a guideline value and an overhead will be added anyway.