Input Output Researcher Explain Cardano Data Availability Needs

Input Output researcher Giorgos Panagiotakos don submit one document wey explain why Cardano base layer need one dedicated data availability capability.

The proposed Layer 1 Data Availability problem statement dey examine how projects fit publish information wey other people fit retrieve and verify without to make am part of the ledger permanent transaction history. E draw from requirements wey dem discuss for one IO Research technical workshop on September 3.

Why Cardano Projects Need Access to Published Data

Some blockchain applications need make information remain available only long enough for participants to verify action or respond to problem. Others need records to dey accessible long after dem create am.

For certain Layer 2 protocols, participants fit need published state information to reconstruct their positions and withdraw funds if the protocol stall or operator go offline. Optimistic rollups need make transaction data remain accessible long enough for participant to construct fraud proof when dem wan challenge one asserted state.

The document still list large zero-knowledge proofs, governance ballots, audit records and applications wey dey group many small operations into batches. Their retention requirements different: some information fit dey needed for hours, other data for days, and records wey dem go use for later audits fit reach years.

Panagiotakos describe several existing options. Projects fit publish data directly to the Cardano ledger, rely on external system like Celestia, or use trusted operator. According to the document, to post large volumes to the ledger fit cost too much for some applications, while external service dey introduce separate security and availability assumptions.

The CPS still discuss IPFS, wey dey identify content using information wey dem derive from the data itself. That approach allow recipient to check retrieved content, but e no guarantee say another participant go continue to store and serve am.

What a Cardano Data Availability Layer Would Need

The problem statement set out five goals for potential solution. E availability guarantees suppose rely on Cardano existing security assumptions instead of independently trusted storage operator or separate external validator set.

Published information suppose also dey retrievable for defined period. Any proposed solution go need specify when publication dey accepted, when retention begin and end, and the assumptions under which participants fit obtain the data.

The third goal na data integrity: anybody wey retrieve the information suppose fit verify say e correct. The fourth na support for membership and non-membership proofs, wey go allow Plutus smart contracts to check whether particular data belong to published set.

The final goal cover cost and performance. The CPS dey call for substantially lower cost per byte than to publish equivalent data directly to the base layer, higher throughput and publication latency wey dey comparable to Layer 1. E ask make future proposals state figures wey dem fit take measure those requirements.

The document illustrate the range of needs through individual projects. E list retention period of one hour to five days for Gummiworm, while Midgard, one optimistic rollup, dey described as needing seven-day storage and support for membership and non-membership proofs.

For governance applications, the CPS point to previous Project Catalyst voting rounds when e dey discuss potential capacity of 100,000 to one million votes. E still note say some post-quantum zero-knowledge proofs fit pass 100 kilobytes, wey dey increase the amount of data wey applications fit need to publish.

Permanent archival storage and confidentiality no dey inside the proposed scope. For governance records wey need remain available for audits years later, the document identify separate archival mechanism as necessary.

[NEWSBREAK]

Costs, Timing and Open Technical Questions

Panagiotakos never select architecture or announce completed network upgrade. The CPS dey ask which proof system fit support the required throughput and how Plutus scripts go reference am.

E still leave open who suppose pay for retaining data: the publisher, the party wey dey retrieve am or the protocol. Any pricing model go need account for both occasional small publications and applications wey dey generate sustained high-volume traffic.

For stake pool operators, the document dey ask how solution go affect hardware requirements and operating costs, and which incentives go encourage participation. E still call for first phase wey simple enough to deliver useful capability for at least one of the identified applications.

The problem statement include timing constraint. According to the document, solution wey pass roughly eight months away fit arrive too late for some projects wey dey plan to launch within the year. Later alternative go need significant throughput improvement or another clear advantage to replace infrastructure wey project don already integrate.

Post-quantum security dey listed as desirable rather than mandatory. The proposed CPS still open for the Cardano Improvement Proposals repository and dem never assign number give am.