feat(devnet): fix devent after merge 1.3.0 #123
Merged
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
After the upstream merge of v1.3.0, my PR (#73) for starting devnet locally no longer works. We need to be able to start devnet locally, so I made fixes based on the code from upstream merge v1.3.0.
Rationale
The biggest change is the process of contract deployment, where the upstream code uses Foundry instead of Hardhat. I have done a lot of learning and adaptation work on this. I have adapted it to work on the BSC network.
Example
The method used by devnet is the same as before, now in addition to using
make devnet-up-deploy
, you can also usemake devnet-up
to start devnet.Changes
Notable changes: