Add setup function and verification

Author: lsgunnlsgunn

README.md

@@ -161,6 +161,21 @@ Chainweb-EVM-chainid = Foundry-chain-id + chainwebChainIdOffset
 **Important**: The  `chainweb.config.json` configuration file is only used when running scripts with `ChainwebScript`. 
 When running tests with `ChainwebTest`, the configuration parameters are passed directly to the constructor and the configuration file is ignored.
 
+## Setup function
+
+To add custom setup logic to tests or scripts, you should use the optional `userSetUp` method instead of the default Foundry `setUp` method. 
+
+For example:
+
+```bash
+contract CounterTest is ChainwebTest(2, 0) {
+    function userSetUp() public override {
+        // Custom setup can be done here if needed
+        console.log("Setting up your test here");
+    }
+}
+```
+
 ## Tests
 
 To write tests that run on Chainweb EVM and support the multi-chain network, you should extend the `ChainwebTest` contract that's defined in the `lib/foundry-chainweb/src/Chainweb.sol` file instead of using the default Foundry `Test` base contract.
@@ -437,3 +452,51 @@ Sensitive details saved to: /Users/pistolas/foundry-chainweb/examples/Counter/ca
 In the sample output for deploying the contract on multiple chains, you'll notice that the Foundry chain identifiers are computed using the default value from the `foundry.toml` file (`31337`) as a base value and incremented for each Chainweb EVM chain.
 As a result of the computation, Chainweb EVM chain 20 (index 0) maps to the Foundry chain identifier 31337, Chainweb EVM chain 21 (index 1) maps to the Foundry chain identifier 31338, and so on.
 
+## Verifying contracts
+
+You can verify contracts that run on Chainwebd EVM by running the standard `forge verify-contract` command. 
+The following example demonstrates verifying a contract like `Counter.sol` that has no constructor arguments:
+
+```bash
+forge verify-contract \
+  --chain 5920 \
+  --num-of-optimizations 200 \
+  --watch \
+  --verifier blockscout \
+  --verifier-url https://chain-20.evm-testnet-blockscout.chainweb.com/api/ \
+  --verifier-api-version v2 \
+  --compiler-version v0.8.28 \
+  0x3ee2edc5b2967093bf9b3058cf9803bee7595baf \
+  src/Counter.sol:Counter
+```
+
+If your contract has constructor arguments, you can pass them using the `--constructor-args` option.
+For example:
+
+```bash
+--constructor-args $(cast abi-encode "constructor(string,string,uint256,uint256)" "ForgeUSD" "FUSD" 18 1000000000000000000000)
+```
+
+You can run the following command to see all the options:
+
+```bash
+forge verify-contract --help
+```
+
+For contracts that run on multiple Chainweb EVM chains, you must run the `verify-contract` command on each chain.
+However, the `verify-contract` command doesn't support verification if a contract with the same bytecode has been previously verified. 
+If you attempt to verify a contract with the same bytecode as a contract that has been previously verified, verification will fail with a message similar to the following:
+
+```bash
+[address] is already verified. Skipping verification.
+```
+
+To test contract verification on multiple chains, you must change the bytecode, redeploy, then run the verify-contract command on the redployed contract.
+
+You can change the bytecode by adding a constant at the top of the contract like this:
+
+```solidity
+uint256 public constant DUMMY = 1;
+```
+
+Increase the value used for the constant in each contract you deploy to verify contracts that are deployed on multiple chains.