Transaction Rollups

High-frequency transactions are hard to achieve in a blockchain that is decentralized and open. For this reason, many blockchains offer the possibility to define layer-2 solutions that relax some constraints in terms of consensus to increase the transaction throughput. Such solutions rely on the layer-1 chain as a gatekeeper and are “optimistic” in that they consider that economic incentives are sufficient to prevent attacks.


Optimistic rollups are a popular layer-2 solution, e.g., on the Ethereum blockchain (Boba, Arbitrum, Optimism, etc.).


A rollup is a layer-2 solution for high-frequency transactions. A rollup is characterized by a rollup context and a set of rollup operations.

A rollup node is a software component running the rollup. By applying rollup operations, a rollup node turns a rollup context into a new one to make the rollup progress.

A rollup user interacts with the rollup through the rollup node and the Tezos node. A rollup participant is a user that administrates a rollup node.

Note that several rollups can simultaneously be alive on the Tezos chain.


Optimistic rollups work as follows.

Rollup operations (signed by rollup users) are submitted to the layer-1 chain, a.k.a the Tezos chain. As a consequence, the consensus algorithm of the layer-1 chain is used to set and order rollup operations, and nothing more. In particular, rollup operations are not interpreted by the nodes of the layer-1 chain.

Rollup nodes are daemons responsible for interpreting the rollup operations, and computing the rollup context. This context is encoded in a Merkle tree, a ubiquitous data structure in the blockchain universe with many interesting properties. Two of these properties are significant in the context of optimistic rollups:

  1. A given Merkle tree is uniquely identified by a root hash, and

  2. It is possible to prove the presence of a value in the tree without having to share the whole tree, by means of Merkle proofs.

Optimistic rollups implementations leverage these two properties. Firstly, rollup nodes can submit commitments to the layer-1 chain, to advertise the root hash of the rollup context after the application of a set of rollup operations. Secondly, rollup participants can assert the correctness of these commitments, and provide proofs asserting they are incorrect, we call rejections thereafter. By verifying these proofs, the layer-1 chain can reject an invalid commitment without the need to compute the rollup context itself.

As a consequence, the correctness of the rollup operations application is guaranteed as long as one honest rollup node is participating. By contrast, in the absence of honest nodes, a malicious rollup node can commit an invalid hash root, and take over the rollup. This is the reason behind the “optimistic” of optimistic rollups.

Transaction Rollups on Tezos

In some blockchains, optimistic rollups are usually implemented as smart contracts on the layer-1 chain. That is, rollup operations, commitments, and rejections are submitted as layer-1 transactions to a smart contract.

In Tezos, transaction rollups are implemented inside the economic protocol. Rollup users interact with these rollups by means of a set of dedicated manager operations. This design choice, permitted by the amendment feature of Tezos, allows for a specialized, gas- and storage-efficient implementation of optimistic rollups.

Getting Started

Originating a Transaction Rollup

The tezos-client has a dedicated command that any implicit account holder can use to originate a transaction rollup.

tezos-client originate tx rollup from <implicit account address>

where tx is an abbreviation for transaction.

The origination of a transaction rollup burns ꜩ15.

A transaction rollup address is attributed to the new transaction rollup. This address is derived from the hash of the Tezos operation with the origination operation similarly to the smart contract origination. It is always prefixed by tru1. For instance,


is a valid transaction rollup address.

When using the tezos-client to originate a transaction rollup, the client outputs the address of the new rollup.