forked from sphinx-labs/sphinx
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(core): update diff to include constructor arg variables and post…
…-deployment actions
- Loading branch information
1 parent
5de8fa5
commit 2913976
Showing
16 changed files
with
999 additions
and
265 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
'@sphinx-labs/core': minor | ||
--- | ||
|
||
Update diff to include constructor arg variables and post-deployment actions |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,9 @@ | ||
# FAQ | ||
|
||
### How do I deploy a contract when another contract already exists at its `CREATE3` address? | ||
### Why is Sphinx skipping a contract deployment or function call? | ||
|
||
Sphinx detects this situation and outputs the following message in the diff: | ||
```bash | ||
Skipping: | ||
Reason: Contract already deployed at the Create3 address. | ||
Contract(s): | ||
... | ||
``` | ||
With Sphinx, contract deployments and function calls are idempotent. This means that they'll only be executed once per chain, even if you re-deploy your config file. | ||
|
||
To deploy a new contract, you must change its `CREATE3` address. There are two ways to do this: | ||
If you'd like to re-deploy a contract instead of skipping it, you must change its `CREATE3` address. There are two ways to do this: | ||
1. (Recommended): Add a `salt` to the contract definition in the Sphinx config file. For more info on the `salt`, see [here](https://github.com/sphinx-labs/sphinx/blob/develop/docs/config-file.md#contract-definitions). | ||
2. Change the reference name of the contract. For more info on reference names, see [here](https://github.com/sphinx-labs/sphinx/blob/develop/docs/config-file.md#reference-names). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.