High Level Goals for the next Third

[ebuchman]

This is a high level overview of potential plans for this repo over the next few months:

Priorities

• Wrap up the light-client release - https://github.com/informalsystems/tendermint-rs/milestone/1 (any other issues?)~~
• Wrap up the light-client verification spec (support with IBC)
• Integrate model-based testing for the light client and more comprehensive test suite - [light-client] Testing Regimen meta-issue #320, light-client: Verification Testing #330, Generator of Tendermint types for unit, integration, and model-based testing #393
• Support IBC effort with anything it might need from light-client or tendermint types - https://github.com/informalsystems/ibc-rs/issues/60
• Fork accountability spec and support for the Go implementation
• Light Client Evidence Submission - light-client: Fork Detection Evidence Submission Review #415
• Upgrade to be compatible with Tendermint v0.34 (ie. protobuf migration!) - Tendermint 0.34 compatibility #305

Common Goals

• Wrap up the fork detection English spec (not sure if we should focus on the TLA+ for it now)
• Absorb rust-abci repo (and potentially build out a rust abci client) - Absorb rust-abci #29
  • Potentially also support some very basic application development framework
• Improve the websocket connection - event_listener Web socket error #311, Event subscription ADR and refactor event_listener module #313
• Release 0.16.0 - https://github.com/informalsystems/tendermint-rs/milestone/3
• Type Generalizations - light-client: Type Generalization #416
• Productionization Efforts (documentation, crate organization, release process) - Add CONTRIBUTING.md #323
• Compiling to WASM - light-client: wasm compilation #463

Stretch Goals

• Implement the Tendermint MConnection, bring back SecretConnection from tmkms, and run a simple node that can make p2p connections to tendermint full nodes and exchange PEX messages (without any logic or address book ...) - to discuss and open issues about

[tomtau]

I may suggest absorbing @devashishdxt's rearchitected https://github.com/devashishdxt/abci-rs instead, as 1) it works with rust async, 2) has some desired features in place (e.g. unix domain socket support), 3) it was planned to replace the current rust-abci implementation:
tendermint/rust-abci#112 but delayed for the moment.

So I think it's a better starting point -- instead of the custom wrapper types, it can perhaps reuse parts of tendermint-rs?

[tac0turtle]

I may suggest absorbing @devashishdxt's rearchitected devashishdxt/abci-rs instead, as 1) it works with rust async, 2) has some desired features in place (e.g. unix domain socket support), 3) it was planned to replace the current rust-abci implementation:
tendermint/rust-abci#112 but delayed for the moment.

I agree with making this change. I would just like to point out that this may change some of the goals listed above as the current implementation may not be compatible with 0.34 of Tendermint-Go (state-sync, block pruning, runtime event indexing, ...).

[tomtau]

I may suggest absorbing @devashishdxt's rearchitected devashishdxt/abci-rs instead, as 1) it works with rust async, 2) has some desired features in place (e.g. unix domain socket support), 3) it was planned to replace the current rust-abci implementation:
tendermint/rust-abci#112 but delayed for the moment.

I agree with making this change. I would just like to point out that this may change some of the goals listed above as the current implementation may not be compatible with 0.34 of Tendermint-Go (state-sync, block pruning, runtime event indexing, ...).

will any of those have a big impact on abci-rs? For state-sync, it may just be protobuf update + extra trait / functions for it + expecting one more TCP/UDS connection?

[thanethomson]

I think this issue's been open for much longer than the initially anticipated quarter 🙂 I'm closing it for now in favor of the Q3 2021 milestone. I've moved the majority of the still-open issues/requirements to this new milestone with the exception of:

• Fork accountability spec and support for the Go implementation (is there an issue specifically for this somewhere in one of our repos?)
• Type generalizations light-client: Type Generalization #416