Context
Action item from the 2026-05-28 Hotfix FWSS v1.2.0 / PDPVerifier v3.4.0 postmortem. During the hotfix incident, the team rolled forward rather than rolling back. We need a documented rollback procedure and supporting scripts so that rollback is a viable, low-friction option when an upgrade goes wrong.
Notion tracking: PDP and FWSS have a rollback procedure and script
Goals
- Document a clear rollback procedure for both PDP (PDPVerifier) and FWSS (FilecoinWarmStorageService) contract upgrades.
- Provide a script (or set of scripts) that can execute a rollback without requiring the operator to think through the steps under pressure.
- Cover both calibration and mainnet scenarios.
- Address when rollback is and isn't safe (e.g., state migrations that make rollback unsafe).
Scope
This issue lives in filecoin-services but will require PRs in both repos:
- FilOzone/filecoin-services — FWSS rollback procedure and script
- FilOzone/pdp — PDPVerifier rollback procedure and script
Related
Context
Action item from the 2026-05-28 Hotfix FWSS v1.2.0 / PDPVerifier v3.4.0 postmortem. During the hotfix incident, the team rolled forward rather than rolling back. We need a documented rollback procedure and supporting scripts so that rollback is a viable, low-friction option when an upgrade goes wrong.
Notion tracking: PDP and FWSS have a rollback procedure and script
Goals
Scope
This issue lives in filecoin-services but will require PRs in both repos:
Related