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.

Sign up for GitHub

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

Jump to bottom

feat: Ability to become an archival mode after running in pruned mode #3403

Open
renaynay opened this issue May 15, 2024 · 0 comments
Open

feat: Ability to become an archival mode after running in pruned mode #3403

renaynay opened this issue May 15, 2024 · 0 comments
Labels
architecture Architecture / design-related issues area:das Related to DASer area:storage

Comments

@renaynay
Copy link
Member

Node must be able to re-sync blocks it has pruned if it returns to archival mode after having had pruning mode enabled.

Ideas

  • DASer resets its checkpoint to 1 and pruner resets its checkpoint
@renaynay renaynay added area:storage architecture Architecture / design-related issues area:das Related to DASer labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture Architecture / design-related issues area:das Related to DASer area:storage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@renaynay