# 2. Introduction

The GovStack initiative offers an open-standard approach to building digital public infrastructure (DPI). However, the GovStack specifications are designed for global use and do not, by default, address the strict and specific requirements of the European Union’s legal framework. This guide fills that gap for GovStack Wallet BB. It describes the EU Implementation process, a guide that tailors the GovStack Wallet Building Block with a reference to Identity, Consent, and eSignature BBs to meet the high security, privacy, and interoperability standards of eIDAS 2.0 and other relevant EU legislation.

The digital transformation of public administration across Europe has reached a decisive moment. Regulation (EU) 2024/1183, commonly referred to as eIDAS 2.0, shifts Europe from fragmented national eID schemes to a common, interoperable framework based on the European Digital Identity Wallet (EUDIW).

For every Member State, this is a legal obligation, not a side project. Citizens, residents, and businesses must be offered a wallet that works across borders and is recognized by both public and private services. This guide suggests how to realize that obligation using the GovStack Digital Identity Building Blocks:

* **Digital Wallet** (<https://wallet.govstack.global/> ) - The core of this guide
* **Identity** (<https://identity.govstack.global/> )
* **Electronic Signature** (<https://esignature.govstack.global/> )
* **Consent** (<https://consent.govstack.global/> )

GovStack brings a modular, open-standard way of building digital public infrastructure. On its own, however, GovStack is global and neutral. The EU legal framework is very specific. This guide applies an EU Layer on top of GovStack so that Member States can:

* configure the Wallet Building Block to comply with eIDAS 2.0 and GDPR
* reuse open components while keeping full national control over identity infrastructure.
* support the use of Building Blocks in European Union and countries looking towards similar regulatory framework.

Done well, the outcome is straightforward to describe, even if the engineering is not: a citizen can prove attributes and sign contracts anywhere in the EU – all through one wallet backed by national infrastructure and trust lists.

This guide is written for:

* public‑sector CIOs and CTOs deciding on wallet strategy and architecture;
* lead solution and enterprise architects designing the national identity stack;
* program managers overseeing procurement and integration;
* vendors and integrators building or adapting wallet solutions in line with GovStack.

It assumes familiarity with basic identity and security concepts, but it does not require deep protocol expertise, those details live inside the GovStack Wallet specification and the EUDIW ARF.

## **2.2 Scope and Application**

The primary purpose is to guide public‑sector teams through the configuration and governance of a wallet solution that:

* implements the GovStack Wallet specification;
* meets the EUDIW Architecture Reference Framework (ARF) profile, and
* satisfies the legal conditions attached to a European Digital Identity Wallet.

This guide is wallet-centric. Its primary object is the GovStack Wallet Building Block configured as a European Digital Identity Wallet component, specifically the user-facing wallet application and its wallet-unit functions. It covers the GovStack Identity, Consent, and Electronic Signature Building Blocks only where they interact with the wallet or are needed to make the wallet usable in an eIDAS 2.0 environment.

## **2.3 Relation to Other Documents**

The Wallet Implementation Guide sits beside:

* The GovStack Wallet specification, which defines functions and interfaces.
* The GovStack Identity, Consent, and Signature specifications
* The Cross‑Functional Requirements (CFRs), which impose shared constraints such as security and logging.
* The EUDIW Architecture Reference Framework, which profiles standards like OpenID4VCI and OpenID4VP.
* National legal and policy documents.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://specs.govstack.global/impl-eidas-wallet/2.-introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.