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
This is a hypothetical feature that have been discussed on a few occasions.
It could be useful for multiple proposals to be enacted together or not at all. Here are some use cases:
Two protocol parameters from different groups are needed to be updated together atomically, however separate groups will impose separate voting thresholds and potentially might cause SPOs vote on a parameter that they normally would not be required to vote on (eg. one parameter is from a security group while another is not)
Two unrelated proposal types must be enacted together, eg a ParameterUpdate is enacted only if HardForkInitiation was enacted
The text was updated successfully, but these errors were encountered:
This is a hypothetical feature that have been discussed on a few occasions.
It could be useful for multiple proposals to be enacted together or not at all. Here are some use cases:
ParameterUpdate
is enacted only ifHardForkInitiation
was enactedThe text was updated successfully, but these errors were encountered: