hlr-07-attestation-revocation-and-revocation-ch

Name: hlr-07-attestation-revocation-and-revocation-ch
Availability: InStock
Author: Sourcelab

Detail revocation requirements for EUDI attestations and verification processes.

Updated Mar 7, 2026

Search Tags:#security #pid #attestation #revocation #eud #wua

Ready to run

npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-07-attestation-revocation-and-revocation-ch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hlr-07-attestation-revocation-and-revocation-ch
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-07-attestation-revocation-and-revocation-ch
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-07-attestation-revocation-and-revocation-ch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for managing the revocation of EUDI attestations (like PIDs, QEAA, PuB-EAA, and WUAs) and the processes for checking their revocation status.

Core Features & Use Cases

Revocation Methods: Details on how providers must handle revocation, including short-lived attestations, Attestation Status Lists (ASL), and Attestation Revocation Lists (ARL).
Revocation Responsibility: Clarifies who is responsible for revoking specific attestations (e.g., PID Provider for PIDs, Wallet Provider for WUAs).
Revocation Triggers: Outlines conditions under which attestations must be revoked, such as security compromise, user requests, or changes in attribute values.
Relying Party Verification: Specifies how Relying Parties should verify revocation status and the importance of risk analysis.

Quick Start

Understand the requirements for revoking a PID using an Attestation Status List.

Frequently Asked Questions about hlr-07-attestation-revocation-and-revocation-ch

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

FAQPage Schema

How does EUDI attestation revocation work for PIDs and QEAAs?▼

EUDI attestation revocation involves providers invalidating attestations using short-lived attestations, Attestation Status Lists (ASL), or Attestation Revocation Lists (ARL). Providers and relying parties must follow ARF Annex 2 requirements to manage and verify these revocation statuses.

Who is responsible for revoking EUDI attestations like PIDs and WUAs?▼

Revocation responsibility varies by attestation type: the PID Provider handles revoking PIDs, while the Wallet Provider manages the revocation of WUAs. These designated authorities must execute revocation when specific triggers occur.

What triggers an EUDI attestation to be revoked?▼

EUDI attestations must be revoked under specific triggers including security compromises, direct user requests, or when there are changes to attribute values. These conditions ensure compromised attestations are invalidated promptly.

How should relying parties verify the revocation status of EUDI attestations?▼

Relying parties verify EUDI attestation revocation status by checking Attestation Status Lists or Attestation Revocation Lists. They must conduct risk analysis to determine the appropriate verification process according to ARF Annex 2.

What is the difference between Attestation Status Lists and Attestation Revocation Lists?▼

Attestation Status Lists (ASL) and Attestation Revocation Lists (ARL) are distinct revocation methods for EUDI attestations. Providers use these mechanisms alongside short-lived attestations to manage and communicate the invalidation of PIDs, QEAAs, PuB-EAA, and WUAs.

When should I use short-lived attestations instead of a revocation list for EUDI?▼

Short-lived attestations are an alternative EUDI revocation method where expiration naturally limits validity, whereas Attestation Status Lists (ASL) and Revocation Lists (ARL) actively track invalidation. Providers choose based on specific attestation lifecycle and security requirements.