System Chain
Contains a configuration block defining the network at a system level. The system chain lives within the ordering service, and similar to a channel, has an initial configuration containing information such as: MSP information, policies, and configuration details. Any change to the overall network (e.g. a new org joining or a new ordering node being added) will result in a new configuration block being added to the system chain.
The system chain can be thought of as the common binding for a channel or group of channels. For instance, a collection of financial institutions may form a consortium (represented through the system chain), and then proceed to create channels relative to their aligned and varying business agendas.
例如，一組金融機構可以組成一個財團（通過系統鏈代表），然後相對於它們一致且變化的業務議程來創建渠道。
目前通道分爲系統通道（System Channel）和應用通道（Application Channel）。排序節點通過系統通道來管理應用通道，用戶的交易信息通過應用通道傳遞。對一般用戶來說，通道是指應用通道。
Genesis Block
The configuration block that initializes the ordering service, or serves as the first block on a chain.
Configuration Block
Contains the configuration data defining members and policies for a system chain (ordering service) or channel. Any configuration modifications to a channel or overall network (e.g. a member leaving or joining) will result in a new configuration block being appended to the appropriate chain. This block will contain the contents of the genesis block, plus the delta.
Concurrency Control Version Check
Concurrency Control Version Check is a method of keeping ledger state in sync across peers on a channel. Peers execute transactions in parallel, and before committing to the ledger, peers check whether the state read at the time the transaction was executed has been modified. If the data read for the transaction has changed between execution time and commit time, then a Concurrency Control Version Check violation has occurred, and the transaction is marked as invalid on the ledger and values are not updated in the state database.