iBFT can decide on attestation/ proposal data which is not equal to what our local beacon node returned (might be due to a fork for example).
Scenario:
We start instance A with input value Val_1
Other iBFT members send a pre-prepare with Val_2
iBFT decides on Val_2
What should we do?
As of now I'm not sure our iBFT implementation supports this scenario.
What we will have is basically a fork.
2/3 of the group decided a round but we can't validate it (maybe they have a different version of SSV, maybe our beacon is forked, etc.).
In this case our node should try and sync with the other nodes to solve the issue, he might not be able to and will halt
[Originally posted by @alonmuroch]
iBFT can decide on attestation/ proposal data which is not equal to what our local beacon node returned (might be due to a fork for example). Scenario:
As of now I'm not sure our iBFT implementation supports this scenario. What we will have is basically a fork. 2/3 of the group decided a round but we can't validate it (maybe they have a different version of SSV, maybe our beacon is forked, etc.). In this case our node should try and sync with the other nodes to solve the issue, he might not be able to and will halt