-
A reoccurring issue has been how to sufficiently represent inline keys in a concise syntax whilst preserving the required information around a public keys encoding and underlying type.
The [did:key…
-
### Proposed Template
[DIF User Group Charter Template - 20240205](https://docs.google.com/document/d/1xS0tDieZbso-mNVCH-0CNHdafIeNChsPVM1Q5-IMYT4/edit?usp=drive_link)
### Template Source
Reverse eng…
-
Consider:
`did:example:123?q1=1&q2=2#fragment` => did document.
should didDocument.id === `did:example:123?q1=1&q2=2` or `did:example:123` ?
this is particularly concerning for interactions w…
-
Goal: VC HTTP APIs that enable the exchange of verifiable presentations between back-end services. This exchange should work for both scenarios that require a User UI and also for those that do not. A…
-
Hi, I have a question about thread branching and its particular usage in did-exchange https://github.com/hyperledger/aries-rfcs/blob/main/features/0023-did-exchange/README.md
So according to the ge…
-
While reviewing the spec, I noticed that it [says](https://identity.foundation/didcomm-messaging/spec/#perfect-forward-secrecy):
> Due to the triple Key Derivation algorithm used in ECDH-1PU, all m…
-
I was surprised to read the editor's note from Sept. 2022. I see it was merged without feedback (including from me -- I wasn't aware of it). I'd like to see it removed on the basis that it steers peo…
-
After reading through #243 entirely, I've come to realize it's probably best if we get @AnomalRoil to help us out with defining explicit security requirements for the **envelope layer only**. I think …
-
The descriptions about selective disclosure in the W3C Verifiable Credentials specification could be extended by mentioning [SD-JWT (Selective Disclosure JWT)](https://www.ietf.org/id/draft-fett-oauth…
-
In AFJ we've finally updated the default didcomm mime type from V0 (`application/ssi-agent-wire`) to V1 (`application/didcomm-envelope-enc`, at least that what we use for v1).
However looking at [R…