op-chain-ops: create tool to determine which contract versions are deployed for each chain (#8859)
* op-chain-ops: create op-version-check forked from op-upgrade * op-version-check: drop logic for upgrading contracts * op-version-check: add logic for outputting contract versions * op-version-check: improve support for checking multiple chains * op-version-check: replace legacy upgrade references * op-chain-ops: create README * op-version-check: improve README * op-version-check: drop unnecessary deploy-config flag * op-version-check: create op-version-check in Makefile * op-version-check: add usage section to README * op-chain-ops: add op-version-check to README * op-version-check: fix path in README * op-version-check: remove unused function toDeployConfigName * op-version-check: drop capitalization on error strings * op-node: capitalize writeJSONFile function this makes it accessible when op-node/cmd/genesis is imported as a package * op-chain-ops: use op-node/cmd/genesis for writeJSON * op-chain-ops: set name op_node_genesis for import * op-chain-ops: use op-node WriteJSONFile in op-upgrade * op-chains-ops: move to toSuperchainName to upgrades package * op-chain-ops: output all contracts for op-version-check addresses https://github.com/ethereum-optimism/optimism/pull/8859#issuecomment-1881663953 * op-chain-ops: add logging if chain ID is skipped by op-version-check * op-service: create jsonutil/write * op-chain-ops use jsonutil in op-upgrade, op-version-check * op-chain-ops: pass RPC URLs as flags in op-version-check * op-chain-ops: refactor of op-version-check * op-chain-ops: refactor of op-version-check * op-chain-ops: add more logging for op-version-check * op-chain-ops: add more logging for op-version-check
Showing
op-service/jsonutil/write.go
0 → 100644
Please register or sign in to comment