Open
Description
High-level tracking issue for improvements targeting users who want to integrate with CometBFT-based nodes. This issue will be expanded over time.
Integrators currently make use of several surfaces/APIs of a CometBFT-based node in order to provide value-added services on top of those nodes. We want to provide ways to make integrators' lives easier.
This issue does not cover the Go APIs. For improvements targeting the Go APIs, please see #42
Sub-issues:
- Make consuming our Protobuf definitions easier
- Restructure Protobuf usage in Tendermint: version protobuf files tendermint/tendermint#9197 (comment)
- proto: Implement versioning #95
- Publish our Protobuf definitions to the Buf Schema Registry
- Provide better quality, standards-compliant APIs
- Allow for reliable offloading of data to companion services (e.g. independently scalable RPC services)
- Decide which approach is best between:
- ADR-100: Data Companion Push API #73
- ADR-101: Data Companion Pull API #82 ✔️
- ABCI "shim" mechanism to intercept data between the node and ABCI app, as proposed by @lasarojc
- ADR 101: Data companion pull API #574
- Decide which approach is best between:
Original issue tendermint/tendermint#9883