Update outdated _config.yml variables to reflect April 2026 state#4668
Merged
Cobra-Bitcoin merged 1 commit intobitcoin-dot-org:masterfrom Apr 20, 2026
Merged
Conversation
Contributor
Author
|
Just checking if there’s any feedback on this. @Cobra-Bitcoin |
Contributor
|
LGTM. Thank you! |
Contributor
Author
|
Tks @Cobra-Bitcoin |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related: #4662
Summary
The
_config.ymlfile contains a comment indicating "Values last updated 2018-10-16" for several variables used across multiple pages of the site (full-node descriptions, block chain size references, mining reward mentions). This PR updates the outdated values to reflect the current state of the Bitcoin network as of April 2026.Changes
subsidy_in_decimal_bitcoinsbitcoin_datadir_gbchain_gbbitcoin_datadir_gb, maintaining the original ~10 GB gap for chainstate and block indices.total_tx_count_in_millionsNotes
bitcoin_datadir_gb_pruned: 7variable was intentionally left unchanged, as 7 GB remains the documented minimum for running a pruned node (per bitcoin.org/en/full-node).site.text.*variables, including the full-node page, wallet validation descriptions, and initial sync notes.