Skip to content

Conversation

@rjan90
Copy link
Collaborator

@rjan90 rjan90 commented Sep 15, 2025

Towards: #212

Document the FWSS contract upgrade dependencies

chore: create release issue template
@FilOzzy FilOzzy added this to FS Sep 15, 2025
@github-project-automation github-project-automation bot moved this to 📌 Triage in FS Sep 15, 2025
@rjan90 rjan90 moved this from 📌 Triage to ⌨️ In Progress in FS Sep 15, 2025
@rjan90 rjan90 self-assigned this Sep 15, 2025
chore: contract upgrade dependencies document
@rjan90 rjan90 changed the title chore: create release issue template chore: FWSS Contract Upgrade Dependencies Document Oct 1, 2025
rjan90 added 2 commits October 1, 2025 12:52
chore: update dependecies document
chore: update file name
- [ ] Create tag/release manually on GitHub UI

##### Upgrade PDP Implementation Contract in FWSS:
- [ ] Checkout the desired PDP tag you want to upgrade to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to say something about going into the pdp submodule in FWSS?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not clear why we are doing this work from the submodule in FWSS. Why don't we do it PDP repo directly? Are we doing it to just to be certain that we're deploying the actual version in the FWS submodule for pdp?

export IMPLEMENTATION_PATH="src/PDPVerifier.sol:PDPVerifier" # If executing from /pdp
```
- [ ] Use the `upgrade-contract.sh` script to upgrade the contract
- [ ] Verify upgrade on Calibnet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain how?

```
- [ ] Use the `upgrade-contract.sh` script to upgrade the contract
- [ ] Verify upgrade on Calibnet

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there followup steps of updating the contract address in the changelog (although I wish we didn't have this manual step, but I understand we're just documenting what happens now).

```
- [ ] Use the `upgrade-contract.sh` script to upgrade the contract
- [ ] Verify upgrade on Calibnet

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to cover the calibration vs. mainnet case? Do we expect to do both?

@BigLep
Copy link
Contributor

BigLep commented Oct 7, 2025

Reminder to capture steps/deatils about verifying contracts.... Example: https://filecoinproject.slack.com/archives/C07CGTXHHT4/p1759839263065899

@BigLep
Copy link
Contributor

BigLep commented Oct 7, 2025

Reminder to capture steps/deatils about verifying contracts.... Example: https://filecoinproject.slack.com/archives/C07CGTXHHT4/p1759839263065899

My bad. There is a detailed log of steps being taken in #254 which I assume will get generalized and recorded here.

@rjan90
Copy link
Collaborator Author

rjan90 commented Oct 12, 2025

Some of the env-vars are changing in this PR: #279 (review)

@BigLep BigLep moved this from ⌨️ In Progress to 🐱 Todo in FS Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🐱 Todo

Development

Successfully merging this pull request may close these issues.

3 participants