Hyperledger Fabric和Hyperledger Indy之间的交叉账本通信 [英] Cross-ledger communication between Hyperledger Fabric and Hyperledger Indy

问题描述

是否可以在超级账本结构和Indy之间进行跨账目身份管理?

Is it possible to have a cross-ledger identity management between hyperledger fabric and indy?

是否可以在Hyperledger Fabric和Hyperledger Indy之间进行通信?

Is it possible to communicate between Hyperledger Fabric and Hyperledger Indy?

我可以从Fabric中读取数据并将其存储在Indy中，反之亦然吗? 我的想法是使用Indy对身份进行身份验证，并使用Fabric使用所传达的凭据通过链码存储数据.是Quilt工具吗?

Can I read the data from Fabric and store it in Indy and vice-versa? My idea is to use Indy to authenticate identities and use Fabric to store data through chaincodes using the communicated credentials. Is Quilt the tool for it?

推荐答案

Hyperledger Indy是一种去中心化的身份系统，而Hyperledger Fabric是一种通用的去中心化分类帐，可以适用于各种用例.您希望将Indy用于本身在Fabric上运行的系统身份验证目的.

Hyperledger Indy is a decentralised identity system, while Hyperledger Fabric is a general purpose decentralised ledger that can be adapted for a variety of use cases. You wish to use Indy for your systems authentication purposes which itself runs on Fabric.

将Hyperledger Indy视为独立的注册表.分类帐用于存储DID和声明，可以在本地部署，也可以使用 sovrin 测试网.为了进行测试，您可以启动Indy节点的本地池.遵循入门指南，然后查看角色部分.这将为您提供有关如何引导Indy网络的想法.

Consider Hyperledger Indy as an independent registry. The ledger is used for storing the DID's and claims, and can be deployed locally or you can also make use of the sovrin testnet. For testing, you can start a local pool of Indy nodes. Follow the getting started guide and check out the roles section. This will give you an idea on how to bootstrap your Indy network.

完成Indy池的部署后，Fabric末尾的过程非常简单.一旦调用了链码，它便可以使用提供的API对Indy池进行适当的身份验证或授权调用. Indy-SDK .因此，例如，当您调用链式代码以在Fabric中创建新频道时，将调用插入Indy池以验证参与者的身份.

Once you are done deploying the Indy pool, the procedure from the end of Fabric is quite simple. Once your chaincode is invoked, it can make the appropriate authentication or authorisation calls to your Indy pool using the API provided by Indy-SDK. So for example when you invoke the chaincode for creating a new channel in Fabric, insert calls to the Indy pool to verify the identity of the participants.

或者，Indy声明使用代理，这将简化Indy池上用户的所有流程处理，他们提供了参考实现.代理只是充当中介，因此，无论您的系统部署了哪种技术，都可以调用该代理以进行身份​​验证或授权.

Alternatively, Indy states the use of agents which will facilitate all the process handling for a user on the Indy pool, they have provided a reference implementation for the same. The agents just act as intermediateries, so regardless of what technology your system is deployed on, you can make calls to the agent for authentication or authorisation purposes.

这篇关于Hyperledger Fabric和Hyperledger Indy之间的交叉账本通信的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！