集满2*f+1的Commit包后，直接将本地缓 存的最新区块提交到数据库。 ../../../_images/pbft_process.png 下图详细介绍了PBFT各个阶段的具体流程： graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef 对象。 每个预编译合约对象都会实现call接口，预编译合约的具体逻辑在该接 口中实现。 call根据交易的abi编码，获取到Function Selector和参数，然后执行对 应的逻辑。 graph TB Start(开始) --> branch1{预编译合约} branch1 --> |是|op1[根据地址获 取合约对象] branch1 --> |否|op2[EVM] op1 --> op3[解析调用函数及参数] 查询 获取）。若检查有权限，则执行写操作，交易正常执行；若检查无权限，则 拒绝写操作，返回无权限信息。如果判断操作方式为读操作，则不检查权限 信息，正常执行读操作，返回查询数据。流程图如下。 graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef

提交区块的状态，开始广播Commit包； Commit：负责收集Commit包，某节点收集满2*f+1的Commit包后，直接将本地缓 存的最新区块提交到数据库。 下图详细介绍了PBFT各个阶段的具体流程： graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef 对象。 每个预编译合约对象都会实现call接口，预编译合约的具体逻辑在该接 口中实现。 call根据交易的abi编码，获取到Function Selector和参数，然后执行对 应的逻辑。 graph TB Start(开始) --> branch1{预编译合约} branch1 --> |是|op1[根据地址获 取合约对象] branch1 --> |否|op2[EVM] op1 --> op3[解析调用函数及参数] 查询 获取）。若检查有权限，则执行写操作，交易正常执行；若检查无权限，则 拒绝写操作，返回无权限信息。如果判断操作方式为读操作，则不检查权限 信息，正常执行读操作，返回查询数据。流程图如下。 graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef

提交区块的状态，开始广播Commit包； Commit：负责收集Commit包，某节点收集满2*f+1的Commit包后，直接将本地缓 存的最新区块提交到数据库。 下图详细介绍了PBFT各个阶段的具体流程： graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef 对象。 每个预编译合约对象都会实现call接口，预编译合约的具体逻辑在该接 口中实现。 call根据交易的abi编码，获取到Function Selector和参数，然后执行对 应的逻辑。 graph TB Start(开始) --> branch1{预编译合约} branch1 --> |是|op1[根据地址获 取合约对象] branch1 --> |否|op2[EVM] op1 --> op3[解析调用函数及参数] 查询 获取）。若检查有权限，则执行写操作，交易正常执行；若检查无权限，则 拒绝写操作，返回无权限信息。如果判断操作方式为读操作，则不检查权限 信息，正常执行读操作，返回查询数据。流程图如下。 graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef

提交区块的状态，开始广播Commit包； Commit：负责收集Commit包，某节点收集满2*f+1的Commit包后，直接将本地缓 存的最新区块提交到数据库。 下图详细介绍了PBFT各个阶段的具体流程： graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef 对象。 每个预编译合约对象都会实现call接口，预编译合约的具体逻辑在该接 口中实现。 call根据交易的abi编码，获取到Function Selector和参数，然后执行对 应的逻辑。 graph TB Start(开始) --> branch1{预编译合约} branch1 --> |是|op1[根据地址获 取合约对象] branch1 --> |否|op2[EVM] op1 --> op3[解析调用函数及参数] 查询 获取）。若检查有权限，则执行写操作，交易正常执行；若检查无权限，则 拒绝写操作，返回无权限信息。如果判断操作方式为读操作，则不检查权限 信息，正常执行读操作，返回查询数据。流程图如下。 graph TB classDef blue fill:#4C84FF,stroke:#4C84FF,stroke-width:4px, font:#1D263F, text-align:center; classDef

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka

Hyperledger Fabric – it is pluggable. The world state database could be a relational data store, or a graph store, or a temporal database. This provides great flexibility in the types of ledger states that crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka