Rollup Transaction

Overview

A rollup transaction changes state within a rollup execution environment. It may transfer assets, call a contract, deploy code, or perform a protocol-defined system operation without being individually executed by the settlement chain. The sequencer normally receives and orders the transaction, and rollup nodes execute it. Later, the transaction’s data or resulting state difference is included in a batch whose commitment, proof, or challenge window is processed on the settlement layer.

Applications should expose whether a transaction is received, sequenced, published, proven, and finalized because these stages carry different reversal risks. Fees may include rollup execution and underlying data publication. Transaction hashes, nonce rules, and formats can differ across rollups even when they present an Ethereum-compatible interface. A transaction accepted by a sequencer has not necessarily been published, proven, finalized on the base layer, or made withdrawable. Rollup Transaction should be described through its execution, sequencing, data-publication, proof or challenge, bridge, and settlement stages.

The security model for Rollup Transaction includes sequencer control, proof or fault-resolution rules, data availability, bridge contracts, upgrade keys, and the base-layer verifier. A cryptographic proof can reduce execution trust while leaving censorship, data, governance, and contract risks.

Fulfillment and withdrawal policies should use the stage that matches the business risk. Payment applications using Rollup Transaction should maintain separate states for local acceptance, batch publication, proof verification or challenge completion, bridge execution, and base-layer finality. Reliable operation requires monitoring for sequencer outages, delayed batches, proof failures, forced-inclusion paths, contract pauses, and upgrade events. Users should have a documented route to recover or exit when the preferred sequencer, prover, or interface is unavailable.