add record files

Author: jackchuma

mainnet/2025-07-24-eth-recovery/ARBITRUM_VALIDATION.md

@@ -22,6 +22,7 @@ is ready".
 Make sure your ledger is still unlocked and run the following.
 
 #### Arbitrum
+
 ```shell
 make sign-arb
 ```
@@ -66,18 +67,20 @@ After: 0x0000000000000000000000000000000000000000000000000000000000000042
 ```
 
 2. Verify that the delayed message count incremented and delayed inbox account was added in the "TransparentUpgradeableProxy" at address`0x8315177aB297bA92A06054cE80a67Ed4DBd7ed3a`. Because this is the arbitrum bridge contract that is in public use
-the exact changes may be different depending on when you run the script.
-Typically Key `0x0000000000000000000000000000000000000000000000000000000000000006` should be incremented by one and a new
-entry should be added to the delayed inbox (Key is a random hash and the change should be from `0` to some hash).
+   the exact changes may be different depending on when you run the script.
+   Typically Key `0x0000000000000000000000000000000000000000000000000000000000000006` should be incremented by one and a new
+   entry should be added to the delayed inbox (Key is a random hash and the change should be from `0` to some hash).
 
 Example delayed message count increment
+
 ```
 Key: 0x0000000000000000000000000000000000000000000000000000000000000006
 Before: 0x00000000000000000000000000000000000000000000000000000000001f7896
 After: 0x00000000000000000000000000000000000000000000000000000000001f7897
 ```
 
 Example entry
+
 ```
 Key: 0xf652222313e28459528d920b65115c16c04f3efc82aaedc97be59f3f379b85d5
 Before: 0x0000000000000000000000000000000000000000000000000000000000000000
@@ -86,7 +89,6 @@ After: 0xa75a3a7db6a5b6a4458a86058d0baeb45ca7bf04255214eb0bc849ce37d14627
 
 3. Verify that the signer address nonce incremented by 1
 
-
 #### 3.3. Extract the domain hash and the message hash to approve.
 
 Now that we have verified the transaction performs the right
@@ -151,4 +153,4 @@ by anyone once a threshold of signatures are collected, so a
 Facilitator will do the final execution for convenience.
 
 Share the `Data`, `Signer` and `Signature` with the Facilitator, and
-congrats, you are done!
+congrats, you are done!

mainnet/2025-07-24-eth-recovery/BASE_VALIDATION.md

@@ -22,6 +22,7 @@ is ready".
 Make sure your ledger is still unlocked and run the following.
 
 #### Base
+
 ```shell
 make sign-base{n}
 ```
@@ -60,14 +61,16 @@ Now click on the "State" tab. Verify that:
 1. Verify that the nonce is incremented for the Incident Multisig under the "GnosisSafeProxy" at address `0x14536667Cd30e52C0b458BaACcB9faDA7046E056`. We should see the nonce increment by 1:
 
 e.g
+
 ```
 Key: 0x0000000000000000000000000000000000000000000000000000000000000005
 Before: 0x0000000000000000000000000000000000000000000000000000000000000043
 After: 0x0000000000000000000000000000000000000000000000000000000000000044
 ```
 
 2. Verify that the Proxy at address `0x49048044D57e1C92A77f79988d21Fa8fAF74E97e` `prevBoughtGas` and `prevBlockNum` have changed.
-Note: that the prevBlockNum may be different
+   Note: that the prevBlockNum may be different
+
 ```
 Key: 0x0000000000000000000000000000000000000000000000000000000000000001
 Before: 0x00000000015fa555000000000007e1760000000000000000000000003b9aca00
@@ -76,7 +79,6 @@ After: 0x00000000015fa55700000000000f42400000000000000000000000003b9aca00
 
 3. Verify that the signer address nonce incremented by 1
 
-
 #### 3.3. Extract the domain hash and the message hash to approve.
 
 Now that we have verified the transaction performs the right
@@ -141,4 +143,4 @@ by anyone once a threshold of signatures are collected, so a
 Facilitator will do the final execution for convenience.
 
 Share the `Data`, `Signer` and `Signature` with the Facilitator, and
-congrats, you are done!
+congrats, you are done!

mainnet/2025-07-24-eth-recovery/Makefile

@@ -64,7 +64,7 @@ sign-base:
 
 .PHONY: execute-base
 execute-base:
-	CHAIN=$(BASE1) PORTAL=$(BASE_L1_PORTAL) forge script --rpc-url $(L1_RPC_URL) OPStackExecuteRecovery \
+	CHAIN=$(BASE) PORTAL=$(BASE_L1_PORTAL) forge script --rpc-url $(L1_RPC_URL) OPStackExecuteRecovery \
 		--ledger --hd-paths "m/44'/60'/$(LEDGER_ACCOUNT)'/0/0" --sig "run(bytes)" $(SIGNATURES) --broadcast
 
 .PHONY: sign-op

mainnet/2025-07-24-eth-recovery/OPTIMISM_VALIDATION.md

@@ -22,6 +22,7 @@ is ready".
 Make sure your ledger is still unlocked and run the following.
 
 #### Optimism
+
 ```shell
 make sign-op
 ```
@@ -67,7 +68,6 @@ After: 0x0000000000000000000000000000000000000000000000000000000000000043
 
 3. Verify that the signer address nonce incremented by 1
 
-
 #### 3.3. Extract the domain hash and the message hash to approve.
 
 Now that we have verified the transaction performs the right
@@ -132,4 +132,4 @@ by anyone once a threshold of signatures are collected, so a
 Facilitator will do the final execution for convenience.
 
 Share the `Data`, `Signer` and `Signature` with the Facilitator, and
-congrats, you are done!
+congrats, you are done!

mainnet/2025-07-24-eth-recovery/README.md

@@ -1,6 +1,6 @@
 # ETH Recovery Contract Deployment
 
-Status: PENDING
+Status: EXECUTED
 
 ## Description
 
@@ -9,12 +9,16 @@ This task deploys an ETH recovery system to recover funds mistakenly sent to the
 The deployment consists of two separate phases:
 
 **Phase 1 - Implementation Deployment (via DeployRecoveryImplementation.s.sol)**
+
 > This deployment will be broadcasted and executed onchain directly from this script
+
 - **Command**: `make deploy-implementation RPC_URL=<your-rpc-url>`
 - Deploy the Recovery implementation contract from a separate EOA (NOT the DEPLOYER address)
 
 **Phase 2 - Proxy Deployment (via DeployRecoveryProxies.s.sol)**
+
 > This script will NOT broadcast or execute any deployment - it only generates the deployment artifacts that will be consumed by our key management system
+
 - **Command**: `make dry-run-deployments RPC_URL=<your-rpc-url>`
 - Generate artifacts for 6 Recovery proxy contract deployments to align the DEPLOYER's nonce
 - The first 5 deployments increment the nonce (deploying Recovery proxies allows potential fund recovery from these addresses if needed)
@@ -23,11 +27,14 @@ The deployment consists of two separate phases:
 The Recovery contract enables the incident multisig to rescue ETH from any deployed contract address.
 
 ## Description
+
 We need to sign recoveries for 3 different chains. Please follow the instructions for each respective chain:
+
 - [Arbitrum](./ARBITRUM_VALIDATION.md)
 - [Optimism](./OPTIMISM_VALIDATION.md)
 
 Due to the large number of recoveries for the Base chain, they are split into 5 seperate transactions
+
 - [BASE1](./BASE_VALIDATION.md)
 - [BASE2](./BASE_VALIDATION.md)
 - [BASE3](./BASE_VALIDATION.md)