> For the complete documentation index, see [llms.txt](https://elder-2.gitbook.io/elder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elder-2.gitbook.io/elder-docs/architecture/transaction-flow.md).

# Transaction Flow

<div data-full-width="false"><figure><img src="/files/Sc0wLf7QFhnpJGUW1ypF" alt=""><figcaption></figcaption></figure></div>

#### Transaction Lifecycle

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.