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
Have the flag enable-protocol-upgrade-via-soroban-env-host-prev set by default. Introduce a new flag to exclude prev so it can be used for minor releases after the protocol upgrade.
Why:
Nodes without the prev host will reject protocol upgrades during consensus. During protocol 21 upgrade we saw a validator had built core from source and missed setting this flag. This caused them to loose sync during the upgrade.
The text was updated successfully, but these errors were encountered:
I wonder if we should just remove the flag and always have prev enabled. @graydon Is there any benefit to removing the prev crate other than slightly reducing the binary size?
What:
Have the flag enable-protocol-upgrade-via-soroban-env-host-prev set by default. Introduce a new flag to exclude prev so it can be used for minor releases after the protocol upgrade.
Why:
Nodes without the prev host will reject protocol upgrades during consensus. During protocol 21 upgrade we saw a validator had built core from source and missed setting this flag. This caused them to loose sync during the upgrade.
The text was updated successfully, but these errors were encountered: