feat: allow for devnet deployments against already instantiated devnet environments #302
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.
Motivation:
As a devkit user, I want to use an already running anvil/hardhat environment to deploy my devnet against so that I can take advantage of third-party services (such as buildbear.io)
Modifications:
--skip-forking) todevkit avs devnet startto skip starting local anvil forksaddChainIDsToWhitelistto correctly wait for receiptsPrivateKeyto assign asTableUpdaterto avoidKeyRegistrarconflictsResult:
Testing: