Insights from the 1st Dev Call on Celestia’s CIP process
Table of Contents
· 🧩Introducing
· 🧩Frequency and structure of development calls
· 🧩Trace the course — Celestia’s proposals for improvement
· 🧩Synergy in action — Forming working groups
· 🧩Technical Frontiers — Snark accounts and gas reimbursement
· 🧩 Data management — a new paradigm
· 🧩Clarifying terminology
· 🧩Conclusion: The future of Celestia
🧩Introducing
In October 2023, the Celestia Foundation announced the Celestia Improvement Proposal Process (CIP), which marks an important step in the evolution of the Celestia network. The CIP process aims to coordinate technical proposals to improve the network across its entire modular stack, including upgrades to the core protocol. Unlike most Cosmos chains, Celestia’s core protocol updates are not governed by token voting or validators, but by an off-chain social layer, echoing a similar model to Ethereum. This process, inspired by standardisation processes such as those of the Internet Engineering Task Force (IETF) and the Ethereum Improvement Proposal (EIP), applies to several layers of the Celestia stack, including consensus, data availability and peer-to-peer layers. In addition, Celestia’s Request for Comment (CRC) proposals will focus on design specifications for proposals that do not directly affect the core protocol. The CIP process encourages the participation of all stakeholders, fostering a collaborative environment for technical decision-making and innovation. You can learn more about the process in the publication Introducing the Celestia Improvement Proposal Process.
The Celestia Dev Call stood out as a crucial gathering for developers, strategists and enthusiasts. The Dev Call provided a platform for sharing ideas, addressing technical challenges and charting the future course of development of the Celestia Improvement Process programme. This article delves into the key discussions, innovative proposals and strategic planning that marked the last Dev Call.
🧩Frequency and structure of development calls
The Dev Call began with a discussion about its frequency and structure, reflecting on whether weekly, bi-weekly or monthly meetings would better serve the needs of the project. This conversation is more than logistics; it reflects a conscious effort to balance deep and meaningful development conversations with the agility needed in a rapidly changing technology landscape.
More info here:
https://github.com/celestiaorg/CIPs/blob/main/README.md
🧩Trace the course — Celestia’s proposals for improvement
One of the main points of the meeting was the Celestia Improvement Proposals (CIP). These proposals form the backbone of Celestia’s evolution and range from protocol adjustments to the introduction of important new features. The meeting stressed the importance of community consensus in shaping these proposals, emphasising the need for diverse viewpoints and strong advocacy for the proposed ideas.
More info here:
https://github.com/celestiaorg/CIPs/blob/main/cips/cip-1.md
🧩Synergy in action — Forming working groups
The call highlighted the formation of specialised working groups, addressing key areas such as data availability and user interface improvements. These groups represent a strategic move towards more specialised and focused efforts in key areas, fostering an environment of innovation and targeted problem solving.
🧩Technical Frontiers — Snark accounts and gas reimbursement
The technical segment of the call shed light on innovative proposals such as Snark accounts, which offer a combination of increased security and transaction efficiency. Another notable discussion focused on a proposal for a more equitable gas rebate mechanism within the Cosmos SDK, showing a drive towards fairness and efficiency in the use of resources.
🧩 Data management — a new paradigm
A key topic of discussion was the proposal to standardise the data expiry time for pruned nodes. This proposal is not just a technical consideration; it is a strategic decision affecting data management and network sustainability. It represents a thoughtful approach to balancing data availability with the practicalities of network maintenance.
More info here:
https://github.com/celestiaorg/CIPs/blob/main/cips/cip-4.md
🧩Clarifying terminology
Another proposal was to change the term “data availability” to “data publishing” to avoid confusion in the technology community. Data availability” has been misunderstood, often being confused with data storage. The proposal suggests that “data publishing” is a clearer and more accurate term, as it refers specifically to making data publicly accessible on the web. This change would facilitate understanding and avoid misunderstandings in the community.
More info here:
https://github.com/celestiaorg/CIPs/blob/main/cips/cip-5.md
🧩Conclusion: The future of Celestia
Celestia’s Dev Call, with its mix of technical deep dives and strategic discussions, marks an important step in the project’s journey. As the blockchain landscape continues to evolve, these meetings will play a pivotal role in guiding Celestia’s development, ensuring it remains at the forefront of innovation while adapting to the ever-changing needs of its community.
As we look forward to the next Dev Call, it is clear that Celestia is not just creating a technology, but nurturing a vibrant ecosystem that thrives on collaboration, innovation and a shared vision for the future.
