Merge pull request #9 from zerodevapp/feat/verify

feat: add contract verification

.env.example

@@ -16,8 +16,29 @@ MAINNET_PROJECT_ID="YOUR_MAINNET_PROJECT_ID"
 SEPOILA_PROJECT_ID="YOUR_SEPOILA_PROJECT_ID"
 OPTIMISM_PROJECT_ID="YOUR_OPTIMISM_PROJECT_ID"
 OPTIMISM_SEPOLIA_PROJECT_ID="YOUR_OPTIMISM_SEPOLIA_PROJECT_ID"
+OPBNB_PROJECT_ID="YOUR_OPBNB_PROJECT_ID"
 POLYGON_PROJECT_ID="YOUR_POLYGON_PROJECT_ID"
 POLYGON_MUMBAI_PROJECT_ID="YOUR_POLYGON_MUMBAI_PROJECT_ID"
 LINEA_PROJECT_ID="YOUR_LINEA_PROJECT_ID"
 LINEA_TESTNET_PROJECT_ID="YOUR_LINEA_TESTNET_PROJECT_ID"
 ASTAR_ZKATANA_PROJECT_ID="YOUR_ASTAR_ZKATANA_PROJECT_ID"
+
+# Set up etherscan API key for each network you want to verify on
+
+ARBITRUM_ETHERSCAN_API_KEY=""
+ARBITRUM_SEPOLIA_ETHERSCAN_API_KEY=""
+AVALANCHE_ETHERSCAN_API_KEY=""
+AVALANCHE_FUJI_ETHERSCAN_API_KEY=""
+BASE_ETHERSCAN_API_KEY=""
+BASE_SEPOLIA_ETHERSCAN_API_KEY=""
+BSC_ETHERSCAN_API_KEY=""
+MAINNET_ETHERSCAN_API_KEY=""
+SEPOILA_ETHERSCAN_API_KEY=""
+OPTIMISM_ETHERSCAN_API_KEY=""
+OPTIMISM_SEPOLIA_ETHERSCAN_API_KEY=""
+OPBNB_ETHERSCAN_API_KEY=""
+POLYGON_ETHERSCAN_API_KEY=""
+POLYGON_MUMBAI_ETHERSCAN_API_KEY=""
+LINEA_ETHERSCAN_API_KEY=""
+LINEA_TESTNET_ETHERSCAN_API_KEY=""
+ASTAR_ZKATANA_ETHERSCAN_API_KEY=""

.gitignore

@@ -3,4 +3,10 @@ node_modules
 dist
 bytecode
 session-key.txt
-log
+log
+
+# for testing contract verification
+foundry.toml
+out/
+cache/
+src/HelloWorld.sol

README.md

@@ -8,7 +8,7 @@ Orchestra is a CLI for deterministically deploying contracts to multiple chains,
 2. Create a `.env` file based on `.env.example`
    - You can acquire the project IDs from [the ZeroDev dashboard](https://dashboard.zerodev.app/)
 3. Test the installation by running `zerodev -h`
- 
+
 ## Usage
 
 ### Deploying a Contract
@@ -57,6 +57,7 @@ All commands should be prefixed with `zerodev`
   - `-m, --mainnet-all`: deploy to all mainnets
   - `-c, --chains [CHAINS]`: list of chains to deploy, with `all` selected by default
   - `-e, --expected-address <address>`: expected address to confirm
+  - `-v, --verify <CONTRACT_NAME>`: contract name to be verified
 - `check-deployment [options]`: Check if the contract has been deployed on the specified chains
   - `-f, --file <path-to-bytecode>`: file path of bytecode used for deployment
   - `-b, --bytecode <bytecode>`: bytecode to deploy, should have constructor arguments encoded
@@ -75,4 +76,4 @@ Orchestra supports all network supported by ZeroDev. Check details [here](https:
 
 ## Help Wanted
 
-- Orchestra can in principle run on any AA infra, but since ERC-4337 paymasters tend to be incompatible across vendors, currently Orchestra only support ZeroDev paymasters.  We welcome PRs to add support for other AA infra providers.  To do so, you would first add support for other infra providers to [Kernel.js](https://github.com/zerodevapp/kernel.js), which Orchestra is built on top of.  Feel free to [reach out to us](https://discord.gg/KS9MRaTSjx) if you need help with this task.
+- Orchestra can in principle run on any AA infra, but since ERC-4337 paymasters tend to be incompatible across vendors, currently Orchestra only support ZeroDev paymasters. We welcome PRs to add support for other AA infra providers. To do so, you would first add support for other infra providers to [Kernel.js](https://github.com/zerodevapp/kernel.js), which Orchestra is built on top of. Feel free to [reach out to us](https://discord.gg/KS9MRaTSjx) if you need help with this task.