Devnet

[liamsi]

Dev-net

After our MVP we want to be able to deploy a basic dev-net.

Goals

The main goal of the dev-net is to test DAS in a much more realistic setting and at the same time test the deployment flow and assumptions about rollups as much as possible.

Hence the minimal features we need before we can launch the devnet are:

• full storage nodes (FS) and DAS light clients
• ability to deploy optimint/ABCI-based Rollups

Stretch goals

Ideally, we would have fully implemented (state and erasure coding) fraud proofs as well as the propagation part.
Additionally, it would be nice to have Ethermint/some EVM compatible execution environment as a rollup on top of optimint. Also, nice to have are partial nodes but this depends and is blocked on celestiaorg/celestia-specs#200.

ADRs and Spec

• Summarize all changes that were already done in lazyledger-core in one ADR ADR: document changes pre-ADR001 #386
• Define a path for moving the bitswap/IPFS logic into a separate repo
• Describe communication between core/consensus to Celestia node and overall Design of Celestia node (@liamsi)
• Write networking documentation for networking between Celestia nodes
• ADR regarding the PartsetHeader (goal: minimize changes to tendermint but still safe) (Proposal: Remove the PartSetHeader from the Header and don't Sign over it when Voting #511)

The issues below are not directly blocking the dev-net but are critical to increase implementation and specification velocity mid and long-term:

• further improve and codify process between specs and implementation Add Contributing.md and codify process and goals celestia-specs#158
• Critical Component: Consensus
  • Pseudo-Code for core consensus: Pseudocode for core-consensus protocol celestia-specs#176,
  • fork-choice & leader selection: https://github.com/lazyledger/lazyledger-specs/issues/148
• Clarifications and Assumptions around storage nodes: node types: storage nodes celestia-specs#175

Repositories

• Create Celestia node repo (as laid out in ADR)

Granular issues

• Optimint is ready for deploying Rollups (use-case / dev centric MVP)
• consensus timeouts to achieve 60 sec block time: Investigate consensus steps timeouts #87
• Revert writing to local dag during proposal #436
• Define and implement DAS light client logic in Celestia node repo
• Make it easy to pull changes from upstream and cherry-pick celestia-core onto tendermint #528
• Revert changes to the BlockID and PartSetHeader #509
• Remove the DataAvailabilityHeader from the Proposal #518
• Refactor remaining changes to tendermint to be more isolated #505
• Decouple DAS from celestai-core #506
• ipld: consider moving into separate repo #296
• Celestia node; for details see: Write ADR for high-level pre-devnet architecture celestia-node#1 (previous context: ADR: First Implementation of a Storage Node #435)

Chores

• Code Contribution Guidelines to facilitate community contributions: should be tackled as part of Define CONTRIBUTING.md #407

Nice to Have

• serving shares per NID (#221, [ DRAFT / WIP ] p2p/ipld: retrieve application messages #422)
• Use a different ipfs-network: https://github.com/celestiaorg/lazyledger-core/issues/154
• Define data "sharding" for partial nodes: Define how to shard the chain data for partial nodes celestia-specs#200
• erasure coding fraud proofs Implement BadEncodingFraudProof  #461
• (fully) implement state fraud proofs across repos: Fraud Proofs Tracking Issue #459
• clarify how much of the custom logic could moved into the app
• Decide on: git sync Codify the decision that validators will download all block data celestia-specs#180
• Proposal: Remove the PartSetHeader from the Header and don't Sign over it when Voting #511

[liamsi]

Congrats everyone 🎉 This issue can be closed. Let's create tracking issues per team and I'll create an overarching project board for the next milestone: testnet.