search

hypersign-protocol / hid-node

A permissionless blockchain network to manage digital identity and access rights
https://hypersign.id
Apache License 2.0
223 stars 23 forks source link

`clientSpec` needs to specified for every signature #339

Closed arnabghose997 closed 1 year ago

arnabghose997 commented 1 year ago

In the current implementation, clientSpec is being passed as a seperate paramter of RPC Input for DID Doc related transactions. This would be fine, as long as, all required Signatures being passed, are produced using the same clientSpec, which is provided by the user in the RPC param clientSpec.

However, in situations where some signatures are produced from one clientSpec while other signatures are produced from other clientSpec, the program would treat every signature to be produced by the clientSpec provided by the user in the RPC Input.

This issue only applies for DID Doc, as in case of Credential Schema and Credential Status, exactly one signature is passed