Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CIP: Rename data availability to data publication #6

Merged
merged 7 commits into from
Nov 28, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions cips/cip-5.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
cip: 5
title: Rename data availability to data publication
description: Renaming data avaiability to data publication to better reflect the message
author: msfew (@fewwwww) <msfew@hyperoracle.io>, Kartin <kartin@hyperoracle.io>, Xiaohang Yu (@xhyumiracle)
discussions-to: https://forum.celestia.org/t/informational-cip-rename-data-availability-to-data-publication/1287
status: Draft
type: Informational
created: 2023-11-06
---

## Abstract

The term [`data availability`](https://celestia.org/glossary/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 publication`.

## Motivation

The term `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 `data storage`.

## Specification

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.

The term `data availability` is RECOMMENDED to be renamed to `data publication`.

## Rationale

Motivations:
- `Data publication` is the act of making data publicly accessible. In Celestia's context, it means the block data was actually published to the network and ready to be accessed, downloaded, and verified. This aligns more precisely with the intended meaning, which revolves around whether data has been published.
- The community already favors and commonly uses the term `data publication`.
- `Data publication` maintains a similar structure to `data availability`, making it easier for those familiar with the latter term to transition.

Alternative designs:
- `Proof of publication`: While intuitive, it differs in structure from `data availability` and 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.

## Copyright

Copyright and related rights waived via [CC0](../LICENSE).