chore: update addresses (#332)

contracts/README.md

@@ -25,6 +25,17 @@ forge test
 SUCCINCT_GATEWAY=[0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803](https://etherscan.io/address/0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803)
 SUCCINCT_FEE_VAULT=[0x5999d401444f15d262fdce310bb68bd234de11aa](https://etherscan.io/address/0x5999d401444f15d262fdce310bb68bd234de11aa)
 
+| Chain            | Address                                                                                                                          |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| Mainnet          | [0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803](https://etherscan.io/address/0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803)            |
+| Goerli           | [0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803](https://goerli.etherscan.io/address/0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803)     |
+| Sepolia          | [0xaea9288f0b7a8c605c4d474c56e5e74f96bfd4b3](https://sepolia.etherscan.io/address/0xaea9288f0b7a8c605c4d474c56e5e74f96bfd4b3)    |
+| Holesky          | [0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803](https://holesky.etherscan.io/address/0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803)    |
+| Optimism         | [0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803](https://optimistic.etherscan.io/address/0x6e4f1e9ea315ebfd69d18c2db974eef6105fb803) |
+| Arbitrum         | [0x2d27182206f0442885989626934ca9dd5290f979](https://arbiscan.io/address/0x2d27182206f0442885989626934ca9dd5290f979)             |
+| Arbitrum Sepolia | [0x2d27182206f0442885989626934ca9dd5290f979](https://sepolia.arbiscan.io/address/0x2d27182206f0442885989626934ca9dd5290f979)     |
+| Gnosis           | [0x6e4f1e9eA315EBFd69d18C2DB974EEf6105FB803](https://gnosisscan.io/address/0x6e4f1e9eA315EBFd69d18C2DB974EEf6105FB803)           |
+
 ## Deploying
 
 Each contract has it's own deployment file in the form of `script/deploy/{Contract}.s.sol`. Inside each, there is a `Deploy{Contract}` script that will deploy the contract. This allows for programmatic cross-chain deployment of contracts using `script/deploy.sh`.
@@ -44,7 +55,7 @@ Contract verification will be automatically applied during deployment. However,
 For example, to verify both the proxy and implementation contract of SuccinctGateway (both of which have no `constructor_args`) on Chains 5, 420, 84531, and 421613, you would run:
 
 ```sh
-./script/verify.sh "SuccinctGateway" "5 420 84531 421613" "true" 
+./script/verify.sh "SuccinctGateway" "5 420 84531 421613" "true"
 ```
 
 ## Upgrading
@@ -59,7 +70,7 @@ Timelocked upgrades take place in two parts (`schedule` and then `execute` after
 
 #### Step 1: Deploy a new implementation contract
 
-Re-deploy the new contract via `script/deploy.sh`. This will generate a new `*_IMPL` implementation contract address with the current contract code. 
+Re-deploy the new contract via `script/deploy.sh`. This will generate a new `*_IMPL` implementation contract address with the current contract code.
 
 #### Step 2: Schedule the upgrade