-
Notifications
You must be signed in to change notification settings - Fork 73
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
ship in 4.0.4: head.block_num is 2 blocks behind trace_end_block and chain_state_end_block #1694
Milestone
Comments
heifner
added a commit
that referenced
this issue
Oct 13, 2023
heifner
added a commit
that referenced
this issue
Oct 16, 2023
[4.0] Signal accepted_block after it is marked valid
heifner
added a commit
that referenced
this issue
Oct 16, 2023
heifner
added a commit
that referenced
this issue
Oct 16, 2023
[4.0 -> 5.0] Signal accepted_block after it is marked valid
heifner
added a commit
that referenced
this issue
Oct 16, 2023
heifner
added a commit
that referenced
this issue
Oct 16, 2023
[5.0 -> main] Signal accepted_block after it is marked valid
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Head block in ship response to
get_status_request_v0
is supposed to be the same as the last block in traces.As of 4.0.4, the head block is always 2 blocks behind. Here's the test that reproduces it with Proton mainnet (Proton is much smaller than EOS, but running standard Leap software).
The text was updated successfully, but these errors were encountered: