nanocurrency / roadmap

Issues covering broader features and network upgrades for inclusion in the Nano public roadmap
https://github.com/orgs/nanocurrency/projects/5
BSD 3-Clause "New" or "Revised" License
25 stars 3 forks source link

Bounded block backlog #16

Open zhyatt opened 3 years ago

zhyatt commented 3 years ago

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 commented 1 year ago

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