You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to run gpbft without being able to vote in the network.
The requirement that we receive messages from ourselves makes this impossible.
It also causes gpbft to have to be terminated if the async signing fails.
I don't have a good solution for this on top of my head.
The text was updated successfully, but these errors were encountered:
The requirement to receive own messages is gone now. It's reasonably likely this will now "just work" with a host that simply ignores attempts to broadcast messages (because there's no ID or power associated with the participant).
One thing this might need is a flag or something to accept all chains during the QUALITY phase. A passive node has no preferred chain of their own or incentive to have one, because they're not even necessarily running or observing EC. I think if we just input base chain every time, the node might be unnecessarily reluctant to accept proposals through the prepare and commit phases. But I could be wrong.
It should be possible to run gpbft without being able to vote in the network.
The requirement that we receive messages from ourselves makes this impossible.
It also causes gpbft to have to be terminated if the async signing fails.
I don't have a good solution for this on top of my head.
The text was updated successfully, but these errors were encountered: