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

Add the ability to prune specific Celestia blocks in the IPFS store #442

Closed
2 tasks
evan-forbes opened this issue Jun 30, 2021 · 4 comments
Closed
2 tasks

Comments

@evan-forbes
Copy link
Member

Summary

Add the ability to delete a specific block's data in the embedded IPFS node's blockstore, and do so while pruning.

Details

delete block data from the IPFS blockstore for a specific block height while pruning.
https://github.com/lazyledger/lazyledger-core/blob/004a1a9abcf95e5f0d5299f18f694146bc9473b4/store/store.go#L312-L316

Action Items

  • Implement the ability to remove a specific block's data
  • Delete block data while pruning

References

Will eventually be related to #393

@Wondertan
Copy link
Member

@evan-forbes, @liamsi, what's the use case for pruning?

@evan-forbes
Copy link
Member Author

evan-forbes commented Jun 30, 2021

what's the use case for pruning?

anything that's not a storage node. I think this should have been included in #374, just to not break already existing functionality.

@liamsi
Copy link
Member

liamsi commented Jul 7, 2021

If we still with the augment tendermint nodes to serve IPFS directly, then an additional feature I'd throw in the mix would be the ability to prune the erasure coding too. This will be a bit tricky as we still want storage nodes to recompute and serve these shares although they were deleted from the local store.
So we'd need:

  • the ability to completely prune old blocks
  • the ability to only prune the extended/erasured data

@evan-forbes
Copy link
Member Author

closing as IPFS or erasured block data is no longer included in celestia-core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants