This app runs inside the BotSurf browser. Don't have it yet? Get the app or extension now!

Rollup Force-Inclusion Request Tool

Developer Tools · All
0 installs · Verified BotGentz app
Launch App
Opens in BotSurf — nothing to install.
CategoryDeveloper Tools
PlatformAll
Pricing Free
Installs0
Download BotSurf to use — free
No account needed for free apps. Once BotSurf is open, find this app in Apps from the + menu.

About this app

WHAT IT DOES

The Rollup Force-Inclusion Request Tool enables users to request force inclusion of L2 transactions through L1 rollup contracts. It reads rollup contract state for L1 rollup and sequencer inbox contracts, user address, wallet balance, and transaction data including sender, target, value, and data. The tool processes force-inclusion parameters such as deadline and gas price, sequencer state, gas price, base fee, block timestamp, chain ID, transaction nonce, approval state, contract owner state, and request status. It supports requestForceInclusion for standard requests, batchForceInclusion for multiple requests in one transaction, and forceInclusionWithProof for proof-attached requests.

HOW TO USE

Connect your wallet and select the target network (L1). Enter the rollup contract address, sender address, target L2 contract address, transaction value in wei, and transaction data as hex. Optionally set a gas price override in gwei and a deadline in blocks from now. Choose the execution method (requestForceInclusion, batchForceInclusion, or forceInclusionWithProof). The tool will fetch the rollup state, display sequencer status, and show the current request status. Once confirmed, it submits the force-inclusion request. The tool validates all addresses and data before signing.

TECHNICAL MECHANISM

Unlike standard transaction submission tools, this executor is purpose-built for rollup force-inclusion workflows. It first reads the rollup contract's isActive() to ensure the contract is operational. The tool fetches sequencerStatus() to check if the sequencer is online—force-inclusion is typically used when the sequencer is not processing transactions. It reads the request status via getRequestStatus() to check if the transaction has already been processed or included. The tool selects the optimal method: requestForceInclusion for standard requests, batchForceInclusion for multiple requests in one transaction, or forceInclusionWithProof for requests with proof data. The deadline is specified in L1 blocks from the current block. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting. The tool displays the transaction data length and deadline before confirmation.

WHAT IT CANNOT SEE

This tool cannot guarantee that the force-inclusion request will be processed or that the transaction will be included within the deadline. It cannot predict the sequencer's behavior or detect if the request has already been processed. It also cannot guarantee that the transaction will be included at the specified gas price. The tool cannot verify the proof data for forceInclusionWithProof or detect if the sequencer has resumed normal operation. It also cannot detect if the rollup contract has been paused or upgraded.

PLEASE NOTE

This tool supports EVM-compatible chains. Force-inclusion is a last resort mechanism—use only when the sequencer is not processing transactions. The request is irreversible—verify all data carefully before signing. The rollup contract must implement the force-inclusion functions expected by this tool. The deadline must be later than the current block; setting it too short may cause the request to expire. Batch requests require arrays of senders, targets, values, data, and deadlines. This tool does not guarantee inclusion—only requests it.

Similar Apps

Log in to BotGentz

Suggest an App

Tell us what you'd find useful — if we build it, we'll email you the moment it's ready.