We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now we archive state using BeaconState.serialize() which is not optimized, see https://github.com/ChainSafe/lodestar/blob/unstable/packages/state-transition/test/perf/util/serializeState.test.ts#L20
BeaconState.serialize()
state.serializeToBytes()
No response
The text was updated successfully, but these errors were encountered:
should be done after we turn on n-historical state by default then we have a bufferPool on chain to be used for archiving state too
Sorry, something went wrong.
we done need this considering #7005
twoeths
Successfully merging a pull request may close this issue.
Problem description
Right now we archive state using
BeaconState.serialize()
which is not optimized, see https://github.com/ChainSafe/lodestar/blob/unstable/packages/state-transition/test/perf/util/serializeState.test.ts#L20Solution description
state.serializeToBytes()
apiAdditional context
No response
The text was updated successfully, but these errors were encountered: