# 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="/files/CiYhu6qN7MQSRL0FpZGR" 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-kasplex.gitbook.io/krc20/protocols/rtd-rollup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.