Most of our capabilities tend to be self issued. For such capabilities we use did:key: of the issuer as a resource as that is pretty much only "resource" that user can credibly claim that would not:
Require out of bound checks
Capability specific validation logic (e.g. certain signatures)
This approach leads to lot of redundant with fields which are the same as the token issuer. What if we made with optional field and when omitted implied issuer did ?
Most of our capabilities tend to be self issued. For such capabilities we use
did:key:
of the issuer as a resource as that is pretty much only "resource" that user can credibly claim that would not:This approach leads to lot of redundant
with
fields which are the same as the tokenissuer
. What if we madewith
optional field and when omitted implied issuer did ?