Anatomy of the Provenance Blockchain Application
Provenance Blockchain is an ecosystem for application-specific financial services blockchain applications.
The Provenance Blockchain SDK enables developers to build modules that implement the business logic of a financial services blockchain. In other words, SDK modules implement the bulk of the logic of the blockchain, while the core does the wiring and enables modules to be composed together. The end goal is to build a robust ecosystem of open-source SDK modules, making it increasingly easier to build complex blockchain applications.
While the Cosmos SDK documentation does a good job explaining the concepts of an application-specific blockchain, it is helpful to drill down into the core concepts and get hands-on. That's what this section aims to do.
The Provenance Blockchain core application-specific blockchain is effectively encompassed by the
provenancedbinary - which is both a client and a daemon process. It is the core process of the Provenance Blockchain. Participants in the network run this process to host a node (initialize their state-machine), connect with other nodes, and update their state-machine as new blocks come in.
As shown in the Provenance Blockchain Node Components diagram, the Provenance Blockchain application-specific blockchain is composed of multiple components all running a single binary (
provenanced) on a machine (node):
Provenance Blockchain Node Components
The Tendermint BFT State Machine Replication component (again, compiled into the
provenancedbinary) handles state machine replication, distribution, consensus, and networking.
The Provenance Blockchain SDK, built on top of the Cosmos SDK, manages a state-machine and key-value store. The Provenanced SDK includes base modules from the Cosmos SDK as well as custom modules like Metadata and Marker for financial-services related functionality. The Provenance Blockchain SDK component communicates with Tendermint using the ABCI. ABCI is a Tendermint construct and serves as the interface between Tendermint (a state-machine replication engine) and the Provenance Blockchain application (the actual state machine and blockchain implementation).
provenancedbinary encapsulates the Provenance Blockchain SDK (and inheritied Cosmos SDK) and Tendermint engine. Cosmovisor is a small process manager around
provenancedthat monitors the governance module via stdout to see if there's a chain upgrade proposal coming in. If it sees a proposal that gets approved it can be run manually or automatically to download the new code, stop the node, run the migration script, replace the node binary, and start with the new genesis file.
provenancedbinary also communicates with and manages external (to the binary) components on the node including:
- A Keyring backend which holds the private/public keypairs used to interact with a node. For instance, a validator key needs to be set up before running the blockchain node so that blocks can be correctly signed. The private key can be stored in different locations, called "backends". Backends may include a file, the operating system's own key storage, or a Hardware Security Module (preferred for Validators).
- Config Files and Genesis App files that define the specific configuration settings of the node and genesis data consumed and stored as part of the blockchain node during initial startup.
- An Upgrades directory used by the
cosmovisorprocess manager during chain upgrades.
- A Data directory where blockchain state is stored. This is effectively the key-value storage used by the core application and modules.
External applications communicate with a
provenancednode instance using
gRPClayer of the
provenancedapplication exposes the Provenance Blockchain modules to external applications. Thus, the core blockchain modules that implement the business logic of the blockchain are available via the
gRPCinterface provides access to the Provenance Blockchain modules, the Event Manager dispatches blockchain transaction events. External applications can subscribe to events like token or coin transfers, metadata updates, and governance proposals.