You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
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?
@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
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
The text was updated successfully, but these errors were encountered: