The term of data availability is often considered a confusing term for community members:
- People who are new to modular networks may confuse it with “data storage”.
- People who are familiar with the term still may find it confusing (1, 2).
- Even Celestia finds it difficult to explain.
Below is the content of CIP itself for further discussion.
data availability isn’t as straightforward as it should be and could lead to misunderstandings within the community. To address this, this CIP proposes replacing
data availability with
data availability has caused confusion within the community due to its lack of intuitive clarity. For instance, in Celestia’s Glossary, there isn’t a clear definition of
data availability; instead, it states that
data availability addresses the question of whether this data has been published. Additionally, numerous community members have misinterpreted
data availability as meaning
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 and RFC 8174.
data availability is RECOMMENDED to be renamed to
Data publicationaligns more precisely with the intended meaning, which revolves around whether data has been published.
- The community already favors and commonly uses the term
Data publicationmaintains a similar structure to
data availability, making it easier for those familiar with the latter term to transition.
Proof of publication: While intuitive, it differs in structure from
data availabilityand may be too closely associated with terms like
proof of work, potentially causing confusion within consensus-related mechanisms.
Data availability proof: While logically coherent, it may create issues when used in conjunction with other terms, as the emphasis falls on “proof”. For instance, “verify a rollup’s data availability” and “verify a rollup’s data availability proof” might not refer to the same concept.
No backward compatibility issues found.
No security issues found.
Copyright and related rights waived via CC0.