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.
 
 
 
 
 
 
Sam Kleinman 048f6a32f9
lint: fix lint errors (#301)
4 years ago
.github proto: add files (#246) 4 years ago
ivy-proofs lint: fix lint errors (#301) 4 years ago
proto p2p: update state sync messages for reverse sync (#285) 4 years ago
rfc lint: fix lint errors (#301) 4 years ago
rust-spec Fixed a broken link (#291) 4 years ago
spec lint: fix lint errors (#301) 4 years ago
.gitignore Add three timeouts and align pseudocode better with existing algorithm 7 years ago
.markdownlint.yml lint: fix lint errors (#301) 4 years ago
README.md lint: fix lint errors (#301) 4 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 proto directory. These specify P2P messages that each implementation should follow to be compatible.