This is a very small change, but removes a method from the `service.Service` interface (a win!) and forces callers to explicitly pass loggers in to objects during construction rather than (later) injecting them. There's not a real need for this kind of lazy construction of loggers, and I think a decent potential for confusion for mutable loggers. The main concern I have is that this changes the constructor API for ABCI clients. I think this is fine, and I suspect that as we plumb contexts through, and make changes to the RPC services there'll be a number of similar sorts of changes to various (quasi) public interfaces, which I think we should welcome.
Application BlockChain Interface (ABCI)
Blockchains are systems for multi-master state machine replication. ABCI is an interface that defines the boundary between the replication engine (the blockchain), and the state machine (the application). Using a socket protocol, a consensus engine running in one process can manage an application state running in another.
Previously, the ABCI was referred to as TMSP.
The community has provided a number of additional implementations, see the Tendermint Ecosystem
Installation & Usage
To get up and running quickly, see the getting started guide along with the abci-cli documentation which will go through the examples found in the examples directory.
Specification
A detailed description of the ABCI methods and message types is contained in:
Protocol Buffers
To compile the protobuf file, run (from the root of the repo):
make protoc_abci
See protoc --help and the Protocol Buffers site
for details on compiling for other languages. Note we also include a GRPC
service definition.