This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Incorrect (really big) number of confirmed blocks in header when producer get voted out then voted in again #3835
Comments
Great ~
So last produce block num - 1 means irreversible? |
Later I found out this is not really a big issue. |
Where can I find the actual content of a block on EOS? |
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 9, 2018
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 9, 2018
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 9, 2018
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 9, 2018
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 9, 2018
This was referenced Jul 9, 2018
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 10, 2018
…equest changes. GH EOSIO#3835
brianjohnson5972
added a commit
to brianjohnson5972/eos
that referenced
this issue
Jul 10, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We recently find a bug in producer plugin that cause the synchronization fails.
This is the short story:
In my understanding, we should fix this in the producer plugin, by not confirming the blocks that already became irreversible, instead of just checking the watermark (last produce block num).
related log:
The text was updated successfully, but these errors were encountered: