Skip to content

multi: Update outdated IBD refs to inital chain sync. #3490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jun 3, 2025

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Jun 3, 2025

Historically, initial block download consisted of downloading all blocks one-by-one in a linear fashion and only storing them once they had been fully verified, so the terminology of initial block download accurately described the process.

However, the logic related to initial chain syncing was changed long ago to a much more efficient and robust approach based on downloading the headers first and then using those to guide the sync process.

This updates the remaining references in the code to more accurately refer to the initial chain sync process/mode accordingly.

The following is an overview of the changes:

  • Updates the help text for the initialblockdownload field of the getblockchaininfo RPC to refer to the initial chain sync mode
    • NOTE: The RPC field name was not updated to avoid breaking the API
  • Updates several comments in peer, blockchain, and netsync
  • Updates the JSON-RPC API docs description to match

@davecgh davecgh added this to the 2.1.0 milestone Jun 3, 2025
davecgh added 2 commits June 3, 2025 15:20
This updates the help text for the initialblockdownload field of the
getblockchaininfo RPC to more accurately refer to the initial chain sync
mode that it represents since what was previously the initial block
download no longer applies and hasn't for a very long time.

Historically, initial block download consisted of downloading all blocks
one-by-one in a linear fashion and only storing them once they had been
fully verified, so the terminology of initial block download accurately
described the process.

However, the logic related to initial chain syncing was changed long ago
to a much more efficient and robust approach based on downloading the
headers first and then using those to guide the sync process.

The RPC field name was not updated to avoid breaking the API, but its
meaning changed and this updates the text accordingly.
This updates the description of the initialblockdownload field to more
accurately refer to the initial chain sync mode that it represents.
@davecgh davecgh force-pushed the multi_consistent_initial_chain_sync branch from 080de83 to 3339a78 Compare June 3, 2025 20:20
@davecgh davecgh merged commit 3339a78 into decred:master Jun 3, 2025
2 checks passed
@davecgh davecgh deleted the multi_consistent_initial_chain_sync branch June 3, 2025 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants