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

feat(deploy): deploy implementations before proxies #12114

Merged
merged 3 commits into from
Sep 26, 2024
Merged

Conversation

maurelian
Copy link
Contributor

This change prepares for the OPCM integration by deploying the implementations before the proxies.
intializeImplementations() was renamed to initializeProxies() which is more accurate.

Also the ASR's implementation was unnecessarily initialized with a proxy address for a constructor
argument.

@maurelian maurelian marked this pull request as ready for review September 25, 2024 16:58
@maurelian maurelian requested a review from a team as a code owner September 25, 2024 16:58
@maurelian maurelian requested review from mbaxter and removed request for a team September 25, 2024 16:58
Copy link
Contributor Author

Merge activity

  • Sep 25, 7:45 PM EDT: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..

This change prepares for the OPCM integration by deploying the implementations before the proxies.
`intializeImplementations()` was renamed to `initializeProxies()` which is more accurate.

Also the ASR's implementation was unnecessarily initialized with a proxy address for a constructor
argument.
It must be deployed per chain because it is not MCP ready.
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