fix: remove proxy implementation for OPCM contract #13531
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request removes the proxy implementation for the
OPContractsManager
(OPCM) contract in the Bedrock deployment script. The changes replace the reference to a previously deployedOPContractsManager
with the creation of a new instance of the contract directly within the deployment process.Tests
No specific tests were added for this change as it directly updates the deployment script. However, deployment processes should be revalidated to ensure that the removal of the proxy does not introduce regressions or disrupt existing deployment workflows.
Additional Context
OPContractsManager
is deployed afresh with each invocation of the script, aligning with deployment requirements for Bedrock.Metadata
Notes for Maintainers
Allow edits by maintainers: ✅
This change follows the contributing guidelines and aims to streamline the Bedrock contract deployment process.