Application BlockChain Interface (ABCI)

Blockchains are a system 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). By using a socket protocol, we enable a consensus engine running in one process to manage an application state running in another.

For more information on ABCI, motivations, and tutorials, please visit our blog post, and the more detailed application developer's guide.

Previously, the ABCI was referred to as TMSP.

Other implementations:

• C++ cpp-tmsp by Martin Dyring-Andersen
• JavaScript js-abci
• Java jABCI
• Erlang abci_server by Krzysztof Jurewicz

Specification

The primary specification is made using Protocol Buffers. To build it, run

make protoc

See protoc --help and the Protocol Buffers site for details on compiling for other languages. Note we also include a GRPC service definition.

For the specification as an interface in Go, see the types/application.go file.

Message Types

ABCI requests/responses are defined as simple Protobuf messages in this schema file. TendermintCore sends the requests, and the ABCI application sends the responses. Here, we describe the requests and responses as function arguments and return values, and make some notes about usage:

DeliverTx

• Arguments:
  • Data ([]byte): The request transaction bytes
• Returns:
  • Code (uint32): Response code
  • Data ([]byte): Result bytes, if any
  • Log (string): Debug or error message
• Usage:
  Append and run a transaction. If the transaction is valid, returns CodeType.OK

CheckTx

• Arguments:

  • Data ([]byte): The request transaction bytes

• Returns:

  • Code (uint32): Response code
  • Data ([]byte): Result bytes, if any
  • Log (string): Debug or error message

• Usage:
  Validate a mempool transaction, prior to broadcasting or proposing. This message should not mutate the main state, but application developers may want to keep a separate CheckTx state that gets reset upon Commit.

  CheckTx can happen interspersed with DeliverTx, but they happen on different ABCI connections - CheckTx from the mempool connection, and DeliverTx from the consensus connection. During Commit, the mempool is locked, so you can reset the mempool state to the latest state after running all those DeliverTxs, and then the mempool will re-run whatever txs it has against that latest mempool state.

  Transactions are first run through CheckTx before broadcast to peers in the mempool layer. You can make CheckTx semi-stateful and clear the state upon Commit or BeginBlock, to allow for dependent sequences of transactions in the same block.

Commit

• Returns:
  • Data ([]byte): The Merkle root hash
  • Log (string): Debug or error message
• Usage:
  Return a Merkle root hash of the application state.

Query

• Arguments:
  • Data ([]byte): Raw query bytes. Can be used with or in lieu of Path.
  • Path (string): Path of request, like an HTTP GET path. Can be used with or in liue of Data.
    • Apps MUST interpret '/store' as a query by key on the underlying store. The key SHOULD be specified in the Data field.
    • Apps SHOULD allow queries over specific types like '/accounts/...' or '/votes/...'
  • Height (uint64): The block height for which you want the query (default=0 returns data for the latest committed block). Note that this is the height of the block containing the application's Merkle root hash, which represents the state as it was after committing the block at Height-1
  • Prove (bool): Return Merkle proof with response if possible
• Returns:
  • Code (uint32): Response code
  • Key ([]byte): The key of the matching data
  • Value ([]byte): The value of the matching data
  • Proof ([]byte): Proof for the data, if requested
  • Height (uint64): The block height from which data was derived. Note that this is the height of the block containing the application's Merkle root hash, which represents the state as it was after committing the block at Height-1
  • Log (string): Debug or error message Please note The current implementation of go-merkle doesn't support querying proofs from past blocks, so for the present moment, any height other than 0 will return an error (recall height=0 defaults to latest block). Hopefully this will be improved soon(ish)

Info

• Returns:

  • Data (string): Some arbitrary information
  • Version (Version): Version information
  • LastBlockHeight (uint64): Latest block for which the app has called Commit
  • LastBlockAppHash ([]byte): Latest result of Commit

• Usage:
  Return information about the application state. Used to sync the app with Tendermint on crash/restart.

SetOption

• Arguments:
  • Key (string): Key to set
  • Value (string): Value to set for key
• Returns:
  • Log (string): Debug or error message
• Usage:
  Set application options. E.g. Key="mode", Value="mempool" for a mempool connection, or Key="mode", Value="consensus" for a consensus connection. Other options are application specific.

InitChain

• Arguments:
  • Validators ([]Validator): Initial genesis validators
• Usage:
  Called once upon genesis

BeginBlock

• Arguments:
  • Hash ([]byte): The block's hash. This can be derived from the block header.
  • Header (struct{}): The block header
• Usage:
  Signals the beginning of a new block. Called prior to any DeliverTxs. The header is expected to at least contain the Height.

EndBlock

• Arguments:
  • Height (uint64): The block height that ended
• Returns:
  • Diffs ([]Validator): Changed validators with new voting powers (0 to remove)
• Usage:
  Signals the end of a block. Called prior to each Commit after all transactions. Validator set is updated with the result.

Echo

• Arguments:
  • Message (string): A string to echo back
• Returns:
  • Message (string): The input string
• Usage:
  
  • Echo a string to test an abci client/server implementation

Flush

• Usage:
  
  • Signals that messages queued on the client should be flushed to the server. It is called periodically by the client implementation to ensure asynchronous requests are actually sent, and is called immediately to make a synchronous request, which returns when the Flush response comes back.

Implementation

We provide three implementations of the ABCI in Go:

1. ABCI-socket
2. GRPC
3. Golang in-process

Socket

ABCI is best implemented as a streaming protocol. The socket implementation provides for asynchronous, ordered message passing over unix or tcp. Messages are serialized using Protobuf3 and length-prefixed. Protobuf3 doesn't have an official length-prefix standard, so we use our own. The first byte represents the length of the big-endian encoded length.

For example, if the Protobuf3 encoded ABCI message is 0xDEADBEEF (4 bytes), the length-prefixed message is 0x0104DEADBEEF. If the Protobuf3 encoded ABCI message is 65535 bytes long, the length-prefixed message would be like 0x02FFFF....

GRPC

GRPC is an rpc framework native to Protocol Buffers with support in many languages. Implementing the ABCI using GRPC can allow for faster prototyping, but is expected to be much slower than the ordered, asynchronous socket protocol.

Note the length-prefixing used in the socket implementation does not apply for GRPC.

In Process

The simplest implementation just uses function calls within Go. This means ABCI applications written in Golang can be compiled with TendermintCore and run as a single binary.

Tools and Apps

The abci-cli tool wraps any ABCI client and can be used for probing/testing an ABCI application. See the guide for more details.

Multiple example apps are included:

• the counter application, which illustrates nonce checking in txs
• the dummy application, which illustrates a simple key-value merkle tree
• the dummy --persistent application, which augments the dummy with persistence and validator set changes