Closed arnabghose997 closed 1 year ago
@Vishwas1 There is one change that is needed to be pushed, based on an observation from running a Client Side Application for signing the DID Document using Metamask
The personal_sign
method only accepts the message as a string input, which is why we JSON.stringify()
the DID Doc before passing it to the method. However, on the blockchain end, in its current implementation, the serialisation of DID Doc happens based binary encoding, because of which the message is interprated differently here.
In order to solve it, the didDoc object on hid-node
has to serialised using JSON Marshaller, instead of Proto Marshaller. This will be only specific for Ethereum based addresses only.
personal_sign
(https://docs.metamask.io/guide/signing-data.html#personal-sign) support has been added as a clientSpec for SSI Docs.
Closes: https://github.com/hypersign-protocol/hid-node/issues/57
This PR aims to introduce support for
blockchainAccountId
, where users can pass blockchain addresses instead of a public key, to validate a recoverable signature. This PR aims to support only EVM based address at the moment.The e2e test report for
x/ssi
module is attached. Test CasesTC-10
andTC-11
has been written for the feature of this PR e2e_ssi_module_test_report.txt