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

Document local data storage in a spec document #1311

Closed
whyrusleeping opened this issue Nov 10, 2018 · 1 comment
Closed

Document local data storage in a spec document #1311

whyrusleeping opened this issue Nov 10, 2018 · 1 comment

Comments

@whyrusleeping
Copy link
Member

Description

We need to document what data a filecoin node stores locally. The exact implementation details are not important here, It doesnt matter if you use leveldb or badger or postgres. The main thing I want here is effectively an interface description of the 'Repo', and an indication of what storage operations we have. For example, we have the keystore which we use to track private keys, we have block storage for content addressed data, we have a way to store various bits of chain state, and a pretty solid amount of other stuff.

Acceptance criteria

  • More detail than 'filecoin needs a KV store'
  • Less detail than every byte that goes where on disk
  • Must accurately account for everything we are persisting to disk, and why

Risks + pitfalls

Where to begin

Create a new doc in the specs repo called either repo.md or local-storage.md

@whyrusleeping whyrusleeping added the P1 High - we should be working on this now or in the immediate future label Nov 10, 2018
@mishmosh
Copy link
Contributor

because it's not protocol-affecting, more of an "implementation suggestions" section, not picking this up at this time

@mishmosh mishmosh removed the P1 High - we should be working on this now or in the immediate future label Jan 24, 2019
@anorth anorth closed this as completed Mar 1, 2020
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