Skip to content
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

chaincmd: correctly create consortium engine in import chain #371

Merged
merged 3 commits into from
May 21, 2024

Conversation

minh-bq
Copy link
Contributor

@minh-bq minh-bq commented Oct 20, 2023

Currently, when import chain is used, we don't recognize the chain config to
create the consortium engine. This commit creates the consortium engine when it
is set in the chain config.

@minh-bq minh-bq marked this pull request as ready for review March 4, 2024 06:50
@minh-bq minh-bq force-pushed the fix/import-chain-consensus branch from 2c0e312 to 9a30eea Compare May 21, 2024 03:28
Currently, when import chain is used, we don't recognize the chain config to
create the consortium engine. This commit creates the consortium engine when it
is set in the chain config.
In version 1, the checkpoint header check happens early in the header
verification step. This makes statedb read sometimes happens in incorrect
statedb. While full sync, this leads to peer drop but still be able to continue
syncing with other peers. However, while running import chain command or fast
sync, this could lead to error. Add a option to disable checkpoint header check
in these cases.
@minh-bq minh-bq force-pushed the fix/import-chain-consensus branch from 9a30eea to edb1059 Compare May 21, 2024 04:19
@minh-bq minh-bq merged commit 0564e55 into axieinfinity:master May 21, 2024
1 check passed
@minh-bq minh-bq deleted the fix/import-chain-consensus branch May 21, 2024 04:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants