Inside Bitcoin
Opening the selected file…
Inside Bitcoin
Opening the selected file…
The code behind the network, with room to understand it.
Release published 2026-10-28 · Snapshot fetched 2026-11-01. Latest stable release at fetch time; development branches and Git history are excluded. Only the selected code window and visible folders load here.
2512. The `SHA256SUMS` file2533. The `SHA256SUMS.asc` combined signature file you just created.255- After uploading release candidate binaries, notify the bitcoin-core-dev mailing list and256bitcoin-dev group that a release candidate is available for testing. Include a link to the release257notes draft.259- The server will automatically create an OpenTimestamps file and torrent of the directory.261- Optionally help seed this torrent. To get the `magnet:` URI use:263```sh264transmission-show -m <torrent file>265```267Insert the magnet URI into the announcement sent to mailing lists. This permits268people without access to `bitcoincore.org` to download the binary distribution.269Also put it into the `optional_magnetlink:` slot in the YAML file for270bitcoincore.org.272- Archive the release notes for the new version to `doc/release-notes/release-notes-${VERSION}.md`273(branch `master` and branch of the release).275- Update the bitcoincore.org website277- blog post279- maintained versions [table](https://github.com/bitcoin-core/bitcoincore.org/commits/master/_includes/posts/maintenance-table.md)281- RPC documentation update283- See https://github.com/bitcoin-core/bitcoincore.org/blob/master/contrib/doc-gen/286- Update repositories288- Delete post-EOL [release branches](https://github.com/bitcoin/bitcoin/branches/all) and create a tag `v${branch_name}-final`.290- Delete ["Needs backport" labels](https://github.com/bitcoin/bitcoin/labels?q=backport) for non-existing branches.292- Update packaging repo294- Push the flatpak to flathub, e.g. https://github.com/flathub/org.bitcoincore.bitcoin-qt/pull/2296- Push the snap, see https://github.com/bitcoin-core/packaging/blob/main/snap/local/build.md298- Create a [new GitHub release](https://github.com/bitcoin/bitcoin/releases/new) with a link to the archived release notes300- Announce the release, along with any security advisory pre-announcements:302- bitcoin-dev and bitcoin-core-dev mailing list304- Bitcoin Core announcements list https://bitcoincore.org/en/list/announcements/join/306- Bitcoin Core Twitter https://twitter.com/bitcoincoreorg308- Celebrate310### Additional information312#### <a name="how-to-calculate-assumed-blockchain-and-chain-state-size"></a>How to calculate `m_assumed_blockchain_size` and `m_assumed_chain_state_size`314Both variables are used as a guideline for how much space the user needs on their drive in total, not just strictly for the blockchain.315Note 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.317To calculate `m_assumed_blockchain_size`, take the size in GiB of these directories:318- For `mainnet` -> the data directory, excluding the `/testnet3`, `/testnet4`, `/signet`, and `/regtest` directories and any overly large files, e.g. a huge `debug.log`319- For `testnet` -> `/testnet3`320- For `testnet4` -> `/testnet4`321- For `signet` -> `/signet`323To calculate `m_assumed_chain_state_size`, take the size in GiB of these directories:324- For `mainnet` -> `/chainstate`325- For `testnet` -> `/testnet3/chainstate`326- For `testnet4` -> `/testnet4/chainstate`327- For `signet` -> `/signet/chainstate`329Notes:330- When taking the size for `m_assumed_blockchain_size`, there's no need to exclude the `/chainstate` directory since it's a guideline value and an overhead will be added anyway.331- The expected overhead for growth may change over time. Consider whether the percentage needs to be changed in response; if so, update it here in this section.
Independent explanations by MyBitcoinExplorer. Not affiliated with or endorsed by Bitcoin Core. Guides are educational and do not replace the source or its tests.
Bitcoin Core source © its contributors, distributed under the MIT license. Original notices and bundled third-party licenses are retained in the source tree.