Niels Klomp
Niels Klomp
## What issue is this PR fixing closes #336 and closes #440 ## What is being changed Implement ION DID Provider. Seeking initial feedback before rebasing to Veramo and opening...
**Bug severity** 3 **Describe the bug** Adding/Updating ION services/keys does not get propagated on chain when using Microsoft Endpoints. Needs more investigation. Microsoft gives back a 200 response for them,...
**Is your feature request related to a problem? Please describe.** For the DID ION keys in pr https://github.com/uport-project/veramo/pull/987 I needed to pre-create keys for rotation and recovery. I also needed...
The examples in the spec use did:key everywhere, but did:key only supports verificationMethod/keys and not services. So the examples in the spec cannot satisfy the actual requirements from the spec...
Currently the credentials and deferred credentials endpoint are having a bit of an asymmetrical implementation. The distinction between whether it is deferred or not is based on the HTTP response...
Hi All, In NL several Dutch SSI vendors (TNO, Dutch Blockchain Coalition, Sphereon, Animo) have started work on a new interop profile which for now has the work title Dutch...
~~In the SIOPv2 spec the iss value possibilities were changed from a static https://self-issued.me/v2 (see PR for the change https://bitbucket.org/openid/connect/pull-requests/120). Basically the iss is the sub for a SIOP. See...
Our Presentation Exchange library conforms to PE v1. In our library we are enforcing that a schema URI is a valid URI according to https://identity.foundation/presentation-exchange/spec/v1.0.0/#input-descriptor-object In this profile an example...
Whilst working on the implementation, one of my colleagues noted an inconsistence In the normative references section of the spec for SD-JWT VC. It points to [draft 10](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-16) in the...