Rollup Batch Submission Tool

WHAT IT DOES

The Rollup Batch Submission Tool enables users to submit batches of L2 transactions to rollup contracts on L1. It reads rollup contract state for L1 rollup and sequencer inbox contracts, user address, wallet balance, and batch data including compressed transactions. The tool processes batch compression state, sequencer state, gas price, base fee, block timestamp, chain ID, transaction nonce, approval state, contract owner state, and submission status. It supports submitBatch for standard batch submission, batchSubmitCompressed for compressed batch submission, and batchWithProof for proof-attached batch submission. The tool reads the rollup contract's sequencer status, last batch ID, and batch count before execution.

HOW TO USE

Connect your wallet and select the target network (L1). Enter the rollup contract address and the batch data as hex-encoded L2 transactions. Choose whether the batch is compressed (true/false) and optionally provide proof data for batchWithProof. Select the execution method (submitBatch, batchSubmitCompressed, or batchWithProof). The tool will fetch the rollup state, display the sequencer status, and show the last batch ID. Once confirmed, it submits the batch to the rollup contract. The tool validates the batch data format and displays the data length before signing.

TECHNICAL MECHANISM

Unlike standard transaction submission tools, this executor is purpose-built for rollup batch submission workflows. It first reads the rollup contract's isActive() to ensure the contract is operational. The tool fetches sequencerStatus() to verify the sequencer is online and accepting batches. It reads lastBatchId() to display the current batch number and batchCount() for total submission count. The tool selects the optimal method: submitBatch for standard batch submission, batchSubmitCompressed for batches compressed with zlib or similar algorithms, or batchWithProof for batches that require verification proofs. The batch data is passed as bytes and validated for hex format before submission. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting. The tool displays the compressed status and batch data length for user verification.

WHAT IT CANNOT SEE

This tool cannot verify that the batch data is correctly formatted or that the transactions will execute successfully on L2. It cannot detect if the batch conflicts with other pending batches or if the sequencer has already processed the transactions. It also cannot guarantee that the batch will be accepted by the rollup contract. The tool cannot verify the proof data for batchWithProof submissions or detect if the proof is valid. It also cannot detect if the rollup contract has been paused or upgraded.

PLEASE NOTE

This tool supports EVM-compatible chains. Submitting a batch is irreversible—verify batch data carefully before signing. The rollup contract must implement the batch submission functions expected by this tool. Compressed batches must be properly compressed off-chain before submission. BatchWithProof requires a valid proof generated from the L2 state. This tool does not verify transaction validity—only submits the batch. For transaction validation, use the L2 Transaction Simulator.