Let's talk



Support for High Assurance Interoperability Profile in Credo

We're currently looking to fund this proposal. Read the full technical proposal here

In our previous efforts, to make Credo compatible with the ARF Animo raised funds to support required standards in the popular JavaScript framework. The effort led to the support of OpenID for Verifiable Credentials, SD-JWTs, Hardware Security Support in Aries Askar, and support for the Mobile Drivers License (ISO/IEC 18013-5).

These additions result in significant progress in compliance with European regulations; however, they do not guarantee interoperability. To address this, the High Assurance Interoperability Profile (HAIP) was introduced, providing requirements around the configuration and use of the OpenID4VC protocols and SD-JWT credential format. An explicit goal of the HAIP specification is to support “eIDAS PID and (Q)EAA as defined in eIDAS ARF 1.0”. The HAIP specification emphasizes privacy and security and can be used for high assurance credentials. HAIP will be crucial in creating interoperability between different systems and implementations in the European ecosystem and beyond.

In light of our continuous efforts to make Credo a framework that simplifies the development of decentralized identity solutions, we propose adding a set of features to make it as easy as possible to conform to HAIP. By incorporating extra configuration, automation, and validation logic within the framework, we can significantly reduce the amount of work that users of the framework need to do to comply with the profile.

The 4 main work items are:

  • Work item 1: Support for X.509 certificate chain verification - € 38.400
  • Work item 2: Credo OpenID4VC modules - € 55.200
  • Work item 3: Token Status List - € 19.200
  • Work item 4: HAIP-specific functionality in Credo - € 31.200

🚧 This proposal is currently looking for funding. Reach out to berend@animo.id to get involved.