-
Notifications
You must be signed in to change notification settings - Fork 5
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
ref: move storage to its own crate #87
Conversation
idx_bytes[7], | ||
]) | ||
} else { | ||
self.put_cf(metadata, LAST_REPEATED_KEY_INDEX, u64::to_be_bytes(0))?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I always wondered what this was for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understood it, that would just ensure that we put in an entry if we didn't have one before. Though, since we update it after every new initial write anyways I don't think we need that
This is the first step towards being able to create snapshots out of the current merkle tree state. Previously we had two separate databases defined in the main crate,
InnerDB
&SnapshotDB
. This PR moves them into a new one,state-reconstruction-storage
, and also renames them as follows:InnerDB
->ReconstructionDatabase
SnapshotDB
->SnapshotDatabase