tendermint

9953 Commits

183 Branches

291 MiB

Tree: 1b4daf7c5f

Commit Graph

Author	SHA1	Message	Date
M. J. Fromberger	f9e0f77af3	docs: Update spec links to point to tendermint/tendermint (#7851 )	3 years ago
M. J. Fromberger	5a49d1b997	RFC 002 Interprocess Communication in Tendermint (#6913 ) Communication in Tendermint among consensus nodes, applications, and operator tools all use different message formats and transport mechanisms. In some cases there are multiple options. Having all these options complicates both the code and the developer experience, and hides bugs. To support a more robust, trustworthy, and usable system, we should document which communication paths are essential, which could be removed or reduced in scope, and what we can improve for the most important use cases. This document proposes a variety of possible improvements of varying size and scope. Specific design proposals should get their own documentation.	3 years ago

Author

SHA1

Message

Date

M. J. Fromberger

f9e0f77af3

docs: Update spec links to point to tendermint/tendermint (#7851 )

3 years ago

M. J. Fromberger

5a49d1b997

RFC 002 Interprocess Communication in Tendermint (#6913 )

Communication in Tendermint among consensus nodes, applications, and operator
tools all use different message formats and transport mechanisms.  In some
cases there are multiple options. Having all these options complicates both the
code and the developer experience, and hides bugs. To support a more robust,
trustworthy, and usable system, we should document which communication paths
are essential, which could be removed or reduced in scope, and what we can
improve for the most important use cases.

This document proposes a variety of possible improvements of varying size and
scope. Specific design proposals should get their own documentation.

3 years ago

2 Commits (1b4daf7c5f70ca8884a58a73454a216786faac9f)