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

Bounded block backlog #16

Open
zhyatt opened this issue Oct 4, 2021 · 1 comment
Open

Bounded block backlog #16

zhyatt opened this issue Oct 4, 2021 · 1 comment
Labels
ledger management

Comments

@zhyatt
Copy link
Contributor

zhyatt commented Oct 4, 2021 •
edited
Loading

Summary
The backlog of potential blocks to confirm can be considered unbounded due to writing blocks to the ledger on disk. This persisting of unconfirmed blocks on disk may not be necessary so options for bounding the backlog, such as keeping unconfirmed blocks only in memory, are being explored.

What problem would be solved by this feature?
By keeping the backlog bounded, disk usage or unconfirmed blocks can be reduced.

Related resources
@qwahzi qwahzi mentioned this issue Aug 13, 2023
Open
@qwahzi
Copy link

qwahzi commented Aug 19, 2023

Removing this one from the roadmap board, since it's been replaced by 4198

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ledger management
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zhyatt @qwahzi