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.

Sign up for GitHub

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

Jump to bottom

Components should robustly sync their state with the chain #3570

Closed
Tracked by #3366
alexghr opened this issue Dec 5, 2023 · 0 comments
Closed
Tracked by #3366

Components should robustly sync their state with the chain #3570

alexghr opened this issue Dec 5, 2023 · 0 comments
Assignees
@alexghr

Comments

@alexghr
Copy link
Contributor

alexghr commented Dec 5, 2023

Double check that components synch data from the chain in a robust way and that they have a consistent view of the chain state (ie. we don't up with archiver at block 20 and world state at block 17 and then the sequencer tries to build block 21 based on block 17's tree roots)
@github-project-automation github-project-automation bot moved this to Todo in A3 Dec 5, 2023
This was referenced Dec 5, 2023
Closed
Merged
@alexghr alexghr self-assigned this Dec 12, 2023
alexghr added a commit that referenced this issue Dec 13, 2023
@alexghr
feat: persist pxe state (#3628)
9ccbbd9 
This PR adds a persistent database to PXE. I've created a new package in
the monorepo called `@aztec/kv-store` which exports a set of general
data structures that can be used by components to store state in
consistent manner. The only implementation right now is with LMDB (both
persisted on disk and in-memory/temporary file).

This higher level abstraction allowed me to easily add storage to ~PXE's
note processors, its synchronizer and~ the key store too.

Fix #3364 

Changes to the synchronizer and note processors have been taken out and
will be merged in a separate PR (as part of #3570) because it will
require some changes to the benchmarking code.

Synch changes here #3673
@alexghr alexghr moved this from Todo to In Progress in A3 Jan 9, 2024
michaelelliot pushed a commit to Swoir/noir_rs that referenced this issue Feb 28, 2024
@alexghr
feat: persist pxe state (AztecProtocol#3628)
43323fa 
This PR adds a persistent database to PXE. I've created a new package in
the monorepo called `@aztec/kv-store` which exports a set of general
data structures that can be used by components to store state in
consistent manner. The only implementation right now is with LMDB (both
persisted on disk and in-memory/temporary file).

This higher level abstraction allowed me to easily add storage to ~PXE's
note processors, its synchronizer and~ the key store too.

Fix AztecProtocol#3364 

Changes to the synchronizer and note processors have been taken out and
will be merged in a separate PR (as part of AztecProtocol#3570) because it will
require some changes to the benchmarking code.

Synch changes here AztecProtocol#3673
@alexghr alexghr closed this as completed Nov 13, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in A3 Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexghr alexghr

Labels
None yet
Projects
A3
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexghr