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
HBBFT POSDAO checks currently hold a write lock, even if they are just reading the state.
We can split it up to only acquire a write lock after a read lock showed that we need to update the hbbft state.
The text was updated successfully, but these errors were encountered:
SurfingNerd
added a commit
to SurfingNerd/openethereum-3.x
that referenced
this issue
Aug 23, 2022
we did a lock management optimization in diamond-node.
we still can take a review into this branch vs current implementation.
maybe there are good takes in this branch that are not implemented in diamond-node.
HBBFT POSDAO checks currently hold a write lock, even if they are just reading the state.
We can split it up to only acquire a write lock after a read lock showed that we need to update the hbbft state.
The text was updated successfully, but these errors were encountered: