Update environment configuration for wallet keys and accounts

Author: saurenzio

infrastructure/local-setup-preparation/src/utils.ts

@@ -59,8 +59,8 @@ export async function isOperator(chainId: string, walletAddress: string): Promis
 
 export function getWalletKeys(): WalletKey[] {
     // Use private keys from environment variables
-    const privateKeys = process.env.API_WEB3_JSON_RPC_ACCOUNT_PKS
-        ? process.env.API_WEB3_JSON_RPC_ACCOUNT_PKS.split(',').map(key => key.trim())
+    const privateKeys = process.env.PRE_FUNDED_ACCOUNT_PKS
+        ? process.env.PRE_FUNDED_ACCOUNT_PKS.split(',').map(key => key.trim())
         : [];
 
     // If no keys are provided in environment, log a warning

local-setup/.env.example

@@ -98,6 +98,12 @@ ETH_SENDER_SENDER_OPERATOR_BLOBS_ETH_ADDR=your-eth-sender-operator-blobs-address
 CHAIN_STATE_KEEPER_FEE_ACCOUNT_ADDR=your-fee-account-address
 FEE_RECEIVER_PRIVATE_KEY=your-fee-account-private-key
 
+# Private key for the governance account
+GOVERNANCE_PRIVATE_KEY=0x86830b34ff2ee5a1e43ba6f3861e594137c3606e97d8bb30a4697e7be9c6969
+
+# Private key for the validator account
+VALIDATOR_PRIVATE_KEY=0x86830b34ff2ee5a1e43ba6f3861e594137c3606e97d8bb30a4697e7be9c6969d
+
 # Basic configuration: GOVERNOR_PRIVATE_KEY and DEPLOYER_PRIVATE_KEY should be the same
 # GOVERNOR_ADDRESS and CHAIN_ADMIN_ADDRESS should both be derived from that private key
 # Advanced configuration: GOVERNOR_ADDRESS should be derived from GOVERNOR_PRIVATE_KEY
@@ -110,6 +116,8 @@ GOVERNOR_PRIVATE_KEY=your-governor-private-key
 GOVERNOR_ADDRESS=your-governor-address
 # Address with administrative privileges for chain management
 CHAIN_ADMIN_ADDRESS=your-chain-admin-address
+# Pre-funded account private keys
+PRE_FUNDED_ACCOUNT_PKS=your-pre-funded-account-pks
 
 #######################
 # Block Explorer Configuration

local-setup/README.md

@@ -155,13 +155,31 @@ Your `.env` file must configure the following roles, using addresses that are pr
    GOVERNOR_PRIVATE_KEY=<private-key>
    GOVERNOR_ADDRESS=<derived-address>
    CHAIN_ADMIN_ADDRESS=<derived-address>
+   GOVERNANCE_PRIVATE_KEY=<private-key>
    ```
 
-   - Basic setup: Use the same private key for DEPLOYER and GOVERNOR roles
+   - Basic setup: Use the same private key for DEPLOYER, GOVERNOR and GOVERNANCE roles
    - Advanced setup: Can use different addresses for granular permissions
    - All addresses must be pre-funded in reth_config
    - GOVERNOR_ADDRESS and CHAIN_ADMIN_ADDRESS should be derived from their respective private keys
 
+5. **Validator Account**
+
+   ```
+   VALIDATOR_PRIVATE_KEY=<private-key>
+   ```
+
+   - Responsible for validating transactions and blocks
+   - Must be pre-funded in reth_config
+
+6. **Pre-funded Account**
+
+   ```
+   PRE_FUNDED_ACCOUNT_PKS=<private-key>
+   ```
+
+   - Pre-funded account private keys
+
 #### L1 Chain Configuration
 
 The Layer 1 chain configuration is defined in `local-setup/reth_chaindata/reth_config`. This file configures the local Ethereum-compatible chain used as the L1 for the zkSync deployment.