[SC-1177] Deploy with create3 and save deployment #147
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.
Static Code Analysis (readability, compactness):
Added a method to save a deployment object after deploying via create3, as
hardhat-deploy
does not support this and contracts deployed via create3 remain without deployments or with outdated ones. This method allows saving up-to-date deployment information.Dynamic Code Analysis (external APIs, interaction flows):
The new method is similar to the
deployAndGetContract
method and is intended for deploying contracts and verifying code, but using for deploy with create3. It provides similar interaction flows and interacts with external APIs in a comparable manner.Efficiency (gas costs, computational complexity, memory requirements):
Efficiency has not been measured as this is an auxiliary JS utility without EVM optimizations. The focus was on functionality and ease of use.
Opinion, trade-offs and other thoughts (optional):