zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
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.
158 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: ea8238f090
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'ea8238f090'
${ noResults }
 ZIP  TAR.GZ
Sam Kleinman ea8238f090
abci: reorder sidebar (#282) 		4 years ago
.github proto: add files (#246) 4 years ago
ivy-proofs add Ivy proofs (#210) 4 years ago
proto proto: modify height int64 to uint64 (#253) 4 years ago
rfc Fix list of RFCs (#266) 4 years ago
rust-spec readme: cleanup (#262) 4 years ago
spec abci: reorder sidebar (#282) 4 years ago
.gitignore Add three timeouts and align pseudocode better with existing algorithm 7 years ago
.markdownlint.yml Current versions of light client specs from tendermint-rs (#158) 4 years ago
README.md readme: cleanup (#262) 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.