upgrade-vaults proposal assumes an earlier governance parameter change #10793
Labels
bug
Something isn't working
contract-upgrade
Governance
Governance
Vaults
VaultFactor (née Treasury)
Describe the bug
The upgrade-vaults proposal assumes at least 1 vault factory governance parameter has previously been changed (i.e. that a notifier has issued a value). On devnet, it seems this was not the case as of the Oct 16/18 vaultFactory upgrades; this left an upgrade pending. The Dec 30 ReplaceAllElectorates coreEval changed the electorate parameter, which prompted the Oct 16/18 upgrade to complete; this left the vaultFactory connected to the Dec 16/18 governance contracts.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Platform Environment
git describe --tags --always
)Additional context
Screenshots
If applicable, add screenshots to help explain your problem, especially for UI interactions.
The text was updated successfully, but these errors were encountered: