Data Availability in Rollkit
Data availability (DA) is a core of Rollkit's. Rollkit utilize's 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.
Learn more about data availability:
How Rollkit Handles Data Availability
Rollkit is designed to be DA-agnostic, meaning it can integrate with different data availability layers depending on your needs. The main options are:
Local Data Availability (Local DA):
- Used for development, testing, and local deployments.
- Not secure for production, as data can be withheld by the node operator.
External Data Availability Layer (DA Interface):
- Used for production and secure deployments.
- Rollkit can post block data to any external DA layer that implements the Rollkit DA interface (e.g., Celestia).
- Anyone can verify that the data is available and reconstruct the rollup state, depending on the guarantees of the chosen DA layer.
Why Data Availability Matters in Rollkit
- Fraud Proofs and Security:
- Rollkit rollups rely on data availability to enable fraud proofs and ensure that invalid state transitions can be challenged.
- If data is unavailable, users cannot verify the rollup's state or submit fraud proofs.
Best Practices
- Use Local DA only for development and testing locally.
- Alternatively, you can use Celestia testnets.
- For production, always use a decentralized DA layer that implements the Rollkit DA interface.