Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Improvement to TrustID ecosystem #40

Open
Zzocker opened this issue May 17, 2021 · 2 comments
Open

Improvement to TrustID ecosystem #40

Zzocker opened this issue May 17, 2021 · 2 comments
Assignees

Comments

@Zzocker
Copy link

Zzocker commented May 17, 2021

I have some query and suggestions regarding this project, specifically about the use of trustID in HL fabric application. I know one of the aims of this project is to provide a single digital identity for all types of blockchain.

Question:
Since invoke (worldstate update request) chaincode is not possible with chaincode installed on different channels. And trustID fabric chaincode uses InvokeChaincode(chaincodeName string, args [][]byte, channel string) pb.Response to invoke services. So to use dids stored on blockchain on different channels , one will have to install trustID chaincode to all these channels and manage the same dids documents on all these channels. To manage the same didis on many channels, trustID sdk will have to make atomic requests (CRUD on DIDs) to fabric. This atomic request won’t be easy to achieve. Please let me know if I am right till now, or am I missing something?

@mtnieto

@c20liu
Copy link

c20liu commented Jul 28, 2021

@Zzocker
I agree with you that it is impossible to call updates across channels. If the application contract is updated, it can only be restricted to the same channel. In addition, the code seems to require that each application contract function be bound to a service, otherwise invoke will report an error

@c20liu
Copy link

c20liu commented Jul 29, 2021

@Zzocker I am also learning the implementation of DID on Fabric, do you know what other projects can be studied, thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants