-
-
DIDDoc must support service endpoints.
The standard practice would be to use did:peer with numalgo 2 which is effectively a did:key with a service endpoint
-
An attached DidDoc in a DidEx Response sent by AcaPy is not signed by the owner of the Did within the Doc. Instead it is signed by whoever created the attachment. Is that ok?
A rough DidEx Responde…
-
It is my contention that the following should be a success condition of our work: the SDS spec defines the minimum features and components required for all SDS implementations to be so unified and int…
-
Per https://discord.com/channels/937858703112155166/1118914862106542100/1121125803342692483, there is a need to support signing with an so we can cleanly attach to DWNs.
The alternatives include:
…
-
While writing tests for the connection protocol in the test suite, I made a few observations regarding DID Documents as described in the DIDDoc conventions RFC and Cross domain messaging RFC and how t…
-
I can issue a VC and also a VP containing the VC, but while verifying, I come across the following error in the verification result:
`{"verified":false,"credentials":{"verified":false,"results":[{"…
-
Currently, we have some `From` implementations which should be converted to `TryFrom` as they may fail, e.g. `impl From for DidDoc`.
-
## What
> Give a brief description of the objective of this issue. What needs to be discussed?
The current produced types for TS is not following standards of the spec.
I just touched upon the DIDD…
-
The blockchain sometimes allows use of DIDs that have not been registered to the `did` module. ~~An example of this is project creation, where the project creator (`senderDid`) does not need to be reg…