Vishwas1
commented
2 years ago DID on IBC related discussion: https://github.com/cosmos/cosmos-sdk/discussions/8431
- As the IBC ecosystem evolves, there will be many different applications and many different entities that will want to interact with those IBC applications. The basic use case is that a single user wants to authenticate an IBC packet being sent.
- The basic use case is that a single user wants to authenticate an IBC packet being sent. This is simple enough to implement with the x/auth module in the SDK.
- However, the set of entities who wish to send IBC packets will naturally become more complex and diverse as the set of IBC applications becomes more complex and diverse
- . For example, a tendermint validator set may want to be able to authenticate and send IBC packets.
- All of these entities will need to implement their own form of authentication that must pass in order to send the IBC packet.
If each authentication scheme is implemented in a different way, then IBC applications that need to process an "authorizing party" before sending the IBC packet will have to explicitly enable each authentication scheme.
Instead a uniform authentication layer that sits between specific authentication schemes and their end applications will provide a uniform interface across which entities can authenticate interactions with IBC applications
Instead a uniform authentication layer that sits between specific authentication schemes and their end applications will provide a uniform interface across which entities can authenticate interactions with IBC applications
The DID document for an internet user might include their public keys and which public key should be used for which interaction. Perhaps the DID document specifies an ED25519 PublicKey for authenticating web log-ins, and a JsonWebKey2020 for negotiating secret keys for communication. The (DID, DID Document) pair is maintained on a public ledger and allows the DID document to be updated, allowing other parties to authenticate interactions from the DID subject even as public keys are rotated.
Pre-requisite
Basic of IBC #11
Objective: Write ICS spec for DID transfer over IBC
Example Specs: