Testnet Tracking Issue

[evan-forbes]

Core & App

Summary

Here are the issues we are aiming to address before testnet. Essentially, we will attempt re-write most of the existing logic in celestia-core in the app. We might not be able to use stock tendermint at first, but that is the goal for mainnet. This will be done by using the PrepareProposal and ProcessProposal portions in the abci++ branch. This list is not yet complete, and some features might not be possible without ABCI++.

ABCI++

• Adopt simplified version of ABCI++ merging back potentially split shares into corresponding fields of Block.Data celestia-core#231

Filling the data square

• Implement non-interactive defaults #455
• Mechanism to efficiently and safely fill the square #454
• Adopt Reaping from the mempool to max square size #77

Bad Encoding Fraud Proof

• Implement BadEncodingFraudProof #461

Check for message inclusion

• ADR for message inclusion check #520
• Create API to check for message inclusion #565

Maintenance/Bug fixes/Misc

• p2p/ipld: LazyLedger ipld plugin celestia-core#144
• Debug why WirePayForMessages are not removed from the mempool when rechecking transactions #584
• Decide on signing over the PartSetHeader #511
• build(deps): Bump github.com/tendermint/tm-db from 0.5.1 to 0.6.0 celestia-core#39
• use a different network than the default public ipfs network celestia-node#3
• Quick and dirty fee burning
• Changing the default consensus timeouts #585
• Support malleated transactions in the event system #590

Stretch Goals

• Check that only paid for messages are included in the block
• Proper fee burning build(deps): Bump github.com/btcsuite/btcd from 0.20.1-beta to 0.21.0-beta celestia-core#49
• Message inclusion fraud proofs #519
• gas optimize the quantum gravity bridge (e.g. BLS sigs)

Quantum Gravity Bridge

• contracts: nmt verification Merkle proof verification for Solidity contracts blobstream-contracts#6
• contracts: parsing out shares Library for share parsing blobstream-contracts#18
• orchestrator: change to send data to contract only Orchestrator changes for new contract blobstream-contracts#9
• orchestrator: decide on either merkelize and send tuples to contract, or, use existing data root and implement accordingly Investigate what to commit to blobstream-contracts#20
• orchestrator: read tuples from app/node (depends on the above decision) Orchestrator read pay for message txs from node blobstream-contracts#19
• deploy on ETH test-net 🎉 🚀

EVMOS settlement rollup hub

• complete and stabilize EVMOS ontop of optimint integration (Implement transaction indexing rollkit/rollkit#189, rpc: Implement endpoints rollkit/rollkit#49)
• run it as part of CI/CD pipeline (@jbowen93, @Bidon15)
• customize and deploy Arbitrum on top of EVMOS rollup
• planning goal: spec out and implement state fraud proofs for the EVMOS settlement rollup
• stretch/planning goal: decide and spec out leader selection for Evmos rollup (could be in solidity or a modified version of the staking module)

Celestia Node

See ADR for details.

• State Machine Integration (ability for node to recompute state independent tendermint+app)
• Bad Encoding Fraud Proofs
• RPC framework + APIs

Optimint

• integrate Optimint with Celestia DA layer (Implement LazyLedger Data Availability client rollkit/rollkit#64)

[evan-forbes]

closing as this tracking issue is outdated