You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
M. J. Fromberger
e92aa56a75
|
3 years ago | |
|---|---|---|
| .github | 3 years ago | |
| ivy-proofs | 3 years ago | |
| proto | 3 years ago | |
| rfc | 4 years ago | |
| rust-spec | 3 years ago | |
| spec | 3 years ago | |
| third_party/proto/gogoproto | 3 years ago | |
| .clang-format | 3 years ago | |
| .gitignore | 3 years ago | |
| .markdownlint.yml | 4 years ago | |
| CHANGELOG.md | 4 years ago | |
| Makefile | 3 years ago | |
| README.md | 4 years ago | |
| buf.gen.yaml | 3 years ago | |
| buf.yaml | 3 years ago | |
README.md
Tendermint Spec
This repository contains specifications for the Tendermint protocol.
There are currently two implementations of the Tendermint protocol, maintained by two separate-but-collaborative entities: One in Go, maintained by Interchain GmbH, and one in Rust, maintained by Informal Systems.
Data Structures
Consensus Protocol
P2P and Network Protocols
- The Base P2P Layer: multiplex the protocols ("reactors") on authenticated and encrypted TCP connections
P2P Messages
- Peer Exchange (PEX): gossip known peer addresses so peers can find each other
- Block Sync: gossip blocks so peers can catch up quickly
- Consensus: gossip votes and block parts so new blocks can be committed
- Mempool: gossip transactions so they get included in blocks
- Evidence: sending invalid evidence will stop the peer
ABCI
- ABCI: Details about interactions between the application and consensus engine over ABCI
RFC
- RFC: RFCs describe proposals to change the spec.
ProtoBuf
- Proto: The data structures of the Tendermint protocol are located in the
protodirectory. These specify P2P messages that each implementation should follow to be compatible.