docs: update PDPVerifier upgrade checklist for relative delays - #289
Merged
wjmelements merged 1 commit intoJul 27, 2026
Merged
Conversation
wjmelements
approved these changes
Jul 27, 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.
On top of #285.
What changed
UPGRADE_DELAY_EPOCHSfor the normal planned-upgrade flow;nextUpgrade.afterEpochfor subsequent readiness checks.Why
The existing checklist calculates
AFTER_EPOCHbefore Safe signing, so signing time consumes the requested notice window. Once #285 is deployed, the relative-delay method should be the normal path. The legacy path remains temporarily because the currently deployed v3.4.0 implementation does not exposeannounceUpgradePlan().Temporary compatibility cleanup is tracked in #288.