feat: create new core data & blockstore that acts as a cache/buffered store #287
Labels
dif/medium
Prior experience is likely helpful
effort/days
Estimated to take multiple days, but less than a week
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
status/in-progress
In progress
see ipfs/helia-http-gateway#18
We should be able to use a store like so:
That would take any blockstore as a "fronting" blockstore, and another blockstore as a "backing" blockstore, and would use the front blockstore for immediate writes (cache), and flush that data to the backing blockstore according to some criteria.
This should work similar to https://github.com/ChainSafe/lodestar/blob/unstable/packages/beacon-node/src/network/peers/datastore.ts?rgh-link-date=2023-10-19T14%3A35%3A02Z#L71 but be more generic (i.e. not just for peer data)
The text was updated successfully, but these errors were encountered: