Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Commit cb9f7ac

Browse files
committed
Update DA docs
1 parent 75ba3d7 commit cb9f7ac

1 file changed

Lines changed: 7 additions & 9 deletions

File tree

learn/data-availability.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22

33
Data availability (DA) is a core component of Rollkit's modular rollup framework. In Rollkit, data availability ensures that all transaction data and block information required to verify the rollup's state is accessible to anyone running a node or light client.
44

5+
Learn more about data availability:
6+
7+
- [What is DA](https://celestia.org/what-is-da/)
8+
- [The importance of DA for Rollups](https://medium.com/zeeve/exploring-data-availability-layer-and-its-importance-in-rollups-0a4fbf2e0ffc)
9+
510
## How Rollkit Handles Data Availability
611

712
Rollkit is designed to be DA-agnostic, meaning it can integrate with different data availability layers depending on your needs. The main options are:
813

9-
- **Mock Data Availability (Mock DA):**
10-
- Simple in-memory DA layer that is great for testing and development.
11-
- Data is stored and served by the rollup node itself.
12-
- Not secure for production, as data can be withheld by the node operator.
13-
1414
- **Local Data Availability (Local DA):**
1515
- Used for development, testing, and local deployments.
1616
- Not secure for production, as data can be withheld by the node operator.
@@ -26,12 +26,10 @@ Rollkit is designed to be DA-agnostic, meaning it can integrate with different d
2626
- Rollkit rollups rely on data availability to enable fraud proofs and ensure that invalid state transitions can be challenged.
2727
- If data is unavailable, users cannot verify the rollup's state or submit fraud proofs.
2828

29-
- **Interoperability:**
30-
- By supporting multiple DA layers, Rollkit enables rollups to be deployed in a variety of environments, from local devnets to scalable, decentralized networks.
31-
3229
## Best Practices
3330

34-
- **Use Mock or Local DA only for development and testing.**
31+
- **Use Local DA only for development and testing locally.**
32+
- **Alternatively, you can use [Celestia testnets](https://docs.celestia.org/how-to-guides/participate).**
3533
- **For production, always use a decentralized DA layer that implements the Rollkit DA interface.**
3634

3735
## Learn More

0 commit comments

Comments
 (0)