From b4d2d74767ed0441dbc3a789cad2334eaac54290 Mon Sep 17 00:00:00 2001 From: Jon Atack Date: Wed, 23 Feb 2022 00:11:52 +0100 Subject: Release process: specify blockchain/chain_state units, reduce repetition --- doc/release-process.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'doc') diff --git a/doc/release-process.md b/doc/release-process.md index bad0e8cd72..b0f7ab02db 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -300,15 +300,15 @@ cat "$VERSION"/*/all.SHA256SUMS.asc > SHA256SUMS.asc Both variables are used as a guideline for how much space the user needs on their drive in total, not just strictly for the blockchain. 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 the `/testnet3`, `/signet`, and `/regtest` directories. -- For `testnet` -> Take the size of the `/testnet3` directory. -- For `signet` -> Take the size of the `/signet` 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 `signet` -> Take the size of the `/signet/chainstate` directory. +To calculate `m_assumed_blockchain_size`, take the size in GiB of these directories: +- For `mainnet` -> the data directory, excluding the `/testnet3`, `/signet`, and `/regtest` directories +- For `testnet` -> `/testnet3` +- For `signet` -> `/signet` + +To calculate `m_assumed_chain_state_size`, take the size in GiB of these directories: +- For `mainnet` -> `/chainstate` +- For `testnet` -> `/testnet3/chainstate` +- For `signet` -> `/signet/chainstate` 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. -- cgit v1.2.3