> For the complete documentation index, see [llms.txt](https://jk0-5.gitbook.io/jk-doks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jk0-5.gitbook.io/jk-doks/jk-doks-en/dkargo-platform/dkargo-network/rollup.md).

# Rollup

The key to the efficiency of the dKargo network lies in the rollup process. The rollup process proceeds as follows:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfuesqmGiu7Qqhci72K24MM25Jq2uKpkExWWd8eSkKr6C9f7DE_23zFO-BJTEXn7BLLzqmeJ40coMLmJDO1lGD6tzo_3raegbkqlK7ms4vanfMt-m91VPi5h4AL4IeLwL4REF28ZOWRRz6CaZqUwdisT73f?key=lVxGisYoJe5feqK40jbgfw" alt=""><figcaption></figcaption></figure>

## 1. Transaction Sequencing

The Sequencer receives transactions initiated by users, determines the processing order, and groups these transactions into Layer 3 blocks, organized by time.

## 2. State Synchronization

The generated Layer 3 blocks are propagated to all nodes within the network. Each node executes the transactions contained in the Layer 3 blocks using the State Transition Function (STF), ensuring data synchronization across the entire network. Since the transactions are executed in a predetermined order through the same STF, all nodes maintain a consistent state.

## 3. Rollup Processing

The Sequencer periodically batches the Layer 3 blocks and performs the rollup process, recording these onto Arbitrum-One. This process involves storing the cumulative hash values of the transactions and the structured information of the Layer 3 blocks (referred to as Rblocks) on Arbitrum-One.

<br>

<br>