...
| TERMS | Under Review | Working | Approved |
|---|---|---|---|
| AML | X | ||
| Application | X | ||
| Block | X | ||
| Chain | X | ||
| Chaincode | X | ||
| ERC Token Standard | X | ||
| Genesis Block | X | ||
| Stablecoin | X | ||
| BFT consensus | X | ||
Business process flows: These are the commons steps in a business process, or supply chain process. In the solar project finance example page, these are Identify a project, Originate a project, Raise the Funds, Build the project, and Run the project. The application environment is specifically aligned with the processes since they provide services across
Governance Framework: This pertains to the Governance Frameworks in common Trust Over Ip stacks.
DIDs and Agent Credentials: Common ID layer and verifiable credential layer that determined who is who in the common network, and what data can be shared between each agent. Tools for this are provided from Hyperledger Indy (DID) and Hyperledger Aries (Agent Credentials).
Common DLT Data Layer: This can be a permissioned ledger that stores data from the network that applications can use for their specific services across the business process flow, granted that they have access from the other applications and the underlying agentes (eg. the user). Such a layer can use Hyperledger Fabric.
Business Protocols and Taxonomies: The common language use by the business process flows can be understood as a shared taxonomy, which defines common schemas and methods. This is business specific.
Client Layer: This layer is a common entry point for every application in the network, it makes it easy for applications to interact with the network and even integrate their own set of network solutions, since application may be leveraging tools from other DLT environments.
Application Environment: These are the actual applications and platform of applications using the network and providing different concrete services to the end-user for their processes. Applications in this model can be proprietary or open source, but require using the open source network to establish the trusted interactions across them.
Term | Status | Definition |
| AML | NEEDS REVIEW | |
Application | NEEDS REVIEW | |
| BLOCK | A block contains one or more transactions stored within the blockchain. Blocks are created by the ordering service, and then validated and committed by peers. Analogy: A block is similar to a page of a ledger. | |
| Blockchain | A block contains an ordered set of transactions. It is cryptographically linked to the preceding block, and in turn it is linked to be subsequent blocks. A blockchain is a list of records (blocks), linked (or chained) chronologically. The first block in such a chain of blocks is called the genesis block. Analogy: a blockchain is similar to a book of records that keeps a log of all transactions ("blocks"), in chronological order. | |
| Chain | The ledger’s chain is a transaction log structured as hash-linked blocks of transactions. Peers receive blocks of transactions from the ordering service, mark the block’s transactions as valid or invalid based on endorsement policies and concurrency violations, and append the block to the hash chain on the peer’s file system. | |
| Chaincode | Embedded logic that encodes the rules for specific types of network transactions. | |
DApp | Decentralized application - Whole or part of logic on a decentralized network; built on a peer-to-peer network like a blockchain; May have their own blockchain. | |
Initiatives | Groups of stakeholders collaborating to educate, develop pilots, & set policy. | |
Blockchain Platform | A decentralized, distributed, immutable ledger. | |
Project | Implementation of an Application, DApp, or Intermediary System. | |
Intermediary System | Standard or specification for data and procedure that may include libraries, protocols, applications; is not a blockchain in and of itself. | |
Private Consortium | Organization members collaborating to set standards, governance, development, and hosting of a private blockchain and its related applications. | |
Public Permissioned Consortium | Organization members collaborating to set standards, governance, development, and hosting of a public permissioned blockchain and its related applications. | |
| Channel | Private blockchain overlay that allows for data confidentiality and isolation. Channels are defined by a Configuration Block | |
| Configuration block | Block that contains the configuration data that defines members and policies for a system chain or channel. | |
| Consensus | General agreement that allows to confirm the correctness and the order of the set of transactions of a specific block. | |
| Smart contract | Decentralized, immutable and deterministic protocols that provide automation in blockchain solutions and allow to remove third-parties and let peer-to-peer interactions. Smart contract activities can be verifiedOnce agreed between the parties and deployed on a distributed ledger, their activities and outcomes can be verified, so they can be trusted by all stakeholders. | |
| Genesis block | First block of a block chain, that initializes the ordering service. | |
| Transaction | A transaction is created when a chaincode is invoked from a client application to read or write data from the ledger. | |
| Smart contract | Code – invoked by a client application external to the blockchain network – that manages access and modifications to a set of key-value pairs in the latest values for all keys included in the chain transaction log via transactions. |
...