Skip to content
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

Add --no-sync-pruned-blocks, and enable syncing pruned blocks by default for pruned nodes #9180

Closed
wants to merge 2 commits into from

Conversation

expiredhotdog
Copy link

@expiredhotdog expiredhotdog commented Feb 19, 2024

Resolves #8834.

Edit: closed because this got needlessly messy

@expiredhotdog expiredhotdog changed the title Add --no-sync-pruned-blocks, and enable syncing pruned blocks by default Add --no-sync-pruned-blocks, and enable syncing pruned blocks by default for pruned nodes Feb 19, 2024
Copy link
Collaborator

@selsta selsta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about changing

const command_line::arg_descriptor<bool> arg_sync_pruned_blocks  = {

to

const command_line::arg_descriptor<unit64_t> arg_sync_pruned_blocks  = {

and then setting it to 1 as default value. Then someone who wants to disable it can do --sync-pruned-blocks 0 and we don't have to add another flag. See the --fast-block-sync flag as an example that works this way.

@expiredhotdog
Copy link
Author

expiredhotdog commented Feb 21, 2024

@selsta This change was modeled after #3191, with the intent of doing the same as #8855 at some point in the future. The reasoning for adding --no-fluffy-blocks at the time was to avoid breaking anyone's scripts, which I somewhat agree with.

I'm happy to change it if you think the unit64_t version would be better, though.

extra sanity checking

update autocomplete

simplify
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider enabling --sync-pruned-blocks by default for pruned nodes
3 participants