Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test: Sepolia task to transfer owner of ProtocolVersions #554

Open
Tracked by #396
blmalone opened this issue Feb 5, 2025 · 5 comments
Open
Tracked by #396

Test: Sepolia task to transfer owner of ProtocolVersions #554

blmalone opened this issue Feb 5, 2025 · 5 comments

Comments

@blmalone
Copy link
Contributor

blmalone commented Feb 5, 2025

0xfd1D2e729aE8eEe2E146c033bf4400fE75284301 is the Sepolia ProtocolVersions owner.

On mainnet, the owner of ProtocolVersions is the Foundation Upgrade Safe (FUS) - 0x847B5c174615B1B7fDF770882256e2D3E95b9D92

We should create a template in superchain-ops 2.0 that transfers the ProtocolVersions owner. Then create a task from this template on sepolia that transfers the owner to the sepolia FUS.

@mds1
Copy link
Contributor

mds1 commented Feb 5, 2025

I would probably create a general ownership transfer template where the inputs are a the chain, contract name, and the new owner address, where the new owner address is a named string like "Foundation Upgrades Safe" which the template maps to the correct address

@blmalone
Copy link
Contributor Author

Make sense, we've got this implemented here: #595

@blmalone
Copy link
Contributor Author

Doing deputy pause module first, this can come after

@ElliotFriedman
Copy link
Contributor

Where can we find the ProtocolVersions contract in the superchain ops or superchain registry repo?

Searching this address 0x8062AbC286f5e7D9428a0Ccb9AbD71e50d93b935 in the addresses.json file in superchain-registry shows no results.

Looking in the AddressRegistry contract in superchain ops doesn't show anywhere an address named or close to ProtocolVersions is stored.

Should this be another address that is added to the hardcoded addresses.toml file?

Or, should we modify AddressRegistry contract to fetch this onchain from the OPCM?

@ElliotFriedman
Copy link
Contributor

The most generic version of the TransferOwnerTemplate would accept a toml configuration file with values for both the new owner and contract whose ownership is being transferred.

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

No branches or pull requests

3 participants