Skip to content

[DataAvailability] Create in-memory Registers storage implementation #7186

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

Closed
peterargue opened this issue Mar 24, 2025 · 0 comments · Fixed by #7233
Closed

[DataAvailability] Create in-memory Registers storage implementation #7186

peterargue opened this issue Mar 24, 2025 · 0 comments · Fixed by #7233
Assignees
Labels

Comments

@peterargue
Copy link
Contributor

peterargue commented Mar 24, 2025

Create an in-memory implementation of the storage.Registers interface. As a preliminary step, split Registers into 2 interfaces: RegistersReader and the main interface (similar to TransactionResults)

Next, implement all methods.

The cache will be used concurrently, however, data will be written once and immutable. We can take advantage of this to avoid adding a lock by checking if data was written before reading/writing.

The value for FirstHeight should be passed in during construction, and the value for LatestHeight should be passed in during the call to Store.

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

Successfully merging a pull request may close this issue.

2 participants