Introduction of CREATE3 for Deployment to Deterministic Addresses to Resolve Cyclical Dependencies #104
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.
This PR introduces an enhancement to our deployment process with the introduction of
CREATE3
. Here's a brief overview of the changes:Introduction of
CREATE3
: We have introducedCREATE3
, a feature that allows deployment to a deterministic address using only a salt. This is a major advancement in resolving cyclical dependencies within our system.Immutable Addresses for Dependencies: The introduction of
CREATE3
allows us to store dependencies as immutable addresses. This eliminates the need for governed functions to set these addresses, further simplifying our protocol.Simplified Protocol Post Configurations: No need to configure dependencies' addresses through the governance process after deployment.