From 9bb2f19bd121361d69b5fd88741314d59dba5056 Mon Sep 17 00:00:00 2001 From: Goran Vladika Date: Tue, 7 May 2024 18:18:37 +0200 Subject: [PATCH] Update docs --- docs/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment.md b/docs/deployment.md index e060c993b..1b9dbaff3 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -108,6 +108,6 @@ Script is applicable for the verifying source code on the Blockscout explorer. S 1. Update `hardhat.config.ts`. Find `orbit` field under `networks` and `customChains` and replace values with correct RPC and blockscout endpoints. 2. `yarn install && yarn build` -3. Set up `.env` - provide `PARENT_RPC`, `TOKEN_BRIDGE_CREATOR` (address of token bridge creator on parent chain) and `INBOX_ADDRESS`. +3. Set up `.env` - provide `BASECHAIN_RPC`, `L1_TOKEN_BRIDGE_CREATOR` (address of token bridge creator on parent chain) and `INBOX_ADDRESS`. 4. Optionally provide the `DEPLOYER_KEY`. That's the private key of any funded address on the Orbit chain. It is required if you want to get `UpgradeExecutor` and `aeWETH` verified. Due to specifics of cross-chain deployment used by token bridge creator, the only way to get `UpgradeExecutor` and `aeWETH` verified is to deploy dummy instances on the Orbit chain and verify them. That way the original instances will get automatically verified because of the deployed bytecode match. If `DEPLOYER_KEY` is not provided, this step will be skipped. 5. Run script as following: `yarn run blockscout:verify --network orbit` \ No newline at end of file