Update batch configuration and environment variables for data availability worker

Author: saurenzio

README.md

@@ -291,7 +291,6 @@ proxy-relay:
       - LEGACY_BRIDGE_TESTING=1
       # - IPFS_API_URL=http://ipfs:5001
       - ML_RPC_URL=http://host.docker.internal:13034 # change to mainnet if needed
-      - ML_BATCH_SIZE=10 # change if necessary
       - 4EVERLAND_API_KEY= XXXXX
       - 4EVERLAND_SECRET_KEY= XXXX
       - 4EVERLAND_BUCKET_NAME=zkthunder # only for test
@@ -317,8 +316,6 @@ In zkthunder’s environment settings:
 
 - **ML_RPC_URL** stands for the RPC wallet port of Mintlayer.
 
-- **ML_BATCH_SIZE** controls the frequency of sending data to Mintlayer.
-
 - **4EVERLAND_API_KEY, 4EVERLAND_SECRET_KEY, 4EVERLAND_BUCKET_NAME** these three variables stand for a specific bucket
   on 4everland, we upload the block information to it.
 
@@ -344,14 +341,14 @@ tracing::info!( "put {} to ipfs and get response code: {:?}",
 
 Note that three batches is related to one block. And every time we add a batch’s data to the 4everland bucket, the
 storage network will respond with an ipfs hash value. We collect such value until the number of responses reach the
-threshold of **BATCH_SIZE\*3**.
+threshold of **BATCH_SIZE**.
 
 Then, we upload these all hash values as a file to 4everland storage:
 
 ```rust
 
 // if block_number reaches the BATCH_SIZE, report the hashes to ipfs and then mintlayer
-let batch_size: usize = env::var("ML_BATCH_SIZE")
+let batch_size: usize = env::var("BATCH_SIZE")
                         .ok()
                         .and_then(|v| v.parse().ok())
                         .unwrap_or(10  as  usize);

local-setup/.env.example

@@ -37,6 +37,7 @@ CF_ZONE_API_TOKEN=your-zone-api-token
 4EVERLAND_API_KEY=your-4everland-api-key
 4EVERLAND_SECRET_KEY=your-4everland-secret-key
 4EVERLAND_BUCKET_NAME=zkthunder-2
+BATCH_SIZE=30
 
 #######################
 # MintLayer Configuration
@@ -46,7 +47,6 @@ ML_RPC_URL=http://wallet-rpc-daemon:13034
 ML_RPC_USERNAME=wallet_rpc_user
 ML_RPC_PASSWORD=your-secure-password
 ML_MNEMONIC=your-wallet-mnemonic
-ML_BATCH_SIZE=10
 
 # Node Configuration
 ML_TESTNET_NODE_RPC_BIND_ADDRESS=0.0.0.0:13030
@@ -79,6 +79,7 @@ CHAIN_ETH_ZKSYNC_NETWORK=zkthunder
 CHAIN_ETH_ZKSYNC_NETWORK_ID=4237
 CONTRACTS_ERA_CHAIN_ID=4237
 LEGACY_BRIDGE_TESTING=1
+CHAIN_STATE_KEEPER_BLOCK_COMMIT_DEADLINE_MS=30000
 
 #######################
 # Accounts Configuration

local-setup/README.md

@@ -98,6 +98,7 @@ Default metrics collected from:
 - `4EVERLAND_API_KEY`: API key from 4EVERLAND
 - `4EVERLAND_SECRET_KEY`: Secret key from 4EVERLAND
 - `4EVERLAND_BUCKET_NAME`: Your bucket name in 4EVERLAND
+- `BATCH_SIZE`: The number of IPFS CIDs to consolidate into a single IPFS CID batch, should be a multiple of 3
 
 #### MintLayer Configuration
 
@@ -403,6 +404,10 @@ All services will be accessible as subdomains of this domain.
    - `ML_TESTNET_NODE_RPC_PASSWORD`
    - `ML_TESTNET_WALLET_RPC_DAEMON_RPC_PASSWORD`
 
+
+#### Chain State Keeper Configuration
+- `CHAIN_STATE_KEEPER_BLOCK_COMMIT_DEADLINE_MS`: This variable defines the maximum time limit, in milliseconds, for the batch commit process to Layer 1
+
 ### Deploying L2 Faucet
 
 You can deploy a faucet contract on the L2 network to allow users to request test ETH. Here's how to set it up:

local-setup/docker-compose.yml

@@ -143,7 +143,7 @@ services:
       --http.corsdomain "*" 
       --http.addr 0.0.0.0 
       --http.port 8545
-      --dev.block-time 2000ms
+      --dev.block-time 6000ms
       --chain /chaindata/reth_config
     environment:
       RUST_LOG: ${RUST_LOG:-info}