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

Minimize disk dependency for chunk validators #12743

Open
walnut-the-cat opened this issue Jan 15, 2025 · 0 comments
Open

Minimize disk dependency for chunk validators #12743

walnut-the-cat opened this issue Jan 15, 2025 · 0 comments
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. community Issues created by community P-low Priority: low T-core Team: issues relevant to the core team

Comments

@walnut-the-cat
Copy link
Contributor

Currently chunk validators need at least Blocks. But it should be possible to reduce disk dependency to (usually) short range of BlockHeaders. The range may be non-trivial because state witness can cover arbitrary range of blocks in case of missing chunks.

It's not a straightforward change, because during implementation we assumed dependency on Chain and EpochManager everywhere. And I think BlockSync is always enabled by default so we need an option to tweak that. We could even put BlockHeaders to memory but that's hard implementation wise, and makes chunk validator less reliable - if stopped, it'd need to download headers from somewhere before being able to perform validation again.

But if one implements that, disk usage will be reduced to, usually, near zero. Doesn't look like a high priority feature in the protocol, but nice and meaningful to have.

relevant discussion: link

@walnut-the-cat walnut-the-cat added C-enhancement Category: An issue proposing an enhancement or a PR with one. community Issues created by community P-low Priority: low T-core Team: issues relevant to the core team labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. community Issues created by community P-low Priority: low T-core Team: issues relevant to the core team
Projects
None yet
Development

No branches or pull requests

1 participant