所有对等节点是否都在 Hyperledger Fabric 中保存所有用户公钥？
我知道用户在加入 Hyperledger Fabric 网络之前必须获得证书颁发机构（CA）创建的身份。 CA 将为用户创建公钥和私钥。当用户向网络中的对等节点提交交易时，该交易将使用用户的私钥进行签名，并且对等节点将使用用户的公钥确认该交易，以确认该交易是由用户发起的首先通过CA（如果我的理解错误请纠正我）。
例如，在一个网络中，有 OrgA、Org B 和 Org C。Org A 有 100 个对等节点和 1,000,000 个用户。如果这 100 个对等节点中的每一个都必须保存 1,000,000 个用户的公钥，那么这不是一种数据库资源的浪费，因为每个节点都必须保存这 1,000,000 个用户的公钥和信息，而他们很可能可以分开保存公共密钥关键是因为这些对等节点来自同一组织？
I know that a user must get an identity created by Certificate Authority(CA) before they join Hyperledger Fabric Network. The CA will create a public key and a private key to the user. When the user submits a transaction to the peer node in the network, the transaction will be signed using private key of the user and the peer node will confirm the transaction by using the public key of the user to confirm the transaction is initiated by a user that had gone through CA first(Correct me if my understanding is wrong).
For example in a network there is OrgA, Org B and Org C. Org A has 100 peer nodes and 1,000,000 user. If each of those 100 peer nodes has to keep 1,000,000 user's public key, isn't it kind of a waste of database resources because each of them has to keep those 1,000,000 user's public key and information when most probably they could divide the keeping of public key since these peer nodes are from the same organization?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
证书中有公钥。对等节点不需要存储公钥，它必须信任 RCA（根证书颁发机构）证书。如果用户的证书是由可信CA生成的，则该用户的证书是可信的。因此对等节点可以使用证书上的公钥来验证交易。
A certificate has public key in it. Peer Node does not need to store public key tho, it has to trusts the RCA (Root Certificate Authority) cert. If the cert of a user is generated by the trusted CA, the user's cert is trusted. So the peer node can use the public key on the cert to verify transaction.
用户将从证书颁发机构（CA）获得在网络中使用的身份（数字证书）。 CA将使用其私钥为用户创建数字证书。如果对等节点保存了CA的公钥，则它们可以验证数字证书的有效性。这样，每个对等节点不需要保存用户的所有公钥。
这里有一个关于数字证书制作的链接。我认为这个流程与 Hyperledger CA 的工作原理相同。
http://docs.blueworx.com/BVR/InfoCenter/V6.1/help/index.jsp?topic=%2Fcom.ibm.wvraix.voip.doc%2Fq009870_.html
User will get identity(digital certificate) to be used in the network from Certificate Authority(CA). CA will use its private key to create digital certificate for the user. If peer node keeps CA's public key, they can verify the validness of the digital certificate. Thus, each peer node doesn't need to keep all public key of the user.
Here's a link about the production of digital certificate. I think this flow works the same with Hyperledger CA.
http://docs.blueworx.com/BVR/InfoCenter/V6.1/help/index.jsp?topic=%2Fcom.ibm.wvraix.voip.doc%2Fq009870_.html