hlr-16-signing-documents-with-a-wallet-unit

Provide EUDI ARF Annex 2 SHALL/SHOULD/MAY requirements for signing documents with a Wallet Unit.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-16-signing-documents-with-a-wallet-unit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hlr-16-signing-documents-with-a-wallet-unit
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-16-signing-documents-with-a-wallet-unit
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-16-signing-documents-with-a-wallet-unit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the EUDI high-level requirements for securely signing documents using a Wallet Unit, ensuring compliance with qualified electronic signature standards.

Core Features & Use Cases

  • Wallet Provider Requirements: Details obligations for Wallet Providers regarding qualified certificates, signature creation applications, and QSCD interfaces.
  • QTSP & RP Requirements: Outlines specifications for Qualified Trust Service Providers and Relying Parties involved in the signing process.
  • Use Case: A developer building an EUDI-compliant wallet application needs to understand the mandatory and recommended features for enabling users to create qualified electronic signatures.

Quick Start

Consult the requirements for Wallet Providers when implementing the signing functionality in a Wallet Unit.

Frequently Asked Questions about hlr-16-signing-documents-with-a-wallet-unit

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

FAQPage Schema
What are the EUDI requirements for signing documents with a Wallet Unit?

EUDI Wallet signing requirements mandate secure authentication, signature creation, and format compliance for qualified electronic signatures. They define SHALL, SHOULD, and MAY obligations for Wallet Providers, QTSPs, and Relying Parties to ensure compliance.

How do I implement qualified electronic signatures in an EUDI-compliant wallet?

To implement qualified electronic signatures in an EUDI-compliant wallet, consult the normative requirements for Wallet Providers regarding qualified certificates, signature creation applications, and QSCD interfaces detailed in the EUDI ARF Annex 2.

What obligations do Wallet Providers have for EUDI document signing?

Wallet Providers handling EUDI document signing must fulfill obligations regarding qualified certificates, signature creation applications, and QSCD interfaces. These requirements ensure the secure creation of qualified electronic signatures within the Wallet Unit.

Does the EUDI Wallet signing process specify requirements for QTSPs and Relying Parties?

Yes, the EUDI Wallet signing process specifies requirements for QTSPs and Relying Parties. It outlines specifications for Qualified Trust Service Providers and Relying Parties to ensure secure authentication and proper signature creation during transactions.

What is the difference between SHALL, SHOULD, and MAY requirements in EUDI Wallet signing?

In EUDI Wallet signing, SHALL requirements are mandatory, SHOULD requirements are recommended, and MAY requirements are optional. This hierarchy defines the precise compliance obligations for Wallet Providers, QTSPs, and Relying Parties during signature creation.