-
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
STR-949 chainstate manager v2 and minor chainstate restructures #633
Conversation
Really happy with the general refactoring I did to the CSM logic, this will hopefully make it simpler to make work when rebasing the changes in the other branch. |
Still have to simplify the actual db impls to remove the now-unnecessary chainstate tables/fields. |
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.
Great work, looks much cleaner.
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.
ACK 164930d
Will make some minor changes in response to these comments and rebase. |
61f77e1
to
20554d0
Compare
Rebased and applied fixes. |
Commit: 83ef9ef SP1 Performance Test Results
|
baa70ca
to
df1738b
Compare
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.
Writing WriteBatch
to db seems a bit weird in that it seems to not allow for updating an idx. The rest is good.
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.
ACK f10c7ca
f10c7ca
to
5a74505
Compare
Okay this should be good to go now. I don't want to force merge this. |
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.
unused file likely retained during conflict fix.
This was moved inside crates/sequencer
Force merging because we have a few approvals already and we want to keep velocity up. |
Description
This is a second attempt at doing the chainstate manager now with some better idea of the context, plus some additional types to support work in the other PR. I expect some more things will be copied over that are related and minimally invasive.
Type of Change
Notes to Reviewers
Checklist
Related Issues