Skip to content

Commit

Permalink
doc/release-process: Correct m_assumed_*_size to GB
Browse files Browse the repository at this point in the history
  • Loading branch information
luke-jr committed Sep 2, 2024
1 parent 4c62285 commit c452d6c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -310,13 +310,13 @@ 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`, take the size in GiB of these directories:
To calculate `m_assumed_blockchain_size`, take the size in GB of these directories:
- For `mainnet` -> the data directory, excluding the `/testnet3`, `/testnet4`, `/signet`, and `/regtest` directories and any overly large files, e.g. a huge `debug.log`
- For `testnet` -> `/testnet3`
- For `testnet4` -> `/testnet4`
- For `signet` -> `/signet`

To calculate `m_assumed_chain_state_size`, take the size in GiB of these directories:
To calculate `m_assumed_chain_state_size`, take the size in GB of these directories:
- For `mainnet` -> `/chainstate`
- For `testnet` -> `/testnet3/chainstate`
- For `testnet4` -> `/testnet4/chainstate`
Expand Down

0 comments on commit c452d6c

Please sign in to comment.