chore: include StateView in v1.3.1 rollout - #568
Merged
Conversation
Kubuxu
approved these changes
Aug 5, 2026
github-project-automation
Bot
moved this from 🔎 Awaiting review
to ✔️ Approved by reviewer
in FOC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
FWSS_VIEWin the Calibnet and Mainnet deployment metadata.Why
The v1.3.1 FWSS implementation preserves the original proving activation epoch when an emptied or suspended dataset is reactivated. The candidate StateView contains the matching canonical challenge-window calculation; the currently deployed StateView instead reverts with
ProvingPeriodNotInitializedwhen no proving deadline is active.Leaving StateView pinned would therefore ship only half of the reactivation behavior. Removing the two policy pins lets the metadata-aware Warm Storage stack run deploy one candidate StateView per network.
For an existing Safe-owned FWSS proxy, the deployment workflow does not switch the View automatically. It records the new address and prints the separate
setViewContractowner action required by the release checklist.