-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Split initial state from chain config #1459
Split initial state from chain config #1459
Conversation
…/fuel-core into feature/split-state-from-config
…s/fuel-core into feature/split-state-from-config
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.
LGTM. I feel like I'm lacking a little context in the goals of the overall feature and the followup work, but I'm happy with everything here.
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.
Thank you, looks definitely much better than everything in one structure!=)
Small comments that should be easy to resolve and we can merge
Co-authored-by: Brandon Vrooman <brandon.vrooman@fuel.sh>
Co-authored-by: Brandon Vrooman <brandon.vrooman@fuel.sh>
…/fuel-core into feature/split-state-from-config
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.
Thanks for putting this together and addressing all the feedback!
…feature/split-state-from-config
Closes #1450
Separates the loading of the initial chain state from loading
ChainConfig
.The parameters to the run command have been renamed to
chain_params
andchain_state
. Should we rename the corresponding structsChainConfig
andStateConfig
accordingly?The block height is moved to the
ChainConfig
to be available instantly because theStateConfig
will be streamed in a later PR.