mirror of
https://github.com/tendermint/tendermint.git
synced 2026-01-07 05:46:32 +00:00
24222c5855
* add parameters to byzantine send action * make net not trusted it's not necessary since for proofs Ivy will assume that the environment does not break action preconditions * use require instead of assume it seems that assume is not checked when other isolates call! * add comment * add comment * run with random seed * make domain model extractable to C++ * substitute require for assume assumes in an action are not checked when the action is called! I.e. they place no requirement on the caller; we're just assuming that the caller is going to do the right thing. This wasn't very important here but it leade to a minor inconsistency slipping through. * make the net isolate not trusted there was no need for it * add tendermint_test.ivy contains a simple test scenario that show that the specification is no vacuuous * update comment * add comments * throw if trying to parse nset value in the repl * add comment * minor refactoring
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.