You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/release-process.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -28,15 +28,15 @@ Release Process
28
28
29
29
#### Before branch-off
30
30
31
-
* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/7415) for an example.
31
+
* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/27488) for an example.
32
32
* Update the following variables in [`src/kernel/chainparams.cpp`](/src/kernel/chainparams.cpp) for mainnet, testnet, and signet:
33
33
-`m_assumed_blockchain_size` and `m_assumed_chain_state_size` with the current size plus some overhead (see
34
34
[this](#how-to-calculate-assumed-blockchain-and-chain-state-size) for information on how to calculate them).
35
35
- The following updates should be reviewed with `reindex-chainstate` and `assumevalid=0` to catch any defect
36
36
that causes rejection of blocks in the past history.
37
37
-`chainTxData` with statistics about the transaction count and rate. Use the output of the `getchaintxstats` RPC with an
38
38
`nBlocks` of 4096 (28 days) and a `bestblockhash` of RPC `getbestblockhash`; see
39
-
[this pull request](https://github.com/bitcoin/bitcoin/pull/20263) for an example. Reviewers can verify the results by running
39
+
[this pull request](https://github.com/bitcoin/bitcoin/pull/28591) for an example. Reviewers can verify the results by running
40
40
`getchaintxstats <window_block_count> <window_final_block_hash>` with the `window_block_count` and `window_final_block_hash` from your output.
41
41
-`defaultAssumeValid` with the output of RPC `getblockhash` using the `height` of `window_final_block_height` above
42
42
(and update the block height comment with that height), taking into account the following:
@@ -45,7 +45,7 @@ Release Process
45
45
-`nMinimumChainWork` with the "chainwork" value of RPC `getblockheader` using the same height as that selected for the previous step.
46
46
* Consider updating the headers synchronization tuning parameters to account for the chainparams updates.
47
47
The optimal values change very slowly, so this isn't strictly necessary every release, but doing so doesn't hurt.
48
-
- Update configuration variables in [`contrib/devtools/headerssync-params.py`](contrib/devtools/headerssync-params.py):
48
+
- Update configuration variables in [`contrib/devtools/headerssync-params.py`](/contrib/devtools/headerssync-params.py):
49
49
- Set `TIME` to the software's expected supported lifetime -- after this time, its ability to defend against a high bandwidth timewarp attacker will begin to degrade.
50
50
- Set `MINCHAINWORK_HEADERS` to the height used for the `nMinimumChainWork` calculation above.
51
51
- Check that the other variables still look reasonable.
0 commit comments