超级账本中的PBFT算法 [英] PBFT algorithm in hyperledger

查看:286
本文介绍了超级账本中的PBFT算法的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

谁能详细解释 PBFT算法,而没有给出相同的任何链接?以及它在 hyperledger 中的工作方式.因此,一旦交易发送到blockchain:

Can anyone explain PBFT Algorithm in detail without giving any link for the same? And how it works in hyperledger. So, once the transaction is sent to the blockchain:

  1. 谁验证交易?

  1. Who validates the transaction?

如何在交易中达成共识?

How the consensus is achieved on the transaction?

交易如何提交到区块链?

How the transaction is committed to the blockchain?

推荐答案

超级账本"是Linux基金会下的一个区块链财团.目前在Hyperledger下至少有4种不同的区块链框架实现:

"Hyperledger" is a blockchain consortium under The Linux Foundation. Currently there are at least 4 different implementations of blockchain frameworks under Hyperledger:

  • Fabric(IBM)
  • Corda(R3)
  • 伊洛哈(Iroha)
  • Sawtooth Lake(Intel)

在Fabric v0.6中<​​/strong>:

In Fabric v0.6:

所有验证对等方之间保持开放连接.您可以向其中任何一个提交事务,该事务将广播到网络中的其他对等方.一位同行被选为领导者".在将要生成新块的时刻:

All validation peers keep open connection to each other. You can submit your transaction to any of them, and this transaction will be broadcasted to other peers in the network. One of peer is elected as "leader". At the moment when a new block is going to be generated:

  1. 领导者订购应包含在区块中的交易候选者,并将此订购交易列表广播到网络中的所有其他验证对等方.
  2. 每个验证对等方收到交易的有序列表时,每个验证对等方将执行以下操作:
  1. The leader orders the transactions candidates that should be included in a block, and broadcasts this list of ordered transactions to all other validation peers in the network.
  2. When each of the Validation Peers receives the ordered list of transactions, each validation peer does the following:
  1. 它开始一个接一个地执行订购的交易.
  2. 所有交易一旦执行,它将为新创建的区块计算哈希码(该哈希码包括已执行交易的哈希和世界的最终状态).
  3. 然后将其答案(生成的哈希码)广播到网络中的其他对等端,并开始计算来自它们的响应.
  4. 如果发现所有验证对等点中有2/3具有相同的哈希码,则会将新块提交到其分类帐的本地副本中.

在Fabric v1.0中:

此版本仍在开发中.在v1中,它不是领导者",单独的服务"订购者"负责块中的交易订单.该服务是可插拔的,并宣布将提供3种不同的选择:

This version is still in development. In v1 the is no "leader", separate service "Orderer" is responsible for transactions order in a block. This service is pluggable and announced that the will be 3 different options:

  1. Solo-单个流程负责订购
  2. Kafka订购者-利用Kafka pubsub系统执行订购
  3. PBFT-尚未实现.

在科达(Corda):

未使用PBFT.此实现使用另一种体系结构方法.

PBFT is not used. This implementation uses another architecture approach.

这篇关于超级账本中的PBFT算法的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆