Hyperledger Fabric的不变性 [英] Immutability in Hyperledger Fabric

问题描述

有人可以解释如何在Hyperledger Fabric中实现不变性吗?如果我们的私人渠道的对等点很少，那么如何保证一侧没有更改分类账中的数据呢?

Can someone explain how the immutability is implemented in Hyperledger Fabric? If we have private channel with little amount of peers, how it can be guaranteed, that one side hasn't changed data in it's ledger?

推荐答案

为确保渠道中没有任何一方以自己的名义篡改数据，您需要提供复杂的认可政策以包括所有必需的参与者并确保他们在认可政策中有足够的代表性.因此，发行新交易的客户必须获得所有利益相关方的认可，从而确保所有人具有相同的一致状态.例如，如果您有两个组织Org1和Org2并且它们彼此不信任，则您要创建背书策略:

In order to guarantee that no party in the channel has tampered data in its own favor you need to present sophisticated endorsement policy to include all required parties and make sure they adequately represented within endorsement policy. Hence making it obligatory for client which issues new transaction to get endorsement from all interested parties, hence ensuring that all have same consistent state. For example if you have two organizations Org1 and Org2 and they do not trust each other, you would like to create endorsement policy:

AND(Org1.memmber, Org2.member)

因此，客户将必须从两个组织的同级收集签注，以认为该交易有效，这些签注必须签名相同的字节，如果数据是伪造的，则不会如此.您可以在官方文档中了解有关认可的更多信息.近期还有关于Fabric体系结构的出版物，对其进行了详细说明.

Therefore client will have to collect endorsements from peers of both organization to consider the transaction valid those endorsement have to sign same bytes, which won't be the case if data was forged. You can read more about endorsements in official documentation. There is also a recent publication of Fabric architecture which explains it in more details.

这篇关于Hyperledger Fabric的不变性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！