Base deployment #94
Base deployment #94
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Approving, but since this has been more difficult than it should have been (see #93 and note that there's no new entry in the broadcast folder) I expect that the PR description will be updated to include the steps that were taken to achieve deterministic deployments and contract verification.
I confirmed that:
- the contracts exist on Base at the given addresses and have verified code
- the contracts were created with
CREATE2 - the addresses are the same as those in other networks (meaning that there's no need to actually check that the verified contract code matches that on other networks)
| - Some contracts will auto-verify themselves (rare), because they exist in other networks | ||
| - Some contracts can be verified with forge e.i. `forge verify-contract --etherscan-api-key $BASESCAN_API_KEY --rpc-url $RPC_URL 0x2f55e8b20D0B9FEFA187AA7d00B6Cbe563605bF5 lib/safe/contracts/handler/ExtensibleFallbackHandler.sol:ExtensibleFallbackHandler` | ||
| - For the contracts which can't be verified neither way, the standard json input has to be generated with forge: `forge verify-contract --verifier sourcify --show-standard-json-input --etherscan-api-key $BASESCAN_API_KEY --rpc-url $RPC_URL 0xfdaFc9d1902f4e0b84f65F49f244b32b31013b74 src/ComposableCoW.sol:ComposableCoW > ComposableCoW.json`, and submit the json to the corresponding block explorer | ||
|
|
There was a problem hiding this comment.
For this specific repository, probably dev/, since it already has the script used to generate networks.json and it's somewhat related.
There was a problem hiding this comment.
For this specific repository, probably dev/, since it already has the script used to generate networks.json and it's somewhat related.
Description
Base deployment contracts.