-
Notifications
You must be signed in to change notification settings - Fork 49
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
Unexpected Epoch Change When All Nodes Down #245
Comments
Try to make a time wrap to roll back to: best: #319407 (0x4279…d04e), finalized #315395 (0x2b4c…1b82) |
Hard to make a patch. Too many deps from substrate, we need to add them to our project. Something like this: = note: expected struct `_::_parity_scale_codec::alloc::vec::Vec<(substrate_consensus_babe_primitives::app::Public, _)>` (struct `substrate_consensus_babe_primitives::app::Public`)
found struct `_::_parity_scale_codec::alloc::vec::Vec<(substrate_consensus_babe_primitives::app::Public, _)>` (struct `substrate_consensus_babe_primitives::app::Public`)
= note: perhaps two different versions of crate `substrate_consensus_babe_primitives` are being used? |
Merged
BABE bypass done, ce4ce7a. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to #244, we've to stop all the validator(eleted) nodes and restart them in native mode. But
Unexpected Epoch Change
happended when all nodes down.According to paritytech/substrate#4464, hard spoon is the only option to recover the chain.
The text was updated successfully, but these errors were encountered: