feat: basic persistent storage #8
Conversation
|
|
||
| /// Struct containing the fields used for restoring the tree state. | ||
| #[derive(Serialize, Deserialize)] | ||
| pub struct StateSnapshot { |
There was a problem hiding this comment.
Idea for the future: Could we store the latest root hash here as well and use that to verify that tree & index key map are in sync?
| /// The latest l1 block number that was processed. | ||
| pub current_l1_block_number: u64, |
There was a problem hiding this comment.
I just realized something: When we import state from other sources (e.g. file), there's no such thing as L1 block number, right?
There was a problem hiding this comment.
That might be the case, I'm not sure what the file format would look like at this point so I can't really answer that. Either way though, I think we can defer this issue to a later PR, what do you say?
There was a problem hiding this comment.
Yes, definitely. I'm actually working on async L1Fetcher right now, based on your code here, so hence the thought. Let's see how this gets shape 🙂
zeapoz
force-pushed
the
feat/persistent-storage
branch
from
d26d3b6 to
720a1b5
Compare
Allows for the restoration of the state when the tool was last used.
StateSnapshotstructthat stores:state.rs->types.rs.Note: this PR does not implement graceful shutdown, so the snapshot file can in rare instances get out of sync with the local database.