diff options
| author | marcoagner <marco@agner.io> | 2018-10-07 13:11:36 +0100 |
|---|---|---|
| committer | marcoagner <marco@agner.io> | 2018-10-07 13:11:36 +0100 |
| commit | 9d0e52834bbd38e7c7410bcb09ef85d157968b04 (patch) | |
| tree | d21d966862cd2f0e7fd3f2c8da1b8ee6af7e1459 /doc | |
| parent | f504a1402afd0760e9d348ecc8bad0094aa7d705 (diff) | |
implements different disk sizes for different networks on intro
- Creates m_assumed_blockchain_size and m_assumed_chain_state_size on CChainParams.
- Implements access to CChainParams' m_assumed_blockchain_size and m_assumed_chain_state_size on node interface.
- Implements m_assumed_blockchain_size and m_assumed_chain_state_size on qt/intro via node interface.
- Updates release process document with the new CChainParam's values.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-process.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/release-process.md b/doc/release-process.md index 3ba622ee6d..91270b4f7e 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -22,7 +22,7 @@ Before every minor and major release: Before every major release: * Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/7415) for an example. -* Update [`BLOCK_CHAIN_SIZE`](/src/qt/intro.cpp) to the current size plus some overhead. +* Update [`src/chainparams.cpp`](/src/chainparams.cpp) m_assumed_blockchain_size and m_assumed_chain_state_size with the current size plus some overhead. * Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. Use the output of the RPC `getchaintxstats`, see [this pull request](https://github.com/bitcoin/bitcoin/pull/12270) for an example. Reviewers can verify the results by running `getchaintxstats <window_block_count> <window_last_block_hash>` with the `window_block_count` and `window_last_block_hash` from your output. * Update version of `contrib/gitian-descriptors/*.yml`: usually one'd want to do this on master after branching off the release - but be sure to at least do it before a new major release |