问题描述
我一直在研究超级账本结构有一段时间了.我在没有使用 docker 和 5 个对等方的情况下成功安装和形成 Fabric 网络.现在我尝试在网络中设置审计员和非验证对等点.我四处浏览，但找不到任何明确的文件.任何人都可以帮忙吗?
I've been working around hyperledger fabric for a while. I'm successful in install and form network of Fabric without using docker with 5 peers. Now I try to Setup Auditor and non-validationg peers within the network. I surf around ,but cannot find any clear document in this.Can anyone help?
推荐答案
Hyperledger Fabric v1.x 架构中不再存在验证节点的概念.每个对等节点既是验证对等节点又是提交对等节点；区别在于承诺和背书的作用.背书节点实际上将在其文件系统上安装链码，并且他们将执行交易以产生背书".
The notion of a validating peer is no longer existent in Hyperledger Fabric v1.x architecture(s). Every peer node is both a validating and committing peer; the distinction is between the roles of committing and endorsing. Endorsing peers will actually have chaincode installed on their filesystems and they will execute transactions to produce an "endorsement".
为了进一步扩展，账本只存在于渠道的范围内.因此，对等点将订阅"或加入"一个频道，并且通过扩展具有特定于该频道的唯一分类帐.因此，链码状态特定于单个通道，不会跨通道共享(但应注意，您可以在另一个通道上查询链码并将返回值用作交易的输入).这有点跑题了，但还是很重要的一点.
To further expand, ledgers only exist in the purview of channels. As such a peer will "subscribe" or "join" a channel, and by extension have a unique ledger that is specific to that channel. Therefore chaincode state is specific to an individual channel and is not shared across (it should be noted though that you can query chaincode on another channel and use the returned values as inputs for a transaction). That's a bit of a digression, but an important point nonetheless.
要向审计员回答您的问题，有几种可能性.1. 组织可以共享适当的证书，从而允许访问其对等节点.然后审计员可以查询特定渠道的分类账历史.2. 审计员在每个需要概览的通道上维护一个对等节点.审计员不会充当链码交易的背书人，但由于在通道上，会将所有交易提交到其自己的分类账中.
3.审计时，审计员加入通道，接收整个交易历史.检查完成后，审核员将从频道中移除.** 这可能提供了最大的隐私，但随着链码版本的发展以及键/值和函数的发展，这可能会很棘手 **
To answer your question wrt to an auditor, there are a few possibilities. 1. Orgs could share the appropriate certs, thus allowing access to their peer node(s). The auditor could then query ledger history on specific channels.2. An auditor maintains a peer node on each channel that needs overview. The auditor would not act as an endorser for chaincode transactions, but as a result of being on the channel, would commit all transactions to its own ledger.
3. At the time of audit, the auditor joins the channel and receives the entire history of transactions. Once the inspection is complete, auditor is removed from the channel. ** This probably provides the most privacy, but can be tricky as chaincode versions evolve, along with key/vals and functions **
这篇关于Hyperledger Fabric 如何在非权限网络和权限网络中设置Auditor的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！