[Epic]: Runtime

[tac0turtle]

Summary

Today the cosmos-sdk is meant to be modular, while it is "modular" to a certain extent there is a need for this to be easier for advanced users. Secondly as we explore different worlds and different consensus engines limiting to what is defined ABCI further limits what can be built.

For example if a user wanted to use a custom header for specific use cases that may not be as generalizable as the current structure (abci).

There are many cases where users may want to swap things out for different designs or only use the sdk as a middleware. The current design is limiting in these functions.

This epic aims to define a couple interfaces that users can swap functionality: consensus, mempool, server, client, commitment, storage and so on.

Problem Definition

Baseapp is limiting in nature due to the tight coupling of ABCI and degree of understanding in order to have confidence in the changes.

Work Breakdown

Phase 1

Tasks

Preview Give feedback

1. Begin defining needs of various users
2. Decouple Comet from modules and storage #17425
   C: comet C:server/v2 T:tech debt +3
3. Write ADR on different interfaces

Phase 2

(After Phase 1 is completed we will have a better idea of the work break down needed for phase 2, for now it will be left as TBD)

Tasks

Preview Give feedback

1. TBD

[tac0turtle]

closing in favour of #18282