DID layer in Cosmos by Hypersign

Hi members, (this is my third post but only one has got approved so far, the last one which I posted under `interchain` category has not yet approved, I am not sure why. I hope this one pass through) I am part of Hypersign team and previously we have introduced our self . We have been building SSI module by following W3C did spec. We also want DIDs to be interoperable over IBC with other zones. At first glance it might look like we are trying to build VDR (verifiable data registry) for DIDs but our long term goal is, in future any existing zone can become registry, all they need is a SSI module enabled. Once everyone has SSI modules enabled, they can exchange DIDs over IBC and get them resolved. Rationale behind this would be, an issuer may exist on any of zones and verifier may exist on the other. The user who have got his verifiable credential issued by an issuer of zone1 can avail services from the other zones (where verifier sits). One of the usecase of this would be, `KYC-zone` may issue KYC credential / whitelist credential to a user and a user may then go trade on a `Dex-Zone`. Due to govt regulation, the Dex-Zone may first ask user to provide the KYC credential…

Excerpt (1196 of 2000 characters). Read the whole post on the forum ↗

Hi Vishwas,

For ref:

IBC Enabled DIDs · Discussion #8431 · cosmos/cosmos-sdk

IBC Enabled DIDs Background Reading https://www.w3.org/TR/did-core/#introduction Context As the IBC ecosystem evolves, there will be many different applications and many different entities that wil...