-
I'm wondering what would be the downsides of using the public DID for connections in case of an agent that acts mainly as an issuer.
I think this could be useful to be implemented as an option to …
-
```
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/resolver/routes.py", line 108, in resolve_did
document = await resolver.resolve(context.profile, did)
…
-
The model specifies `service_dids` and `services`, but the example value in the Open API definition only specifies `service_dids`.
I guess `service_dids` is deprecated. I can't find anything about it…
-
Add a driver that can resolve a domain name to a DID, using the `/.well-known/did-configuration` mechanism:
https://github.com/decentralized-identity/well-known/tree/master/did-configuration
Not…
-
Currently the did:sov diddocs assembled in ACA-Py don't include the `assertionMethod` for the key. This means we can't use it for the default VC proof purpose `assertionMethod` and thus we get an erro…
-
The RFC merely states:
> The `did_doc~attach` contains the DID Doc associated with the DID as a signed attachment. If the DID method for the presented DID is not a peer method and the DID Doc is re…
-
As seen in the didComm example: https://github.com/hyperledger/aries-rfcs/blob/master/features/0067-didcomm-diddoc-conventions/README.md#service-conventions
`recipientKeys` are shown as verificatio…
-
## As an ACA-Py user, I want to receive connection invitations with public DIDs from multiple ledgers, so that I can connect with agents rooted in multiple ledgers.
Replace current Indy ledger reso…
-
Opening this issue to track the unresolved problem of how to respond to a DIDComm message in which the `from` header contains a DID/DID-URL for methods that are self-certifying and do not depend on a …
-
This base class should:
- define a method similar to `async def resolve(did: str) -> DIDDoc`
- extend ABC (Python Abstract Base Class)
- provide a way for the implementing plugin to report whether …