Application Architecture Guide
Here we provide a brief guide on the recommended architecture of a CometBFT blockchain application.
We distinguish here between two forms of “application”. The first is the end-user application, like a desktop-based wallet app that a user downloads, which is where the user actually interacts with the system. The other is the ABCI application, which is the logic that actually runs on the blockchain. Transactions sent by an end-user application are ultimately processed by the ABCI application after being committed by CometBFT.
The end-user application communicates with a REST API exposed by the application. The application runs CometBFT nodes and verifies CometBFT light-client proofs through the CometBFT RPC. The CometBFT process communicates with a local ABCI application, where the user query or transaction is actually processed.
The ABCI application must be a deterministic result of the CometBFT consensus - any external influence on the application state that didn’t come through CometBFT could cause a consensus failure. Thus nothing should communicate with the ABCI application except CometBFT via ABCI.
If the ABCI application is written in Go, it can be compiled into the CometBFT binary. Otherwise, it should use a unix socket to communicate with CometBFT. If it’s necessary to use TCP, extra care must be taken to encrypt and authenticate the connection.
All reads from the ABCI application happen through the CometBFT /abci_query
endpoint. All writes to the ABCI application happen through the CometBFT
/broadcast_tx_* endpoints.
The Light-Client Daemon is what provides light clients (end users) with nearly all the security of a full node. It formats and broadcasts transactions, and verifies proofs of queries and transaction results. Note that it need not be a daemon - the Light-Client logic could instead be implemented in the same process as the end-user application.
Note for those ABCI applications with weaker security requirements, the functionality of the Light-Client Daemon can be moved into the ABCI application process itself. That said, exposing the ABCI application process to anything besides CometBFT over ABCI requires extreme caution, as all transactions, and possibly all queries, should still pass through CometBFT.
See the following for more extensive documentation:
