Right now the steps are:
- Run deployment script
- Creates custom
env/latest/<chainid>-latest.json file (through JsonRegistry)
- This step stores the contract addresses and version per contract
- Creates the default
broadcast/<script>.s.sol/<chainid>/latest.json
- Run
update_network_config.py
- Reads
env/latest/<chainid>-latest.json
- Reads
broadcast/<script>.s.sol/<chainid>/latest.json
- Populates
env/<netwok>.json file
We don't need env/latest/<chainid>-latest.json and JsonRegistry. We can get the contract addresses from the broadcast file, and we can just write the versioning in the own broadcast/<script>.s.sol/<chainid>/latest.json after stopBroadcast(). With this, we have just one file with all the deployment information. update_network_config.py can later read one file.
Benefits:
- Easier to infer from where the values come.
- Only one single file that we can share by just copying the file after a new deployment.
- Simplify deployment scripts
Right now the steps are:
env/latest/<chainid>-latest.jsonfile (through JsonRegistry)broadcast/<script>.s.sol/<chainid>/latest.jsonupdate_network_config.pyenv/latest/<chainid>-latest.jsonbroadcast/<script>.s.sol/<chainid>/latest.jsonenv/<netwok>.jsonfileWe don't need
env/latest/<chainid>-latest.jsonandJsonRegistry. We can get the contract addresses from the broadcast file, and we can just write the versioning in the ownbroadcast/<script>.s.sol/<chainid>/latest.jsonafterstopBroadcast(). With this, we have just one file with all the deployment information.update_network_config.pycan later read one file.Benefits: