hlr-18-combined-presentations-of-attributes

Manage EUDI high-level requirements for cryptographic binding of attestations.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-18-combined-presentations-of-attributes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hlr-18-combined-presentations-of-attributes
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-18-combined-presentations-of-attributes
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-18-combined-presentations-of-attributes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the EUDI high-level requirements for securely combining multiple attestations or attributes within a Wallet Unit, ensuring cryptographic binding and user verification.

Core Features & Use Cases

  • Cryptographic Binding: Implements schemes to prove that multiple private keys are managed by the same Wallet Unit.
  • Attestation Issuance: Supports requesting proof of key management during the issuance of new attestations or PIDs.
  • User Verification: Ensures that new attestations are legitimately linked to the user's existing identity.
  • Use Case: When a user presents a verified identity (PID) and requests a new, specialized attestation, this skill ensures the Wallet Unit can cryptographically prove it manages the keys for both, enhancing trust in the issuance process.

Quick Start

Use the hlr-18-combined-presentations-of-attributes skill to verify the cryptographic binding of attestations for a new issuance request.

Frequently Asked Questions about hlr-18-combined-presentations-of-attributes

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

FAQPage Schema
How does cryptographic binding work for EUDI wallet attestations?▼

Cryptographic binding for EUDI wallet attestations proves a single Wallet Unit manages multiple private keys by cryptographically linking new attestations to existing PIDs during the issuance process, relying on ECCG mechanisms.

How do I verify user identity during EUDI attestation issuance?▼

To verify user identity during EUDI attestation issuance, request proof of key management to ensure the new attestation is cryptographically linked to the user's existing verified identity or PID.

Can I use Zero-Knowledge Proofs for combining EUDI attributes?▼

Yes, you can use Zero-Knowledge Proof mechanisms to combine EUDI attributes, as the skill supports ZKP alongside algorithms from ECCG Agreed Cryptographic Mechanisms to prove private key management.

When do I need cryptographic binding for EUDI Wallet Units?▼

You need cryptographic binding for EUDI Wallet Units when a user presents a verified PID and requests a new specialized attestation, ensuring the Wallet Unit can cryptographically prove it manages keys for both.

What algorithms are required for EUDI combined presentations of attributes?▼

Algorithms required for EUDI combined presentations of attributes rely on the ECCG Agreed Cryptographic Mechanisms and potentially Zero-Knowledge Proof mechanisms to ensure secure cryptographic binding.