PDPVerifier upgrade from `v3.4.0` to `v3.5.0`

[BigLep]

This is part of the "202608 FOC Release": FilOzone/filecoin-services#597

Items that are in scope: https://github.com/FilOzone/pdp/milestone/10

---

Summary

Track the successive rollout of PDPVerifier from v3.4.0 to v3.5.0, with Calibration first and Mainnet second.

This issue is the full operational checklist for the rollout and release closeout.

Rollout Status

Network	Announced	Executable on or after	Executed	Notes
Calibration	Pending	TBD	Pending	Upgrade first; fill in the planned-upgrade transaction and timestamp when announced.
Mainnet	Pending	TBD	Pending	Upgrade after Calibration execution and smoke tests pass.

Operational Notes

Details

- Use this single issue to track the full rollout across both networks. - Confirm the live proxy `VERSION()` separately; it may lag the release baseline if recent releases did not include a PDPVerifier deployment. - Record major steps as issue comments as you go rather than editing every detail into the top post. - Use `UPGRADE_DELAY_EPOCHS` for the normal planned-upgrade flow once the live proxy exposes `announceUpgradePlan()`. Use the temporary `AFTER_EPOCH` bootstrap path only when upgrading from an implementation that predates that method; removal is tracked in #288. - After an announcement executes, read and record the observed `nextUpgrade.afterEpoch`. Use that observed value for all subsequent readiness checks. - Do not deploy until all bytecode-affecting PRs are merged to `main`. - If the release tag must match the exact on-chain bytecode, tag the deploy commit before changelog-only closeout changes. Otherwise, tag the finalized release-notes commit and record the implementation deploy commit separately. - The current `tools/deploy-calibnet.sh` and `tools/deploy-mainnet.sh` also deploy a fresh proxy. For upgrades, the safest path is still: - deploy the implementation manually with `forge create` - generate SAFE calldata with `tools/upgrade.sh` - `tools/upgrade.sh` prints the SAFE contract's on-chain nonce. The Safe UI may queue the transaction at a higher nonce if there are already pending transactions. That does not change the contract calldata.

Suggested release tag:

• v3.5.0

Network Constants

• Mainnet proxy: 0xBADd0B92C1c71d02E7d520f64c0876538fa2557F
• Calibration proxy: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
• SAFE owner: 0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5
• Mainnet RPC: https://api.node.glif.io/rpc/v1
• Calibration RPC: https://api.calibration.node.glif.io/rpc/v1
• Default planned-upgrade notice window: 2880 epochs (~1 day at 30 seconds/epoch)

Release Preparation

Details

1. Prepare and Merge Release PRs

• Release-prep PR opened and reviewed
  • Include the PDPVerifier.VERSION bump if the deployed contract version is changing.
  • Draft CHANGELOG.md release notes before deployment.
  • Use ## [X.Y.Z] - TBD until the rollout executes.
  • Leave implementation addresses, verification links, and deployment transactions as TBD until known.
  • Include expected integration impact, constructor values, and any required caller changes before starting Calibration.
  • Suggested PR title: docs(changelog): draft vX.Y.Z release notes and version bump
• Release-prep PR merged to main
  • Any PDPVerifier.VERSION bump is bytecode-affecting and must be merged before selecting the deploy commit or deploying any implementation.

2. Freeze the Deploy Commit

• Final deploy commit on main confirmed

git checkout main
git pull --ff-only origin main
git rev-parse HEAD

• Intended VERSION confirmed in src/PDPVerifier.sol
  • If a version-only fix PR is needed: chore: correctly set version to vX.Y.Z

rg -n 'string public constant VERSION' src/PDPVerifier.sol

3. Confirm Constructor Values

• Calibration constructor values confirmed
  • initializerVersion
  • challengeFinality
• Current Calibration proxy initializer counter read

RPC_URL="https://api.calibration.node.glif.io/rpc/v1" \
./tools/get-initialized-counter.sh 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C

• Mainnet constructor values confirmed
  • initializerVersion
  • challengeFinality
• Current Mainnet proxy initializer counter read

RPC_URL="https://api.node.glif.io/rpc/v1" \
./tools/get-initialized-counter.sh 0xBADd0B92C1c71d02E7d520f64c0876538fa2557F

Deploy the next implementation with initializerVersion = <current counter + 1>.

4. Confirm the Live Proxy Owner and Version

• Current Calibration proxy owner confirmed
• Current Calibration proxy version confirmed
• Current Calibration planned-upgrade slot checked

cast call --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  -f 0x0000000000000000000000000000000000000000 \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "owner()(address)"

cast call --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "VERSION()(string)"

cast call --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "nextUpgrade()(address,uint96)"

• Current Mainnet proxy owner confirmed
• Current Mainnet proxy version confirmed
• Current Mainnet planned-upgrade slot checked

cast call --rpc-url https://api.node.glif.io/rpc/v1 \
  -f 0x0000000000000000000000000000000000000000 \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "owner()(address)"

cast call --rpc-url https://api.node.glif.io/rpc/v1 \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "VERSION()(string)"

cast call --rpc-url https://api.node.glif.io/rpc/v1 \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "nextUpgrade()(address,uint96)"

If the owner is a SAFE or other contract owner, use tools/upgrade.sh to generate calldata for the owner workflow rather than broadcasting directly.

5. Confirm the PDP Upgrade Plan

• Named PDP technical owner recorded; they own the written, verified upgrade plan and go/no-go decision
• Exact currently deployed Calibration and Mainnet PDPVerifier versions checked against the target version and recorded
• PDP-related cross-repo changes linked, or explicitly recorded as none

6. Record PDP Rollback Safety

• Rollback decision recorded as safe or unsafe, with rationale
• Applicable PDP rollback procedure/script linked, or a reason recorded for why rollback is not the mitigation

7. Validate PDP in FOC Devnet

• Before Calibration, run foc-devnet with the target PDPVerifier upgrade and link evidence that the post-upgrade PDP state is valid (run evidence)
• Exact current and target PDPVerifier versions used by the validation recorded

Calibration Rollout

• Deploy the new PDPVerifier implementation to Calibration
  • Record deployer address, implementation address, and deployment transaction hash

export RPC_URL="https://api.calibration.node.glif.io/rpc/v1"
export KEYSTORE="..."
export PASSWORD="..."

forge create \
  --rpc-url "$RPC_URL" \
  --keystore "$KEYSTORE" \
  --password "$PASSWORD" \
  --broadcast \
  --chain-id 314159 \
  src/PDPVerifier.sol:PDPVerifier \
  --constructor-args \
  <initializerVersion> \
  10

• Sanity-check VERSION() and immutable values on the Calibration implementation

cast call --rpc-url "$RPC_URL" <IMPL> "VERSION()(string)"
cast call --rpc-url "$RPC_URL" <IMPL> "getChallengeFinality()(uint256)"

• Verify the Calibration implementation on Sourcify
• Verify the Calibration implementation on Blockscout
• Verify the Calibration implementation on Filfox (optional)

CONSTRUCTOR_ARGS=$(cast abi-encode "constructor(uint64,uint256)" \
  <initializerVersion> \
  10 | sed 's/^0x//')

forge verify-contract \
  --chain 314159 \
  --rpc-url "$RPC_URL" \
  --watch \
  --constructor-args "$CONSTRUCTOR_ARGS" \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier

forge verify-contract \
  --chain-id 314159 \
  --verifier blockscout \
  --verifier-url "https://filecoin-testnet.blockscout.com/api/" \
  --force \
  --skip-is-verified-check \
  --watch \
  --constructor-args "$CONSTRUCTOR_ARGS" \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier

filfox-verifier forge \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier \
  --chain 314159

• Calibration planned-upgrade announcement payload generated

Choose exactly one announcement mode below. The default notice window is 2880 Filecoin epochs (~1 day); adjust intentionally if the release needs a longer window.

For the normal delay-based flow, once the live proxy exposes announceUpgradePlan():

NOTICE_EPOCHS=2880
unset AFTER_EPOCH

RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
UPGRADE_DELAY_EPOCHS="$NOTICE_EPOCHS" \
./tools/announce-planned-upgrade.sh

Temporary bootstrap compatibility: The currently deployed PDPVerifier v3.4.0 implementation does not expose announceUpgradePlan(). Use the following legacy flow only while the live proxy predates that method—normally for the first bootstrap, or for separately documented rollback recovery. Remove this section only after the full removal criteria in #288 are satisfied.

NOTICE_EPOCHS=2880
SAFE_SIGNING_BUFFER_EPOCHS=2880
CURRENT_EPOCH=$(cast block-number --rpc-url "$RPC_URL")
AFTER_EPOCH=$((CURRENT_EPOCH + SAFE_SIGNING_BUFFER_EPOCHS + NOTICE_EPOCHS))
unset UPGRADE_DELAY_EPOCHS

RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
AFTER_EPOCH="$AFTER_EPOCH" \
./tools/announce-planned-upgrade.sh

If the Safe UI asks whether to use the implementation ABI for the proxy, use the implementation ABI, but keep the transaction target as the proxy.

• Stage the Calibration planned-upgrade SAFE transaction
• Execute the Calibration planned-upgrade SAFE transaction
• Record the Calibration planned-upgrade announcement transaction hash and update the rollout status table

Read the actual plan after the Safe transaction executes. This verifies that the requested notice window starts at execution and catches a legacy announcement that no longer preserves the full notice period.

ANNOUNCE_TX_HASH="<TX_HASH>"
NOTICE_EPOCHS=2880 # Must match the requested notice used above

if ! ANNOUNCE_STATUS=$(cast receipt --rpc-url "$RPC_URL" "$ANNOUNCE_TX_HASH" status); then
  echo "ERROR: failed to read the announcement receipt"
  exit 1
fi

ANNOUNCE_STATUS=${ANNOUNCE_STATUS%% *}
if [ "$ANNOUNCE_STATUS" != "1" ] && [ "$ANNOUNCE_STATUS" != "0x1" ]; then
  echo "ERROR: announcement transaction did not succeed (status $ANNOUNCE_STATUS)"
  exit 1
fi

if ! ANNOUNCE_EPOCH=$(cast receipt --rpc-url "$RPC_URL" "$ANNOUNCE_TX_HASH" blockNumber); then
  echo "ERROR: failed to read the announcement epoch"
  exit 1
fi

if [[ "$ANNOUNCE_EPOCH" =~ ^0x[0-9a-fA-F]+$ ]]; then
  ANNOUNCE_EPOCH=$((ANNOUNCE_EPOCH))
elif ! [[ "$ANNOUNCE_EPOCH" =~ ^[0-9]+$ ]]; then
  echo "ERROR: invalid announcement epoch: $ANNOUNCE_EPOCH"
  exit 1
fi

if ! UPGRADE_PLAN_OUTPUT=$(cast call --rpc-url "$RPC_URL" \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "nextUpgrade()(address,uint96)"); then
  echo "ERROR: failed to read nextUpgrade()"
  exit 1
fi

UPGRADE_PLAN=($UPGRADE_PLAN_OUTPUT)
if [ "${#UPGRADE_PLAN[@]}" -lt 2 ]; then
  echo "ERROR: malformed nextUpgrade() output"
  exit 1
fi

OBSERVED_IMPL=${UPGRADE_PLAN[0]}
OBSERVED_AFTER_EPOCH=${UPGRADE_PLAN[1]}

if [[ "$OBSERVED_AFTER_EPOCH" =~ ^0x[0-9a-fA-F]+$ ]]; then
  OBSERVED_AFTER_EPOCH=$((OBSERVED_AFTER_EPOCH))
elif ! [[ "$OBSERVED_AFTER_EPOCH" =~ ^[0-9]+$ ]]; then
  echo "ERROR: invalid observed afterEpoch: $OBSERVED_AFTER_EPOCH"
  exit 1
fi

MIN_AFTER_EPOCH=$((ANNOUNCE_EPOCH + NOTICE_EPOCHS))

echo "Planned implementation: $OBSERVED_IMPL (expected <IMPL>)"
echo "Observed afterEpoch: $OBSERVED_AFTER_EPOCH"

if [ "$(printf '%s' "$OBSERVED_IMPL" | tr '[:upper:]' '[:lower:]')" != \
  "$(printf '%s' "<IMPL>" | tr '[:upper:]' '[:lower:]')" ]; then
  echo "ERROR: announced implementation mismatch"
  exit 1
fi

if [ "$OBSERVED_AFTER_EPOCH" -lt "$MIN_AFTER_EPOCH" ]; then
  echo "ERROR: announcement does not preserve the requested notice window"
  echo "STOP: do not stage or execute the upgrade."
  echo "Generate and execute a replacement announcement, then repeat this verification."
  exit 1
fi

• Confirm the observed implementation and notice-window checks pass
• If the announcement reverted or a check failed, stop the rollout. For the legacy bootstrap, recompute a fresh AFTER_EPOCH, execute a superseding announcement, record the superseded transaction/plan, and repeat verification.
• Do not stage or execute the upgrade transaction until the observed checks pass
• Record OBSERVED_AFTER_EPOCH in the rollout status table
• Wait until the chain reaches OBSERVED_AFTER_EPOCH

Optional parallel work while waiting: deploy and verify the Mainnet implementation, then stage the Mainnet planned-upgrade announcement with its requested notice window. Do not generate, stage, or execute the final Mainnet upgradeToAndCall payload until the Calibration upgrade executes and smoke tests pass.

• Calibration SAFE upgrade transaction payload generated
  • If SAFE/contract-owner helper changes are needed first: tools: support SAFE-owned PDP upgrades

ETH_RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
./tools/upgrade.sh

For legacy one-step upgrades, this prints:

• target
• value
• data

If building the transaction via the Safe UI ABI form:

• method: upgradeToAndCall(address,bytes)
• newImplementation: <IMPL>
• data: 0x8fd3ab80

0x8fd3ab80 is the calldata for migrate().

• Calibration implementation address, verification links, and calldata shared for independent review
• Stage the Calibration SAFE transaction
• Confirm the Calibration execution window
• Confirm nextUpgrade() still matches <IMPL> and OBSERVED_AFTER_EPOCH
• Confirm current epoch is greater than or equal to OBSERVED_AFTER_EPOCH
• Execute the Calibration SAFE upgrade transaction in the Safe UI
• Verify the Calibration proxy implementation slot
• Verify the Calibration proxy is on vX.Y.Z
• Verify nextUpgrade() cleared to the zero address and 0

cast rpc --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  eth_getStorageAt \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc \
  latest | sed 's/"//g' | sed 's/0x000000000000000000000000/0x/'

cast call --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "VERSION()(string)"

cast call --rpc-url https://api.calibration.node.glif.io/rpc/v1 \
  0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C \
  "nextUpgrade()(address,uint96)"

• Run lightweight read-only smoke tests on Calibration

Find a recent live dataset with active pieces:

RPC_URL="https://api.calibration.node.glif.io/rpc/v1"
PROXY="0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C"
NEXT=$(cast call --rpc-url "$RPC_URL" "$PROXY" "getNextDataSetId()(uint256)" | awk '{print $1}')

for id in $(seq $((NEXT-1)) -1 $((NEXT-20))); do
  live=$(cast call --rpc-url "$RPC_URL" "$PROXY" "dataSetLive(uint256)(bool)" "$id" 2>/dev/null || true)
  if [ "$live" = "true" ]; then
    active=$(cast call --rpc-url "$RPC_URL" "$PROXY" "getActivePieceCount(uint256)(uint256)" "$id" 2>/dev/null | awk '{print $1}' || true)
    if [ "$active" != "0" ]; then
      echo "SET_ID=$id ACTIVE=$active"
      break
    fi
  fi
done

Then run:

SET_ID=<live_set_id>
CID=$(cast call --rpc-url "$RPC_URL" "$PROXY" "getPieceCid(uint256,uint256)((bytes))" "$SET_ID" 0 | tr -d '()')

cast call --rpc-url "$RPC_URL" "$PROXY" \
  "getActivePieces(uint256,uint256,uint256)((bytes)[],uint256[],bool)" \
  "$SET_ID" 0 10

cast call --rpc-url "$RPC_URL" "$PROXY" \
  "getActivePiecesByCursor(uint256,uint256,uint256)((bytes)[],uint256[],bool)" \
  "$SET_ID" 0 10

cast call --rpc-url "$RPC_URL" "$PROXY" \
  "findPieceIdsByCid(uint256,(bytes),uint256,uint256)(uint256[])" \
  "$SET_ID" "($CID)" 0 10

Check that:

• the old and new pagination calls agree

• findPieceIdsByCid() returns the expected piece ID(s)

• Verify createDataSet succeeds on Calibration through a PDP integration path

  • Record the data set ID, transaction link, deployed PDP version, and either manual test evidence or a passing dealbot canary graph.

• Record Calibration result in an issue comment; send external update if needed

  • If release notes need to be drafted or refreshed first: docs(changelog): draft vX.Y.Z release notes

• Confirm no blocker remains for Mainnet rollout

Mainnet Rollout

• Calibration rollout completed successfully, including smoke tests
• Send rollout communication if not already covered by the planned-upgrade announcement
  • If release notes need to be drafted or refreshed first: docs(changelog): draft vX.Y.Z release notes
• Deploy the new PDPVerifier implementation to Mainnet
  • Record deployer address, implementation address, and deployment transaction hash

export RPC_URL="https://api.node.glif.io/rpc/v1"
export KEYSTORE="..."
export PASSWORD="..."

forge create \
  --rpc-url "$RPC_URL" \
  --keystore "$KEYSTORE" \
  --password "$PASSWORD" \
  --broadcast \
  --chain-id 314 \
  src/PDPVerifier.sol:PDPVerifier \
  --constructor-args \
  <initializerVersion> \
  150

• Sanity-check VERSION() and immutable values on the Mainnet implementation

cast call --rpc-url "$RPC_URL" <IMPL> "VERSION()(string)"
cast call --rpc-url "$RPC_URL" <IMPL> "getChallengeFinality()(uint256)"

• Verify the Mainnet implementation on Sourcify
• Verify the Mainnet implementation on Blockscout
• Verify the Mainnet implementation on Filfox (optional)

CONSTRUCTOR_ARGS=$(cast abi-encode "constructor(uint64,uint256)" \
  <initializerVersion> \
  150 | sed 's/^0x//')

forge verify-contract \
  --chain 314 \
  --rpc-url "$RPC_URL" \
  --watch \
  --constructor-args "$CONSTRUCTOR_ARGS" \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier

forge verify-contract \
  --chain-id 314 \
  --verifier blockscout \
  --verifier-url "https://filecoin.blockscout.com/api/" \
  --force \
  --skip-is-verified-check \
  --watch \
  --constructor-args "$CONSTRUCTOR_ARGS" \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier

filfox-verifier forge \
  <IMPL> \
  src/PDPVerifier.sol:PDPVerifier \
  --chain 314

• Mainnet planned-upgrade announcement payload generated

Choose exactly one announcement mode below. The default notice window is 2880 Filecoin epochs (~1 day); adjust intentionally if the release needs a longer window.

For the normal delay-based flow, once the live proxy exposes announceUpgradePlan():

NOTICE_EPOCHS=2880
unset AFTER_EPOCH

RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0xBADd0B92C1c71d02E7d520f64c0876538fa2557F" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
UPGRADE_DELAY_EPOCHS="$NOTICE_EPOCHS" \
./tools/announce-planned-upgrade.sh

Temporary bootstrap compatibility: The currently deployed PDPVerifier v3.4.0 implementation does not expose announceUpgradePlan(). Use the following legacy flow only while the live proxy predates that method—normally for the first bootstrap, or for separately documented rollback recovery. Remove this section only after the full removal criteria in #288 are satisfied.

NOTICE_EPOCHS=2880
SAFE_SIGNING_BUFFER_EPOCHS=2880
CURRENT_EPOCH=$(cast block-number --rpc-url "$RPC_URL")
AFTER_EPOCH=$((CURRENT_EPOCH + SAFE_SIGNING_BUFFER_EPOCHS + NOTICE_EPOCHS))
unset UPGRADE_DELAY_EPOCHS

RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0xBADd0B92C1c71d02E7d520f64c0876538fa2557F" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
AFTER_EPOCH="$AFTER_EPOCH" \
./tools/announce-planned-upgrade.sh

If the Safe UI asks whether to use the implementation ABI for the proxy, use the implementation ABI, but keep the transaction target as the proxy.

• Stage the Mainnet planned-upgrade SAFE transaction
• Execute the Mainnet planned-upgrade SAFE transaction
• Record the Mainnet planned-upgrade announcement transaction hash and update the rollout status table

Read the actual plan after the Safe transaction executes. This verifies that the requested notice window starts at execution and catches a legacy announcement that no longer preserves the full notice period.

ANNOUNCE_TX_HASH="<TX_HASH>"
NOTICE_EPOCHS=2880 # Must match the requested notice used above

if ! ANNOUNCE_STATUS=$(cast receipt --rpc-url "$RPC_URL" "$ANNOUNCE_TX_HASH" status); then
  echo "ERROR: failed to read the announcement receipt"
  exit 1
fi

ANNOUNCE_STATUS=${ANNOUNCE_STATUS%% *}
if [ "$ANNOUNCE_STATUS" != "1" ] && [ "$ANNOUNCE_STATUS" != "0x1" ]; then
  echo "ERROR: announcement transaction did not succeed (status $ANNOUNCE_STATUS)"
  exit 1
fi

if ! ANNOUNCE_EPOCH=$(cast receipt --rpc-url "$RPC_URL" "$ANNOUNCE_TX_HASH" blockNumber); then
  echo "ERROR: failed to read the announcement epoch"
  exit 1
fi

if [[ "$ANNOUNCE_EPOCH" =~ ^0x[0-9a-fA-F]+$ ]]; then
  ANNOUNCE_EPOCH=$((ANNOUNCE_EPOCH))
elif ! [[ "$ANNOUNCE_EPOCH" =~ ^[0-9]+$ ]]; then
  echo "ERROR: invalid announcement epoch: $ANNOUNCE_EPOCH"
  exit 1
fi

if ! UPGRADE_PLAN_OUTPUT=$(cast call --rpc-url "$RPC_URL" \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "nextUpgrade()(address,uint96)"); then
  echo "ERROR: failed to read nextUpgrade()"
  exit 1
fi

UPGRADE_PLAN=($UPGRADE_PLAN_OUTPUT)
if [ "${#UPGRADE_PLAN[@]}" -lt 2 ]; then
  echo "ERROR: malformed nextUpgrade() output"
  exit 1
fi

OBSERVED_IMPL=${UPGRADE_PLAN[0]}
OBSERVED_AFTER_EPOCH=${UPGRADE_PLAN[1]}

if [[ "$OBSERVED_AFTER_EPOCH" =~ ^0x[0-9a-fA-F]+$ ]]; then
  OBSERVED_AFTER_EPOCH=$((OBSERVED_AFTER_EPOCH))
elif ! [[ "$OBSERVED_AFTER_EPOCH" =~ ^[0-9]+$ ]]; then
  echo "ERROR: invalid observed afterEpoch: $OBSERVED_AFTER_EPOCH"
  exit 1
fi

MIN_AFTER_EPOCH=$((ANNOUNCE_EPOCH + NOTICE_EPOCHS))

echo "Planned implementation: $OBSERVED_IMPL (expected <IMPL>)"
echo "Observed afterEpoch: $OBSERVED_AFTER_EPOCH"

if [ "$(printf '%s' "$OBSERVED_IMPL" | tr '[:upper:]' '[:lower:]')" != \
  "$(printf '%s' "<IMPL>" | tr '[:upper:]' '[:lower:]')" ]; then
  echo "ERROR: announced implementation mismatch"
  exit 1
fi

if [ "$OBSERVED_AFTER_EPOCH" -lt "$MIN_AFTER_EPOCH" ]; then
  echo "ERROR: announcement does not preserve the requested notice window"
  echo "STOP: do not stage or execute the upgrade."
  echo "Generate and execute a replacement announcement, then repeat this verification."
  exit 1
fi

• Confirm the observed implementation and notice-window checks pass

• If the announcement reverted or a check failed, stop the rollout. For the legacy bootstrap, recompute a fresh AFTER_EPOCH, execute a superseding announcement, record the superseded transaction/plan, and repeat verification.

• Do not stage or execute the upgrade transaction until the observed checks pass

• Record OBSERVED_AFTER_EPOCH in the rollout status table

• Wait until the chain reaches OBSERVED_AFTER_EPOCH

• Confirm Calibration upgrade and smoke tests completed successfully before proceeding to final Mainnet upgrade execution

• Mainnet SAFE upgrade transaction payload generated

  • If SAFE/contract-owner helper changes are needed first: tools: support SAFE-owned PDP upgrades

ETH_RPC_URL="$RPC_URL" \
SAFE_ADDRESS="0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5" \
PDP_VERIFIER_PROXY_ADDRESS="0xBADd0B92C1c71d02E7d520f64c0876538fa2557F" \
NEW_PDP_VERIFIER_IMPLEMENTATION_ADDRESS="<IMPL>" \
./tools/upgrade.sh

If building the Safe transaction with ABI inputs:

• method: upgradeToAndCall(address,bytes)

• newImplementation: <IMPL>

• data: 0x8fd3ab80

• Mainnet implementation address, verification links, calldata, and rollout notes shared for independent review

• Stage the Mainnet SAFE transaction

• Collect SAFE signer approvals

• Confirm the Mainnet execution date/time

• Confirm nextUpgrade() still matches <IMPL> and OBSERVED_AFTER_EPOCH

• Confirm current epoch is greater than or equal to OBSERVED_AFTER_EPOCH

• Execute the Mainnet SAFE upgrade transaction

• Verify the Mainnet proxy implementation slot

• Verify the Mainnet proxy is on vX.Y.Z

• Verify nextUpgrade() cleared to the zero address and 0

cast rpc --rpc-url https://api.node.glif.io/rpc/v1 \
  eth_getStorageAt \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc \
  latest | sed 's/"//g' | sed 's/0x000000000000000000000000/0x/'

cast call --rpc-url https://api.node.glif.io/rpc/v1 \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "VERSION()(string)"

cast call --rpc-url https://api.node.glif.io/rpc/v1 \
  0xBADd0B92C1c71d02E7d520f64c0876538fa2557F \
  "nextUpgrade()(address,uint96)"

• Verify createDataSet succeeds on Mainnet through a PDP integration path

  • Record the data set ID, transaction link, deployed PDP version, and either manual test evidence or a passing dealbot canary graph.

• Publish completion/update communication

Release Closeout

• Update CHANGELOG.md release date, deployed addresses, verification links, and deployment transactions
• Final release-note PR merged to main
  • Suggested PR title: docs(changelog): finalize vX.Y.Z release notes
• Tag vX.Y.Z
  • The tag may point at a changelog-only commit after deployment.
  • Record the implementation deploy commit separately if it differs from the tag commit.

git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z

• Prefer Blockscout links in the deployed-address section because they give a better verification view than Filfox.
• Sync PDPVerifier source, ABI, and deployments in filecoin-services
  • Pin service_contracts/lib/pdp to the exact PDP release tag.
  • Regenerate/check the PDPVerifier ABI if needed.
  • Update implementation addresses in deployment references.
  • Update proxy addresses only if a proxy address actually changed.
• Create follow-up issue in fwss-subgraph
• Close this rollout issue
  • If the issue template needs improvement afterward: docs: update PDPVerifier upgrade issue template

Deployment / Verification Details

Fill these in as comments or update them here once known.

• Deploy commit: cc3f5eaffee7df80471b671a4e35a42b000685b8
• Release tag: TBD

Calibration

• Proxy address: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
• Previous implementation address: 0xd6b09b0f6D3C42B26a246E141ec701a20Dde2fA61
• New implementation address: 0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1
• Deployment transaction hash: 0x824aec5fd5694c7894985cea1b05545a01d8e09cf114300cf882c3ca79a3a27d
• Planned-upgrade announcement transaction hash: TBD
• Constructor values:
  • initializerVersion: 4
  • challengeFinality: 10
• Verification links:
  • Sourcify: https://sourcify.dev/server/v2/verify/1f5d922b-56e8-4661-a0be-b4a776d7f061
  • Blockscout: https://filecoin-testnet.blockscout.com/address/0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1?tab=contract
  • Filfox: unavailable; verification request returned HTTP 500 on 2026-08-21
• SAFE transaction link:
• SAFE execution transaction hash:
• Smoke-test commands/results:

Mainnet

• Proxy address: 0xBADd0B92C1c71d02E7d520f64c0876538fa2557F

• Previous implementation address: 0xb41A97FEDD2D9497C639A643ec75E56CbCeDe8BA

• New implementation address: 0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1

• Deployment transaction hash: 0xf39ea3a831d2b60035fbe894157f0ce78e0b13fff1ffed2e6cf77d462f0292cc

• Planned-upgrade announcement transaction hash: TBD

• Constructor values:

  • initializerVersion: 4
  • challengeFinality: 150

• Verification links:

  • Sourcify: https://sourcify.dev/server/v2/verify/49d5db23-f920-46aa-a904-5f79f6cb2fcb
  • Blockscout: https://filecoin.blockscout.com/address/0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1?tab=contract
  • Filfox:

• SAFE transaction link:

• SAFE execution transaction hash:

• Upgrade communication links:

• Post-release follow-up links:

  • filecoin-services PR:
  • fwss-subgraph issue:

Suggested Comment Cadence

Recommended issue comments to post as the rollout progresses:

1. Deploy commit and Calibration constructor values
2. Calibration implementation deployment output
3. Calibration verification links and SAFE transaction review request
4. Calibration execution transaction link and smoke-test results
5. Mainnet implementation deployment output
6. Mainnet verification links and SAFE transaction review request
7. Scheduled Mainnet execution window
8. Mainnet execution transaction link and post-upgrade verification
9. Release-closeout links (CHANGELOG, tag, filecoin-services, fwss-subgraph)

[Kubuxu]

Release preparation checkpoint:

• PDP technical owner / go-no-go owner: @Kubuxu
• Release-prep PR: docs(changelog): draft v3.5.0 release notes and version bump #306
• Candidate version: 3.5.0
• forge test: 232 passed, 0 failed
• Calibration proxy: owner 0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5, live VERSION() = 3.4.0, initializer counter 3, nextUpgrade = (0x0, 0)
• Mainnet proxy: owner 0x3569b2600877a9F42d9Ebdd205386F3F3788F3E5, live VERSION() = 3.4.0, initializer counter 3, nextUpgrade = (0x0, 0)
• Candidate constructor values: initializer version 4 on both networks; challenge finality 10 on Calibration and 150 on Mainnet
• Rollback posture: unsafe after compact writes. Once v3.5 creates compact data sets, v3.4 cannot interpret that representation; mitigation should be a forward fix. A rollback before any compact writes is only a narrow emergency option and must be reassessed against observed state.
• FOC devnet validation: not completed; Calibration remains blocked on linked evidence.

[Kubuxu]

Release gate update:

• Release-prep PR docs(changelog): draft v3.5.0 release notes and version bump #306 was approved and merged.
• main is clean and matches origin/main.
• No pull requests are currently open.
• Frozen v3.5.0 deployment commit: cc3f5eaffee7df80471b671a4e35a42b000685b8
• PDPVerifier.VERSION at that commit is 3.5.0.

Remaining pre-Calibration gate: run the target commit through the FOC devnet upgrade path and link evidence that post-upgrade PDP state is valid. After that passes, deploy the Calibration implementation with constructor args (4, 10).