Skip to content

Commit 895fbd7

Browse files
author
MarcoFalke
committed
Merge #12309: doc: Explain how to update chainTxData in release process
7f968ae doc: Explain how to update chainTxData in release process (Wladimir J. van der Laan) Pull request description: Adds a short explanation how to update chainTxData to the release process. Mention where to get the data, and link to an example. Tree-SHA512: 66b0eb12a25afb7b1da0788c8f9f9701d566cb7ce55899402440a57bef0e177b55e926442d3c8aa482299abe7c48ab94735d501c37f0a11fefb86e2fc2e33d9b
2 parents 216f9a4 + 7f968ae commit 895fbd7

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

doc/release-process.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ Before every major release:
2323

2424
* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/7415) for an example.
2525
* Update [`BLOCK_CHAIN_SIZE`](/src/qt/intro.cpp) to the current size plus some overhead.
26-
* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate.
26+
* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. Use the output of the RPC `getchaintxstats`, see
27+
[this pull request](https://github.com/bitcoin/bitcoin/pull/12270) for an example.
2728
* 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
2829

2930
### First time / New builders

0 commit comments

Comments
 (0)