haip-protocol-profile

Name: haip-protocol-profile
Availability: InStock
Author: Sourcelab

Enforce HAIP protocol requirements for OpenID4VP and OpenID4VCI verifiable credential exchange.

Updated Mar 7, 2026

Search Tags:#mdoc #verifiable credentials #sd-jwt #digital identity #openid4vp #haip #openid4vci

Ready to run

npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill haip-protocol-profile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: haip-protocol-profile
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/haip-protocol-profile
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill haip-protocol-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive guidance for implementing the High Assurance Interoperability Profile (HAIP) protocol, ensuring secure and interoperable verifiable credential exchange.

Core Features & Use Cases

OpenID4VP Implementation: Covers request/response modes, client identifiers, and session management for Verifiable Presentations.
OpenID4VCI Support: Details requirements for credential offers, authorization, and credential endpoints for Verifiable Credential Issuance.
Credential Format Profiles: Specifies profiles for ISO mdocs and SD-JWT VCs, ensuring compatibility.
Use Case: A developer building a digital identity wallet needs to ensure it correctly handles Verifiable Presentations according to the HAIP standard, including secure credential offers and presentation exchanges.

Quick Start

Use the haip-protocol-profile skill to understand the requirements for OpenID4VP redirects.

Frequently Asked Questions about haip-protocol-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the HAIP protocol for verifiable credentials?▼

The High Assurance Interoperability Profile (HAIP) enforces secure verifiable credential exchange by standardizing OpenID4VP and OpenID4VCI flows for ISO mdocs and SD-JWT VCs. It specifies security measures like response encryption and cryptographic holder binding to ensure interoperability.

How do I implement OpenID4VP redirects for digital identity wallets?▼

Implement OpenID4VP redirects by following HAIP requirements for request and response modes, client identifiers, and session management. This ensures your digital identity wallet correctly handles Verifiable Presentations according to the interoperability standard.

Does HAIP support both ISO mdocs and SD-JWT VCs?▼

Yes, HAIP specifies distinct credential format profiles for both ISO mdocs and SD-JWT VCs. This ensures compatibility and secure exchange across different verifiable credential formats within OpenID4VP and OpenID4VCI flows.

How do I set up credential offers using OpenID4VCI?▼

Set up OpenID4VCI credential offers by adhering to HAIP requirements for authorization and credential endpoints. This process defines how credentials are securely issued and bound to the holder using cryptographic holder binding.

What security measures are required for HAIP verifiable presentation exchange?▼

HAIP requires response encryption, specific client identifiers, and cryptographic holder binding for secure verifiable presentation exchange. These measures protect credential integrity during OpenID4VP and OpenID4VCI transactions.

Why do I need cryptographic holder binding in OpenID4VP?▼

Cryptographic holder binding is required in HAIP to prove the presenter owns the verifiable credential. It prevents unauthorized credential replay by linking the cryptographic key to the specific credential exchange session.