address failed to load latest signer at first place issue #123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After the v1.7 hard fork, which introduced support for Cancun, and the first blob transaction was included in the chain, the L1 network became unstable. This has resulted in nodes being unable to sync with each other.
The following
BAD BLOCK
error has been observed in our RPC node.Why?
here is the code error thrown.
The error occurs because the signer in the Oasys consensus is not compatible with Cancun. This indicates that the latest chain configuration was not applied when creating the consensus engine.
Solution
To resolve this issue, we load the latest chainConfig before creating the consensus engine.