Skip to content

Conversation

@alysiahuggins
Copy link
Contributor

@alysiahuggins alysiahuggins commented Dec 18, 2025

Closes #<ISSUE_NUMBER>

This PR:

  • Adds a patch upgrade for the FeeContract (v1.0.1)
  • Forces fresh implementation deployment by clearing the contracts cache when upgrading to a patch
  • Adds tests covering fee contract and light client upgrade behavior

This PR does not:

Key places to review:

  • FeeContract.sol version bump (getVersion)
  • upgrade_fee_v1 and multisig upgrade helpers
  • Cache-clearing logic before redeploying implementations
  • New upgrade and redeploy tests


// Verify current version before upgrading
let curr_version = proxy.getVersion().call().await?;
if curr_version.majorVersion != 1 {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

kept this simple to allow for patch upgrades within v1


// Remove old implementation from cache so we deploy a new one
contracts.0.remove(&Contract::FeeContract);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we can allow an explicit flag e.g. --patch-upgrade to allow for redeployment of the same contract and upgrade, in order to do a patch upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants