ChainAgnostic
Feedback on a DID method that standardises CAIP-19 assets.
Hello people!
We at KILT, a digital identity infrastructure, are undertaking a big effort in trying to build a trust layer for assets by leveraging our existing trusted identity infrastructure. In short, we allow attesters to issue digital verifiable credentials to people that request them, with everyone being identified by a KILT Decentralized Identifier (DID).
We are now trying to move into the asset world, where entities might not necessarily be active (i.e., capable of interacting themselves with other entities). And since we define an identity as the combination of an identifier and some information attached to such identifier (the aforementioned credentials), we are trying to come up with a way to define unique and global asset identifiers.
CAIP-19 represents a very good starting point for this purpose, but we think that it lacks the "last mile" effort, being CAIP-19 just identifier that does not define any way to get useful information from such identifier.
As we are more or less deep into DIDs and Verifiable Credentials (VC), we are trying to come up with a DID definition representing a thin wrapper around CAIP-19 identifiers, but that would provide all the capabilities DIDs provide, including a standardised resolution process, a uniform representation, and the flexibility of JSON-LD. An example of that would be the possibility to resolve an Asset DID at a given block hash, without having to make the block hash part of the identifier (as there is an ongoing discussion about the subject). Another potential advantage, would be the possibility to use information specified in the DID specification, such as the alsoKnownAs, canonicalId, and equivalentId properties, to link multiple CAIP19-based assets together and support inter-chain asset teleports, where needed.
I am therefore asking the CAIP community to provide (no rush 😃) feedback to our ongoing standardisation effort for the new Asset DID method, of which a draft (still a PR) can be found here -> https://github.com/KILTprotocol/specifications/blob/76f66d8f8ef75fbdc6999914056bb7a7b18c5340/docs/did/asset-did-spec.md. Not sure if this is the best place, but I am willing to move the conversation over some other channel, if needed.
The initial version of the spec is willingly basic, because we want to avoid making it KILT-centric and would love this to be a community effort to write something that is extensible and flexible enough to accommodate multiple resolvers and multiple use cases.
Thanks in advanced for any feedback!
