# RTD-Rollup

KRC-20 adopts Kaspa’s **RTD (Real-Time Decentralization)** mechanism to implement an efficient and secure Layer-2 Rollup protocol. During block production, Layer-1 miners embed KRC-20 Rollup data into Kaspa Layer-1 blocks via the payload mechanism, enabling on-chain verifiability for KRC-20 OPs and state data.

Rollup data primarily consists of **checkpoint hash commitments** and auxiliary metadata. Each valid KRC-20 transaction deterministically produces an independent, **transaction-level checkpoint commitment**. This commitment is composed of (i) *the previous checkpoint*, (ii) *the OP header (used to anchor the OP’s Layer-1 reference data)*, and (iii) *the KRC-20 state commitment*, thereby forming a verifiable, tamper-evident chained provenance structure.

The KRC-20 Rollup protocol distributes rewards to miners who correctly submit checkpoints and satisfy the eligibility criteria. The reward schedule is computed automatically by the KRC-20 protocol and is disbursed in **bridged native KAS tokens**. The reward pool is funded by fees generated from KRC-20 OPs. This mechanism both sustains miner participation and further strengthens the decentralization of the Rollup process.

To qualify for Rollup rewards, the reward-receiving address (i.e., the coinbase output address) must **stake** a sufficient amount of bridged KAS on KRC-20. Addresses that fail to meet this requirement are considered ineligible and will not receive the corresponding Rollup reward share.

<figure><img src="https://2956913934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGVoRxPt0850PeAekrKkW%2Fuploads%2FGVKkOeacIAaghy8d8RmQ%2Fimage.png?alt=media&#x26;token=692f7d99-0034-4757-8953-fc4465cf0441" alt=""><figcaption></figcaption></figure>

* **Real-Time Decentralization:** Rollup data is submitted by miners worldwide.
* **Chained Commitments:** Strong-consistency, transaction-granular checkpoints that are traceable, verifiable, and immutable.
* **KRC-20 Incentive Mechanism:** Additional miner revenue coupled with bridged-KAS staking requirements.
