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.
 
 
 
 
 
 
William Banfield 6c142f37cd
language fixups
3 years ago
..
README.md abci++ spec: reorganizing basic concepts, adding outline for easy navigation (#8048) 3 years ago
abci++_app_requirements_002_draft.md Editorial/Lint changes 3 years ago
abci++_basic_concepts_002_draft.md Update abci++_basic_concepts_002_draft.md (#8114) 3 years ago
abci++_methods_002_draft.md language fixups 3 years ago
abci++_tmint_expected_behavior_002_draft.md Vote extensions: new design (#8031) 3 years ago
v0.md ABCI++ markdown integration into Tendermint (for spec) (#327) 3 years ago
v1.md ABCI++ markdown integration into Tendermint (for spec) (#327) 3 years ago
v2.md ABCI++ markdown integration into Tendermint (for spec) (#327) 3 years ago
v3.md ABCI++ markdown integration into Tendermint (for spec) (#327) 3 years ago
v4.md ABCI++ markdown integration into Tendermint (for spec) (#327) 3 years ago

README.md

order parent
1 [{title ABCI++} {order 3}]

ABCI++

Introduction

ABCI++ is a major evolution of ABCI (Application Blockchain Interface). Like its predecessor, ABCI++ is the interface between Tendermint (a state-machine replication engine) and the actual state machine being replicated (i.e., the Application). The API consists of a set of methods, each with a corresponding Request and Response message type.

The methods are always initiated by Tendermint. The Application implements its logic for handling all ABCI++ methods. Thus, Tendermint always sends the Request* messages and receives the Response* messages in return.

All ABCI++ messages and methods are defined in protocol buffers. This allows Tendermint to run with applications written in many programming languages.

This specification is split as follows:

  • Overview and basic concepts - interface's overview and concepts needed to understand other parts of this specification.
  • Methods - complete details on all ABCI++ methods and message types.
  • Requirements for the Application - formal requirements on the Application's logic to ensure liveness of Tendermint. These requirements define what Tendermint expects from the Application.
  • Tendermint's expected behavior - specification of how the different ABCI++ methods may be called by Tendermint. This explains what the Application is to expect from Tendermint.

TODO Re-read these and remove redundant info

  • Applications - how to manage ABCI application state and other details about building ABCI applications
  • Client and Server - for those looking to implement their own ABCI application servers