This page outlines the transaction flow in the Elder protocol, showing how transactions move from users to rollups, through sequencing, data availability, settlement, and watch tower operations.

Elder Transaction Flow Docs

Official Elder transaction flow documentation

Join the Community

Get support and connect with other developers
Elder provides a unified entry point for transactions across multiple rollups, with decentralized sequencing, data availability, and robust settlement and dispute mechanisms.

​
Transaction Lifecycle Steps

1

Unified Entry Point

Users can send transactions across multiple rollups through a single entry point.
2

Transaction Sequencing

The proposer in the Elder protocol sequences transactions from different rollups and creates blocks for the respective rollups. The network achieves 1-block finality and provides inclusion finality for rollups.
3

Data Availability (DA)

Elder network compiles a single full block containing transactions from all rollups and sends it to the Data Availability (DA) layer.
4

Rollup Distribution

Rollups query their unit blocks and the transactions from Elder.
5

Proof Handling

Rollups send fault or validity proofs to the settlement layer.
6

Merkle Root Emission

Upon settlement, the system emits an event containing the Merkle root of the transaction roots from the blocks in the batch.
7

Watch Tower Operations

An independent, stateless Watch Tower can submit disagreement transactions to the sequencer node in case of a root hash mismatch.
8

Disagreement and Slashing

If a mismatch is detected, the Watch Tower submits a disagreement transaction, which can result in slashing the registration stake of the rollups.
Elder’s transaction flow ensures security, transparency, and rapid finality for all rollup transactions.
For more details and diagrams, see the official Elder transaction flow documentation.