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

Commit 2503644

Browse files
committed
remove section on DA
1 parent 16a579e commit 2503644

1 file changed

Lines changed: 0 additions & 6 deletions

File tree

learn/data-availability.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,12 +20,6 @@ Rollkit is designed to be DA-agnostic, meaning it can integrate with different d
2020
- Rollkit can post block data to any external DA layer that implements the Rollkit [DA interface](https://github.com/rollkit/rollkit/blob/main/core/da/da.go#L11) (e.g., Celestia).
2121
- Anyone can verify that the data is available and reconstruct the rollup state, depending on the guarantees of the chosen DA layer.
2222

23-
## Why Data Availability Matters in Rollkit
24-
25-
- **Fraud Proofs and Security:**
26-
- Rollkit rollups rely on data availability to enable fraud proofs and ensure that invalid state transitions can be challenged.
27-
- If data is unavailable, users cannot verify the rollup's state or submit fraud proofs.
28-
2923
## Best Practices
3024

3125
- **Use Local DA only for development and testing locally.**

0 commit comments

Comments
 (0)