arf-wscd-states

Explain EUDI Wallet WSCD architectures and state diagrams for ecosystem entities.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill arf-wscd-states
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arf-wscd-states
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/arf-wscd-states
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill arf-wscd-states

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill clarifies the complex architectural choices for Wallet Secure Cryptographic Devices (WSCDs) and details the state transitions for various EUDI Wallet ecosystem entities, ensuring a clear understanding of system behavior and compliance.

Core Features & Use Cases

  • WSCD Architecture Types: Understand and select between Remote, Local External, Local Internal, Local Native, and Hybrid WSCD architectures.
  • State Diagrams: Visualize and comprehend the lifecycle states of Wallet Providers, Wallet Solutions, Wallet Units, PID/Attestation Providers, PIDs/Attestations, and Relying Parties.
  • Pseudonym Implementations: Explore Verifiable, Attested, and Scope Rate-Limited pseudonyms and their implications.
  • Use Case: A developer needs to design a new EUDI Wallet solution and must choose the most appropriate WSCD architecture. This Skill provides the necessary details on each type, their security considerations, and how they integrate into the overall ecosystem.

Quick Start

Explain the different types of WSCD architectures available in the EUDI Wallet ecosystem.

Frequently Asked Questions about arf-wscd-states

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

FAQPage Schema
What are the different WSCD architectures available for an EUDI Wallet solution?

EUDI Wallet WSCD architectures include Remote, Local External, Local Internal, Local Native, and Hybrid models. Each type offers distinct security boundaries and integration patterns for managing cryptographic devices within the wallet ecosystem.

How do I choose the right WSCD architecture for my EUDI Wallet implementation?

Choosing the right WSCD architecture requires evaluating security considerations and ecosystem integration for Remote, Local, or Hybrid models. You must balance hardware isolation, remote management capabilities, and compliance requirements for your specific wallet solution.

What state transitions apply to EUDI Wallet Providers and Relying Parties?

EUDI Wallet state diagrams define lifecycle transitions for Wallet Providers, Solutions, Units, PID Providers, and Relying Parties. These state diagrams map the exact behavioral changes and compliance statuses each ecosystem entity undergoes during operation.

How do Verifiable and Attested pseudonyms work in EUDI Wallet implementations?

EUDI Wallet pseudonyms include Verifiable, Attested, and Scope Rate-Limited types. These pseudonym implementations provide varying levels of privacy and correlation prevention, allowing users to interact with Relying Parties without exposing persistent identifiers.

Can I use a Local Internal WSCD architecture for a compliant EUDI Wallet?

Local Internal WSCD architectures are supported for compliant EUDI Wallet implementations. You must review the specific state diagrams and security considerations to ensure this local cryptographic device model meets your required compliance standards.