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

Set ownership of proxy contracts on deployment #210

Closed
wants to merge 13 commits into from

Conversation

rkachowski
Copy link

@rkachowski rkachowski commented Aug 6, 2024

Sets the ownership of two proxy contracts (SystemConfigProxy and ProtocolVersionsProxy) to the SystemOwnerSafe contract during deployment if the correct config var is set. This removes the deployment account from directly owning L1 contracts, and instead indirectly owns them through multisig membership.

closes https://github.com/celo-org/celo-blockchain-planning/issues/518

@codecov-commenter
Copy link

codecov-commenter commented Aug 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.32%. Comparing base (600324b) to head (cec1f8b).

Additional details and impacted files
@@           Coverage Diff           @@
##            celo7     #210   +/-   ##
=======================================
  Coverage   61.32%   61.32%           
=======================================
  Files          20       20           
  Lines        1753     1753           
  Branches       71       71           
=======================================
  Hits         1075     1075           
  Misses        646      646           
  Partials       32       32           
Flag Coverage Δ
cannon-go-tests 81.03% <ø> (ø)
chain-mon-tests 27.14% <ø> (ø)
sdk-tests 16.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@rkachowski rkachowski marked this pull request as ready for review August 14, 2024 07:53
@rkachowski rkachowski assigned rkachowski and unassigned rkachowski Aug 21, 2024
@palango
Copy link

palango commented Aug 22, 2024

I miss some context here. Do you know why this is done the way it is? For me it seems like the safe is the "better" owner. Can we we maybe upstream this?

@rkachowski
Copy link
Author

hey @palango , I don't know why it's done this way. I would also agree that the safe is the better owner, especially in the case of Celo which doesn't have a well defined security council or ownership policy yet. I don't see why it couldn't be upstreamed

@palango
Copy link

palango commented Aug 30, 2024

@pahor167 @martinvol I'd like to get your input here as well.

@rkachowski rkachowski marked this pull request as draft September 18, 2024 16:26
@rkachowski rkachowski changed the base branch from celo7 to celo8 September 18, 2024 16:53
Copy link

github-actions bot commented Oct 3, 2024

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Oct 3, 2024
@github-actions github-actions bot closed this Oct 8, 2024
@@ -72,7 +72,6 @@ library ChainAssertions {
ResourceMetering.ResourceConfig memory resourceConfig = config.resourceConfig();

if (_isProxy) {
require(config.owner() == _cfg.finalSystemOwner());
require(config.basefeeScalar() == _cfg.basefeeScalar());
Copy link

Choose a reason for hiding this comment

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

Rather then deleting this check - can we update it so it checks the owner based on config ?

/// This is expected to be used in conjusting with deployERC1967ProxyWithOwner after setup actions
/// have been performed on the proxy.
/// @param _name The name of the proxy to transfer ownership of.
/// @param _name The name of the proxy to transfer admin of.
Copy link

Choose a reason for hiding this comment

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

Any reason why not to also change owner of InitializeDataAvailabilityChallenge ?

Copy link
Author

Choose a reason for hiding this comment

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

iirc, this function actually changed the admin - and not owner (as described in the comment) - and was updated for the sake of clarity.

@lvpeschke lvpeschke reopened this Oct 9, 2024
@lvpeschke lvpeschke removed the Stale label Oct 9, 2024
@pahor167 pahor167 changed the base branch from celo8 to celo9 October 10, 2024 12:39
@pahor167 pahor167 changed the base branch from celo9 to celo8 October 10, 2024 12:39
@pahor167
Copy link

Closed in favor of #255

@pahor167 pahor167 closed this Oct 10, 2024
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.

5 participants